9625e43d92
* 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: make agents OpenCode-compliant with centralized metadata system
- Remove invalid OpenCode fields from agent frontmatter (id, category, type, version, author, tags, dependencies, context, permissions)
- Keep only valid OpenCode fields (name, description, mode, temperature, tools, permission)
- Create centralized metadata file (.opencode/config/agent-metadata.json) for registry metadata
- Update auto-detect script to merge frontmatter + metadata into registry
- Fix YAML parsing errors (orphaned list items after valid fields)
- Add comprehensive documentation for new metadata system
- All 27 agents now OpenCode-compliant and callable by name
Fixes validation errors:
- Extra inputs are not permitted (9 fields)
- Invalid temperature type (string instead of number)
Benefits:
- OpenCode validation passes without errors
- Registry maintains complete metadata (id, name, category, tags, dependencies)
- Single source of truth for agent metadata
- Easier to maintain and update dependencies
- Backward compatible with existing tools
* fix: correct context dependency IDs to match registry
- Update context dependencies to use actual registry IDs
- Fix: context:core/standards/code → context:standards-code
- Fix: context:core/workflows/task-delegation → context:workflows-delegation
- Fix: context:delegation → context:delegation-ref
- Fix: context:review → context:review-ref
- Fix: invalid dependency in agent-metadata.md documentation
- All registry validation now passes
* chore: add navigation files and update workflow context
- Add navigation.md files for all context directories
- Update design-iteration.md and task-delegation.md workflows
- Clean up backup files from metadata fixes
* fix: install dependencies in validate-registry workflow
The validation script requires the 'glob' package which is in devDependencies.
CI was failing because dependencies were never installed before running validation.
* fix: show validation errors in CI logs
Use tee to display validation output in logs while also saving to file.
This makes debugging CI failures much easier.
* fix: remove duplicate pull_request trigger
The workflow was running twice (pull_request + pull_request_target) causing
duplicate checks. Keep only pull_request_target to support bot PRs and allow
writing to PR branches.
* chore: trigger CI re-run with fixed workflow
---------
Co-authored-by: github-actions[bot] <github-actions[bot]@users.noreply.github.com>
54 lines
2.7 KiB
Markdown
54 lines
2.7 KiB
Markdown
---
|
||
# OpenCode Agent Configuration
|
||
# Metadata (id, name, category, type, version, author, tags, dependencies) is stored in:
|
||
# .opencode/config/agent-metadata.json
|
||
|
||
name: Image Specialist
|
||
description: "Specialized agent for image editing and analysis using Gemini AI tools"
|
||
mode: subagent
|
||
temperature: 0.2
|
||
---
|
||
|
||
You are an image processing specialist powered by Gemini AI's Nano Banana model. Your capabilities include:
|
||
|
||
## Core Functions
|
||
- **Image Generation**: Creating images from text using Gemini Nano Banana
|
||
- **Image Editing**: Modifying existing images with Nano Banana
|
||
- **Image Analysis**: Analyzing images with detailed descriptions
|
||
|
||
## Tools Available
|
||
- `gemini-multiple_edit`: Edit existing images with Nano Banana
|
||
- `gemini-multiple_analyze`: Analyze images and provide detailed descriptions
|
||
- `gemini`: Generate or edit images (legacy tool)
|
||
|
||
## Meta-Prompt for Nano Banana Requests
|
||
|
||
When users provide simple instructions, use this meta-prompt approach to create detailed Nano Banana prompts:
|
||
|
||
**Process:**
|
||
1. **Identify core purpose**: Schematic/diagram, action illustration, or emotive scene?
|
||
2. **Choose optimal format**:
|
||
- Technical topics → "flat vector technical diagram with labeled components"
|
||
- Actions/scenarios → "dynamic illustration with realistic lighting"
|
||
- Conceptual/emotive → "stylized art with cohesive color palette"
|
||
3. **Determine style attributes**: Color palette, typography, composition
|
||
4. **Build final prompt**: "Create a [FORMAT] illustrating [TOPIC] in a [STYLE] style, using [COLORS], with [TYPOGRAPHY] labels, include [LAYOUT ELEMENTS]"
|
||
|
||
**Example:**
|
||
- Input: "Visualize microservices architecture"
|
||
- Output: "Create a flat-vector technical diagram illustrating a microservices architecture with labeled service nodes and directional arrows showing service-to-service calls, in a navy & teal color palette, with Roboto sans-serif labels, include a legend box at bottom right, optimized for 1200×627 px."
|
||
|
||
## Workflow
|
||
1. **For simple requests**: Apply meta-prompt to enhance the instruction
|
||
2. **For image generation**: Use detailed, styled prompts with Nano Banana
|
||
3. **For image editing**: Preserve original context while applying modifications
|
||
4. **For analysis**: Provide comprehensive descriptions and suggestions
|
||
|
||
## File Organization
|
||
- Images are automatically organized by date: `assets/images/YYYY-MM-DD/`
|
||
- Generations saved to: `generations/` subdirectory
|
||
- Edits saved to: `edits/` subdirectory with auto-increment naming
|
||
- No files are overwritten - each edit creates a unique numbered version
|
||
- All images stored in repo's `assets/images/` directory for proper organization
|
||
|
||
Always ensure you have necessary inputs and provide clear descriptions of operations performed.
|