@fro.bot/systematic 1.14.0 → 1.16.0

package/README.md

@@ -42,7 +42,7 @@ Most AI coding assistants respond to requests without structure or methodology.
 - **Specialized Agents** — Purpose-built subagents for architecture, security, and performance
 - **Zero Configuration** — Works immediately after installation via config hooks
 - **Extensible** — Add project-specific skills and commands alongside bundled ones
-- **Batteries Included** — 8 skills, 24 agents, and 9 commands ship with the npm package
+- **Batteries Included** — 11 skills, 24 agents, and 9 commands ship with the npm package
 - **CLI Tooling** — Inspect, list, and convert assets from the command line
 
 ## Quick Start
@@ -67,6 +67,29 @@ That's it. Restart OpenCode and the plugin's skills, agents, and commands are av
 > [!NOTE]
 > Systematic uses OpenCode's `config` hook to automatically register all bundled content. No manual file copying required.
 
+### Alternative: Install via OCX
+
+[OCX](https://github.com/kdcokenny/ocx) provides component-level installation:
+
+```bash
+# Add the Systematic registry
+ocx registry add https://fro.bot/systematic --name systematic
+
+# Install individual components
+ocx add systematic/brainstorming
+ocx add systematic/agent-architecture-strategist
+
+# Or install bundles
+ocx add systematic/skills     # All 11 skills
+ocx add systematic/agents     # All 24 agents
+ocx add systematic/commands   # All 9 commands
+
+# Or use a profile
+ocx profile add sys --from systematic/standalone
+```
+
+See the [OCX Registry Guide](https://fro.bot/systematic/guides/ocx-registry/) for details.
+
 ### Verify Installation
 
 In any OpenCode conversation, type:
@@ -88,9 +111,12 @@ Skills are structured workflows that guide the AI through systematic engineering
 | `agent-browser` | Browser automation using Vercel's agent-browser CLI |
 | `agent-native-architecture` | Design systems where AI agents are first-class citizens |
 | `compound-docs` | Capture solved problems as categorized documentation |
-| `creating-agent-skills` | Expert guidance for writing and refining skills |
+| `create-agent-skills` | Expert guidance for writing and refining skills |
+| `document-review` | Refine brainstorm or plan documents before proceeding to the next workflow step |
 | `file-todos` | File-based todo tracking with status and dependency management |
+| `frontend-design` | Create distinctive, production-grade frontend interfaces with high design quality |
 | `git-worktree` | Manage git worktrees for isolated parallel development |
+| `orchestrating-swarms` | Coordinate multi-agent swarms, parallel reviews, and pipeline workflows |
 
 ### How Skills Work
 
@@ -369,7 +395,7 @@ systematic/
 │       ├── manifest.ts       # Upstream sync manifest tracking
 │       ├── validation.ts     # Agent config validation + type guards
 │       └── walk-dir.ts       # Recursive directory walker
-├── skills/                   # 8 bundled skills (SKILL.md files)
+├── skills/                   # 11 bundled skills (SKILL.md files)
 ├── agents/                   # 24 bundled agents (4 categories)
 ├── commands/                 # 9 bundled commands (with workflows/ subdir)
 ├── docs/                     # Starlight documentation site

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@fro.bot/systematic",
-  "version": "1.14.0",
+  "version": "1.16.0",
   "description": "Structured engineering workflows for OpenCode",
   "type": "module",
   "homepage": "https://fro.bot/systematic",
@@ -37,6 +37,8 @@
     "docs:build": "bun run docs:generate && bun run --cwd docs build",
     "docs:preview": "bun run --cwd docs preview",
     "docs:generate": "bun docs/scripts/transform-content.ts",
+    "registry:build": "bun scripts/build-registry.ts",
+    "registry:validate": "bun scripts/build-registry.ts --validate-only",
     "prepublishOnly": "bun run build"
   },
   "keywords": [
@@ -46,7 +48,7 @@
     "workflow",
     "engineering"
   ],
-  "author": "Marcus R. Brown",
+  "author": "Marcus R. Brown <human@fro.bot>",
   "license": "MIT",
   "repository": {
     "type": "git",

package/skills/agent-browser/SKILL.md

@@ -221,3 +221,4 @@ Use Playwright MCP when:
 - You need deep MCP tool integration
 - You want tool-based responses
 - You're building complex automation
+

package/skills/agent-native-architecture/SKILL.md

@@ -6,13 +6,13 @@ description: Build applications where agents are first-class citizens. Use this
 <why_now>
 ## Why Now
 
-Software agents work reliably now. Claude Code demonstrated that an LLM with access to bash and file tools, operating in a loop until an objective is achieved, can accomplish complex multi-step tasks autonomously.
+Software agents work reliably now. Modern coding agents like OpenCode have demonstrated that an LLM with access to bash and file tools, operating in a loop until an objective is achieved, can accomplish complex multi-step tasks autonomously.
 
-The surprising discovery: **a really good coding agent is actually a really good general-purpose agent.** The same architecture that lets Claude Code refactor a codebase can let an agent organize your files, manage your reading list, or automate your workflows.
+The surprising discovery: **a really good coding agent is actually a really good general-purpose agent.** The same architecture that lets an agent refactor a codebase can let it organize your files, manage your reading list, or automate your workflows.
 
-The Claude Code SDK makes this accessible. You can build applications where features aren't code you write—they're outcomes you describe, achieved by an agent with tools, operating in a loop until the outcome is reached.
+Agent SDKs make this accessible. You can build applications where features aren't code you write—they're outcomes you describe, achieved by an agent with tools, operating in a loop until the outcome is reached.
 
-This opens up a new field: software that works the way Claude Code works, applied to categories far beyond coding.
+This opens up a new field: software that works the way modern coding agents work, applied to categories far beyond coding.
 </why_now>
 
 <core_principles>

package/skills/agent-native-architecture/references/files-universal-interface.md

@@ -5,7 +5,7 @@ Files are the universal interface for agent-native applications. Agents are natu
 <why_files>
 ## Why Files
 
-Agents are naturally good at files. Claude Code works because bash + filesystem is the most battle-tested agent interface. When building agent-native apps, lean into this.
+Agents are naturally good at files. OpenCode works because bash + filesystem is the most battle-tested agent interface. When building agent-native apps, lean into this.
 
 ### Agents Already Know How
 

package/skills/agent-native-architecture/references/product-implications.md

@@ -11,7 +11,7 @@ The best agent-native applications are simple to start but endlessly powerful.
 
 Excel is the canonical example: you can use it for a grocery list, or you can build complex financial models. The same tool, radically different depths of use.
 
-Claude Code has this quality: fix a typo, or refactor an entire codebase. The interface is the same—natural language—but the capability scales with the ask.
+OpenCode has this quality: fix a typo, or refactor an entire codebase. The interface is the same—natural language—but the capability scales with the ask.
 
 ### The Pattern
 

package/skills/brainstorming/SKILL.md

@@ -188,3 +188,4 @@ Planning answers **HOW** to build it:
 - Testing strategy and verification
 
 When brainstorm output exists, `/workflows:plan` should detect it and use it as input, skipping its own idea refinement phase.
+

package/skills/compound-docs/SKILL.md

@@ -1,11 +1,12 @@
 ---
 name: compound-docs
 description: Capture solved problems as categorized documentation with YAML frontmatter for fast lookup
+disable-model-invocation: true
 allowed-tools:
-  - Read # Parse conversation context
-  - Write # Create resolution docs
-  - Bash # Create directories
-  - Grep # Search existing docs
+  - Read
+  - Write
+  - Bash
+  - Grep
 preconditions:
   - Problem has been solved (not in-progress)
   - Solution has been verified working
@@ -61,7 +62,7 @@ Extract from conversation history:
 
 **Required information:**
 
-- **Module name**: Which CORA module had the problem
+- **Module name**: Which module or component had the problem
 - **Symptom**: Observable error/behavior (exact error messages)
 - **Investigation attempts**: What didn't work and why
 - **Root cause**: Technical explanation of actual problem
@@ -249,7 +250,7 @@ But **NEVER auto-promote**. User decides via decision menu (Option 2).
 
 **Template for critical pattern addition:**
 
-When user selects Option 2 (Add to Required Reading), use the template from `assets/critical-pattern-template.md` to structure the pattern entry. Number it sequentially based on existing patterns in `docs/solutions/patterns/cora-critical-patterns.md`.
+When user selects Option 2 (Add to Required Reading), use the template from `assets/critical-pattern-template.md` to structure the pattern entry. Number it sequentially based on existing patterns in `docs/solutions/patterns/critical-patterns.md`.
 </step>
 
 </critical_sequence>
@@ -270,7 +271,7 @@ File created:
 
 What's next?
 1. Continue workflow (recommended)
-2. Add to Required Reading - Promote to critical patterns (cora-critical-patterns.md)
+2. Add to Required Reading - Promote to critical patterns (critical-patterns.md)
 3. Link related issues - Connect to similar problems
 4. Add to existing skill - Add to a learning skill (e.g., hotwire-native)
 5. Create new skill - Extract into new learning skill
@@ -295,7 +296,7 @@ User selects this when:
 Action:
 1. Extract pattern from the documentation
 2. Format as ❌ WRONG vs ✅ CORRECT with code examples
-3. Add to `docs/solutions/patterns/cora-critical-patterns.md`
+3. Add to `docs/solutions/patterns/critical-patterns.md`
 4. Add cross-reference back to this doc
 5. Confirm: "✓ Added to Required Reading. All subagents will see this pattern before code generation."
 
@@ -317,7 +318,7 @@ Action:
 4. Confirm: "✓ Added to [skill-name] skill in [file]"
 
 Example: For Hotwire Native Tailwind variants solution:
-- Add to `hotwire-native/references/resources.md` under "CORA-Specific Resources"
+- Add to `hotwire-native/references/resources.md` under "Project-Specific Resources"
 - Add to `hotwire-native/references/examples.md` with link to solution doc
 
 **Option 5: Create new skill**
@@ -326,7 +327,7 @@ User selects this when the solution represents the start of a new learning domai
 
 Action:
 1. Prompt: "What should the new skill be called? (e.g., stripe-billing, email-processing)"
-2. Run `python3 .claude/skills/skill-creator/scripts/init_skill.py [skill-name]`
+2. Run `python3 .opencode/skills/create-agent-skills/scripts/init_skill.py [skill-name]`
 3. Create initial reference files with this solution as first example
 4. Confirm: "✓ Created new [skill-name] skill with this solution as first example"
 
@@ -397,11 +398,11 @@ Documentation is successful when ALL of the following are true:
 - Present multiple matches
 - Let user choose: new doc, update existing, or link as duplicate
 
-**Module not in CORA-MODULES.md:**
+**Module not in modules documentation:**
 
 - Warn but don't block
 - Proceed with documentation
-- Suggest: "Add [Module] to CORA-MODULES.md if not there"
+- Suggest: "Add [Module] to modules documentation if not there"
 
 ---
 
@@ -488,7 +489,7 @@ File created:
 
 What's next?
 1. Continue workflow (recommended)
-2. Add to Required Reading - Promote to critical patterns (cora-critical-patterns.md)
+2. Add to Required Reading - Promote to critical patterns (critical-patterns.md)
 3. Link related issues - Connect to similar problems
 4. Add to existing skill - Add to a learning skill (e.g., hotwire-native)
 5. Create new skill - Extract into new learning skill

package/skills/compound-docs/assets/critical-pattern-template.md

@@ -1,6 +1,6 @@
 # Critical Pattern Template
 
-Use this template when adding a pattern to `docs/solutions/patterns/cora-critical-patterns.md`:
+Use this template when adding a pattern to `docs/solutions/patterns/critical-patterns.md`:
 
 ---
 

package/skills/compound-docs/assets/resolution-template.md

@@ -1,5 +1,5 @@
 ---
-module: [Module name or "CORA" for system-wide]
+module: [Module name or "System" for system-wide]
 date: [YYYY-MM-DD]
 problem_type: [build_error|test_failure|runtime_error|performance_issue|database_issue|security_issue|ui_bug|integration_issue|logic_error]
 component: [rails_model|rails_controller|rails_view|service_object|background_job|database|frontend_stimulus|hotwire_turbo|email_processing|brief_system|assistant|authentication|payments]
@@ -19,7 +19,7 @@ tags: [keyword1, keyword2, keyword3]
 [1-2 sentence clear description of the issue and what the user experienced]
 
 ## Environment
-- Module: [Name or "CORA system"]
+- Module: [Name or "System-wide"]
 - Rails Version: [e.g., 7.1.2]
 - Affected Component: [e.g., "Email Processing model", "Brief System service", "Authentication controller"]
 - Date: [YYYY-MM-DD when this was solved]
@@ -78,7 +78,7 @@ tags: [keyword1, keyword2, keyword3]
 
 ## Prevention
 
-[How to avoid this problem in future CORA development:]
+[How to avoid this problem in future development:]
 - [Specific coding practice, check, or pattern to follow]
 - [What to watch out for]
 - [How to catch this early]

package/skills/compound-docs/references/yaml-schema.md

@@ -1,10 +1,10 @@
 # YAML Frontmatter Schema
 
-**See `.claude/skills/codify-docs/schema.yaml` for the complete schema specification.**
+**See `.opencode/skills/compound-docs/schema.yaml` for the complete schema specification.**
 
 ## Required Fields
 
-- **module** (string): Module name (e.g., "EmailProcessing") or "CORA" for system-wide issues
+- **module** (string): Module name (e.g., "EmailProcessing") or "System" for system-wide issues
 - **date** (string): ISO 8601 date (YYYY-MM-DD)
 - **problem_type** (enum): One of [build_error, test_failure, runtime_error, performance_issue, database_issue, security_issue, ui_bug, integration_issue, logic_error, developer_experience, workflow_issue, best_practice, documentation_gap]
 - **component** (enum): One of [rails_model, rails_controller, rails_view, service_object, background_job, database, frontend_stimulus, hotwire_turbo, email_processing, brief_system, assistant, authentication, payments, development_workflow, testing_framework, documentation, tooling]