* feat(context): Add project intelligence system - Add project-intelligence.md standard (what & why) - Add project-intelligence-management.md guide (how to manage) - Add project-intelligence/ folder with 6 context files: - navigation.md (quick overview & routes) - business-domain.md (business context, users, value) - technical-domain.md (stack, architecture, decisions) - business-tech-bridge.md (business → technical mapping) - decisions-log.md (decision history with context) - living-notes.md (active issues, debt, questions) - Update standards navigation with new entries - Register all new contexts in registry.json This enables projects to document and maintain business + technical context for quick onboarding and lasting project understanding. * fix(registry): Add project-intelligence to profiles - Add context:project-intelligence/* to developer, business, full, and advanced profiles - Ensures project intelligence contexts are included when these profiles are selected This complements commit c731328 which added the context entries. * docs(core): refine project intelligence system and deprecate legacy context * feat(claude): simplify Claude Code integration with unified installer - Create single install-claude.sh script that auto-converts and installs - Remove redundant bootstrap-install.sh and install.sh scripts - Delete stale plugin/ directory (now auto-generated from .opencode/) - Add Claude Code documentation (agent-skills, create-subagents, hooks, plugins) - Add installation profiles (essential, developer, business, full, advanced) - Update README with Claude Code beta feature documentation - Add component-planning.md workflow context - Clean up demo files (assets/, src/) - Update registry with new context entries - Add gitignore rule for converter/generated/ The new installer: - Converts agents automatically from .opencode/agent/ - Installs fresh converted agents to ~/.claude/plugins/ - Single command: ./integrations/claude-code/install-claude.sh * fix: update README to use new install-claude.sh script The Claude Code integration now uses the unified install-claude.sh script instead of the removed bootstrap-install.sh and install.sh scripts. * fix(context): Add frontmatter to context files with missing metadata - Add YAML frontmatter with description to system-builder-templates - Add frontmatter to ui/web/design context files - Fixes validation warnings in validate-component.sh * fix(registry): Remove orphaned context entries for deleted files - Remove copywriting-frameworks entry (file moved to content-creation/principles/) - Remove tone-voice entry (file moved to content-creation/principles/)
68 lines
2.2 KiB
Markdown
68 lines
2.2 KiB
Markdown
---
|
|
description: "Overview of available templates for generating context-aware AI systems"
|
|
---
|
|
|
|
# System Builder Templates
|
|
|
|
This directory contains reusable templates for generating context-aware AI systems.
|
|
---
|
|
## Template Categories
|
|
|
|
### Agent Templates
|
|
- `orchestrator-template.md` - Main coordinator agent pattern
|
|
- `subagent-template.md` - Specialized subagent pattern
|
|
- `research-agent-template.md` - Research/information gathering pattern
|
|
- `validation-agent-template.md` - Quality assurance pattern
|
|
- `processing-agent-template.md` - Data transformation pattern
|
|
|
|
### Context Templates
|
|
- `domain-knowledge-template.md` - Domain concept documentation
|
|
- `process-workflow-template.md` - Process/workflow documentation
|
|
- `standards-template.md` - Quality and validation standards
|
|
- `template-pattern-template.md` - Reusable output templates
|
|
|
|
### Workflow Templates
|
|
- `simple-workflow-template.md` - Linear 3-5 stage workflow
|
|
- `moderate-workflow-template.md` - Multi-step with decisions
|
|
- `complex-workflow-template.md` - Multi-agent coordination
|
|
|
|
### Command Templates
|
|
- `simple-command-template.md` - Single parameter command
|
|
- `parameterized-command-template.md` - Multi-parameter with flags
|
|
|
|
### Documentation Templates
|
|
- `readme-template.md` - System overview README
|
|
- `architecture-template.md` - Architecture documentation
|
|
- `testing-template.md` - Testing checklist
|
|
- `quickstart-template.md` - Quick start guide
|
|
|
|
## Usage
|
|
|
|
These templates are used by the system-builder subagents to generate consistent,
|
|
high-quality files following research-backed patterns.
|
|
|
|
Each template includes:
|
|
- XML structure with optimal component ordering
|
|
- Placeholder markers for customization
|
|
- Example content
|
|
- Validation criteria
|
|
- Best practices
|
|
|
|
## Template Variables
|
|
|
|
Templates use these variable patterns:
|
|
- `{domain}` - Domain name
|
|
- `{agent_name}` - Agent name
|
|
- `{purpose}` - Purpose description
|
|
- `{workflow_name}` - Workflow name
|
|
- `{context_file}` - Context file reference
|
|
|
|
## Quality Standards
|
|
|
|
All templates follow:
|
|
- Stanford/Anthropic XML research patterns
|
|
- Optimal component ordering (context→role→task→instructions)
|
|
- Hierarchical context structure
|
|
- @ symbol routing for subagents
|
|
- 3-level context allocation
|
|
- Validation gates and checkpoints
|