* chore: bump version to v0.8.0
* chore: update version to 0.7.1 instead of 0.8.0
* docs: expand comparison table with Oh My OpenCode and additional features
* backup: development context before reorganization
* refactor(context): reorganize development folder
- Remove 7 duplicate files (ui/design files exist in ui/web/)
- Remove 2 redundant READMEs (use navigation.md instead)
- Move react-patterns.md to frontend/react/
- Create frontend/react/navigation.md
- Update 4 navigation files (development, ui, frontend, frontend/react)
- Update developer profile (4 path changes: ui-styling-standards, design-systems, design-assets, animation-patterns)
- Update 3 core context files (visual-development.md, design-iteration.md, file-locations.md)
Result: 29 context files (down from 36), no duplicates, clean structure
Refs: REORGANIZATION_PLAN.md, REORGANIZATION_SUMMARY.md
* docs(context): add frontend delegation guide
- Create when-to-delegate.md with clear decision criteria
- Decision matrix for when to delegate vs. handle directly
- Common patterns and examples
- Red flags and green flags
- Frontend-specialist capabilities reference
- Update frontend and development navigation files
Helps orchestrators decide when to delegate UI work to frontend-specialist subagent.
* feat: enhance developer and advanced profiles with UI, development, and system builder context
- Developer profile: Add UI/UX patterns, development principles, design systems, React patterns, animation patterns, styling standards, and design assets
- Full profile: Add same UI/development context as developer profile for consistency
- Advanced profile: Add comprehensive system builder context including templates, guides, context system standards, and repository management context
- Update profile descriptions to reflect new capabilities
- All context files verified to exist and are properly referenced
* fix: remove duplicate context entries with incorrect paths
- Remove duplicate design-assets, ui-styling-standards, clean-code, animation-patterns, design-systems, react-patterns, and api-design entries that pointed to wrong paths
- Remove non-existent development-readme and mastra-ai-readme entries
- Keep only correct entries with proper file paths
- All registry paths now validated and correct
* feat: add add-context command to registry and all profiles
- Register add-context command in registry.json
- Add command:add-context to all 5 profiles (essential, developer, business, full, advanced)
- Update add-context.md to mention external-context files in .tmp/ directory
- Fix command dependencies to use context IDs instead of full paths
- All registry paths and dependencies validated
* feat: enhance add-context with external context file management
- Add Stage 0: Detect external context files in .tmp/
- Offer options to extract, manage, or harvest external files
- Extract patterns from external context files for use in project intelligence
- Provide management options: update, remove, clean, or harvest
- Add examples showing external context extraction and management
- Update troubleshooting with external context file handling
- Integrate with /context harvest command for permanent context organization
* fix: comprehensive context system audit and restructuring
- Fix 6 command documentation inconsistencies in add-context.md
* Correct /add-context vs /context harvest command references
* Simplify Stage 0 workflow from 4 to 2 options
* Update examples to match actual behavior
* Remove non-existent operations from delegation section
* Fix troubleshooting Q&A section
- Restructure registry.json with 4 major improvements
* Replace 31 duplicate 'navigation' IDs with unique IDs per subfolder
- core-navigation, development-navigation, openagents-repo-navigation, etc.
* Add context:openagents-repo/* to developer and full profiles
- Developers now have repo-specific guides and examples
* Remove context:to-be-consumed/* from essential, developer, business, full
- Keep only in advanced profile for system builders
* Properly scope mastra-ai context via wildcard patterns
Validation Results:
- Registry: 220/220 paths valid, 0 missing dependencies
- Profiles: All appropriately scoped with no duplicate IDs
- Standards: MVI compliance, frontmatter, structure verified
- No regressions: All tests passing
Fixes issues with context organization, command consistency, and profile coverage.
* feat: add premium dark UI design system context
- Add comprehensive quick start guide for premium dark UI
- Add visual reference guide with ASCII diagrams
- Includes color palette, components, layouts, and best practices
- Provides glassmorphism and radial glow patterns
- Complete with accessibility guidelines and responsive design
- Ready-to-use code snippets and templates
* docs: update design navigation with premium dark UI guides
* fix: Clean up agent YAML frontmatter and add standards
Fixed YAML frontmatter issues in 18 agent files:
- Removed duplicate YAML keys (e.g., read: true followed by read: {})
- Removed orphaned list items without parent keys
- Fixed field names (permission: → permissions:)
- Removed extra --- delimiter blocks in content
- Cleaned up comments and invalid OpenCode fields
Changes:
- 14 subagent files fixed (core, code, development, system-builder)
- 4 primary/meta agent files fixed (openagent, opencoder, repo-manager, eval-runner)
- Net reduction: 439 lines removed, 116 lines added (cleaner YAML)
Added agent standards documentation:
- .opencode/context/openagents-repo/standards/agent-frontmatter.md
- .opencode/context/openagents-repo/standards/subagent-structure.md
- .opencode/context/openagents-repo/standards/navigation.md
- Updated main navigation.md with standards section
All files follow MVI principles (<200 lines) and document the 5 common
YAML mistakes that were fixed.
Fixes subagent recognition issues where agents were registered as 'all'
mode instead of 'subagent' mode due to malformed YAML.
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
4.2 KiB
4.2 KiB
Standard: Subagent File Structure
Purpose: Standard structure for subagent files
Priority: CRITICAL - Load this before creating subagent files
File Template
---
name: AgentName
description: Brief description
mode: subagent
temperature: 0.1
tools: {...}
permissions: {...}
---
# AgentName
> **Mission**: One-sentence mission
<rule id="rule_name">Rule description</rule>
<context>
<system>Role in pipeline</system>
<domain>Expertise area</domain>
<task>What agent does</task>
<constraints>Limitations</constraints>
</context>
<tier level="1" desc="Critical">
- @rule_id: Description
</tier>
## Workflow
### Step 1: Preparation
### Step 2: Execution
### Step 3: Output
## Output Format
```yaml
status: "success" | "failure"
---
## Section Details
### 1. Frontmatter
- ONLY valid OpenCode fields (see agent-frontmatter.md)
- No duplicate keys, orphaned items, or invalid fields
### 2. Header + Mission
```markdown
# TestEngineer
> **Mission**: Author tests following TDD — grounded in project standards.
3. Critical Rules (3-5 max)
<rule id="context_first">ALWAYS call ContextScout BEFORE writing tests.</rule>
<rule id="positive_and_negative">EVERY behavior needs positive AND negative tests.</rule>
4. Context
<context>
<system>Code quality gate</system>
<domain>Code review, security, quality</domain>
<task>Review code against standards</task>
<constraints>Read-only, no modifications</constraints>
</context>
5. Execution Tiers
<tier level="1" desc="Critical">
- @context_first: Load context first
</tier>
<tier level="2" desc="Core">
- Load standards
- Analyze code
</tier>
<conflict_resolution>Tier 1 overrides Tier 2/3</conflict_resolution>
Tool Permission Patterns
Read-Only (Reviewers, Analyzers)
tools: {read: true, grep: true, glob: true, bash: false, edit: false, write: false}
permissions:
bash: {"*": "deny"}
edit: {"**/*": "deny"}
task: {contextscout: "allow", "*": "deny"}
Write-Enabled (Coders, Testers)
tools: {read: true, edit: true, write: true, bash: true}
permissions:
bash: {"npm test *": "allow", "git *": "allow", "sudo *": "deny", "*": "deny"}
edit: {"**/*.env*": "deny", "**/*.key": "deny"}
task: {contextscout: "allow", "*": "deny"}
Restricted Bash (Task Managers)
tools: {read: true, bash: true}
permissions:
bash: {"npx ts-node*task-cli*": "allow", "mkdir -p .tmp/tasks*": "allow", "*": "deny"}
File Organization
.opencode/agent/subagents/
├── code/ # tester, reviewer, coder-agent, build-agent
├── core/ # task-manager, contextscout, documentation
├── system-builder/ # agent-generator, command-creator
└── utils/ # image-specialist
Validation Checklist
- Valid OpenCode frontmatter (no extra fields)?
- Mission statement present?
- 3-5 critical rules with unique IDs?
- Context section complete?
- Execution tiers defined with conflict resolution?
- Workflow steps clear and actionable?
- Output format specified?
- Tool permissions appropriate for role?
- File in correct category directory?
- No YAML syntax errors?
Common Patterns
Context-First Pattern:
<rule id="context_first">
ALWAYS call ContextScout BEFORE starting work. Load relevant standards first.
</rule>
Read-Only Pattern:
<rule id="read_only">
Read-only agent. NEVER use write, edit, or bash. Provide suggestions only.
</rule>
Security Pattern:
permissions:
edit:
"**/*.env*": "deny"
"**/*.key": "deny"
"**/*.secret": "deny"
Examples
See existing subagents:
.opencode/agent/subagents/code/tester.md- Write-enabled with tests.opencode/agent/subagents/code/reviewer.md- Read-only reviewer.opencode/agent/subagents/core/task-manager.md- Restricted bash
Related
- Frontmatter:
standards/agent-frontmatter.md - Metadata:
core-concepts/agent-metadata.md - Adding Agents:
guides/adding-agent.md
Last Updated: 2026-01-31 | Version: 1.0.0