@soleri/forge 9.0.0 → 9.0.1

package/dist/skills/brainstorming.md

@@ -1,180 +0,0 @@
----
-name: brainstorming
-description: 'You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.'
----
-
-<!-- Adapted from superpowers (MIT License) -->
-
-# Brainstorming Ideas Into Designs
-
-## Overview
-
-Help turn ideas into fully formed designs and specs through natural collaborative dialogue.
-
-Start by understanding the current project context, then ask questions one at a time to refine the idea. Once you understand what you're building, present the design and get user approval.
-
-<HARD-GATE>
-Do NOT invoke any implementation skill, write any code, scaffold any project, or take any implementation action until you have presented a design and the user has approved it. This applies to EVERY project regardless of perceived simplicity.
-</HARD-GATE>
-
-## Anti-Pattern: "This Is Too Simple To Need A Design"
-
-Every project goes through this process. A todo list, a single-function utility, a config change — all of them. "Simple" projects are where unexamined assumptions cause the most wasted work. The design can be short (a few sentences for truly simple projects), but you MUST present it and get approval.
-
-## Checklist
-
-You MUST create a task for each of these items and complete them in order:
-
-1. **Classify intent** — understand what type of work this is
-2. **Search vault for prior art** — check if something similar was built, decided, or rejected before
-3. **Search web for existing solutions** — don't build what already exists
-4. **Explore project context** — check files, docs, recent commits
-5. **Ask clarifying questions** — one at a time, understand purpose/constraints/success criteria
-6. **Propose 2-3 approaches** — with trade-offs and your recommendation
-7. **Present design** — in sections scaled to their complexity, get user approval after each section
-8. **Capture design decision** — persist the decision to the vault
-9. **Write design doc** — save to `docs/plans/YYYY-MM-DD-<topic>-design.md` and commit
-10. **Transition to implementation** — invoke writing-plans skill to create implementation plan
-
-## Step 0: Classify Intent
-
-Before anything else, understand the type of work:
-
-```
-YOUR_AGENT_core op:route_intent
-  params: { prompt: "<the user's request>" }
-```
-
-This returns the intent type (BUILD, FIX, VALIDATE, DESIGN, IMPROVE, DELIVER) and routing guidance. Use this to focus the brainstorming — a FIX intent needs different questions than a BUILD intent.
-
-## Step 1: Search Before Designing — Vault, Then Web
-
-**BEFORE asking any questions or exploring code**, search for existing knowledge. Follow this order:
-
-### Vault First
-
-```
-YOUR_AGENT_core op:search_intelligent
-  params: { query: "<the feature or idea the user described>" }
-```
-
-Look for:
-
-- **Previous designs** — was this discussed or attempted before?
-- **Architectural decisions** — are there constraints from past decisions?
-- **Patterns** — established approaches in this codebase
-- **Anti-patterns** — approaches that were tried and failed
-
-Browse the knowledge landscape for related context:
-
-```
-YOUR_AGENT_core op:vault_tags
-YOUR_AGENT_core op:vault_domains
-```
-
-Check what the brain says about proven patterns in this domain:
-
-```
-YOUR_AGENT_core op:brain_strengths
-```
-
-Check if other linked projects have solved this:
-
-```
-YOUR_AGENT_core op:memory_cross_project_search
-  params: { query: "<the feature>", crossProject: true }
-```
-
-### Web Search Second
-
-If the vault doesn't have prior art, search the web for:
-
-- **Existing libraries/tools** that solve this problem (don't build what exists)
-- **Reference implementations** in similar projects
-- **Best practices** and established patterns for this type of feature
-- **Known pitfalls** that others have documented
-
-### Present Findings
-
-Present vault + web findings to the user: "Before we design this, here's what I found..." This informs the design conversation and prevents reinventing solutions.
-
-## The Process
-
-**Understanding the idea:**
-
-- Check out the current project state first (files, docs, recent commits)
-- Ask questions one at a time to refine the idea
-- Prefer multiple choice questions when possible, but open-ended is fine too
-- Only one question per message
-- Focus on understanding: purpose, constraints, success criteria
-
-**Exploring approaches:**
-
-- Propose 2-3 different approaches with trade-offs
-- Present options conversationally with your recommendation and reasoning
-- Lead with your recommended option and explain why
-- **Reference vault patterns** — if the vault has a proven approach, lead with it
-- **Reference web findings** — if an existing library solves this, recommend it over custom code
-
-**Presenting the design:**
-
-- Once you understand what you're building, present the design
-- Scale each section to its complexity
-- Ask after each section whether it looks right so far
-- Cover: architecture, components, data flow, error handling, testing
-
-## After the Design
-
-**Capture the design decision to the vault:**
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<feature name> — design decision",
-    description: "<chosen approach, rationale, rejected alternatives>",
-    type: "decision",
-    category: "<relevant domain>",
-    tags: ["<relevant>", "<tags>", "design-decision"]
-  }
-```
-
-This ensures future brainstorming sessions can reference what was decided and why.
-
-**Documentation:**
-
-- Write the validated design to `docs/plans/YYYY-MM-DD-<topic>-design.md`
-- Commit the design document to git
-
-**Implementation:**
-
-- Invoke the writing-plans skill to create a detailed implementation plan
-- Do NOT invoke any other skill. writing-plans is the next step.
-
-## Process Flow
-
-**The terminal state is invoking writing-plans.** Do NOT invoke any other implementation skill. The ONLY skill you invoke after brainstorming is writing-plans.
-
-## Key Principles
-
-- **Classify first** — understand intent before diving in
-- **Vault first** — don't reinvent what's been decided or solved before
-- **Web second** — don't build what already exists as a library
-- **One question at a time** — don't overwhelm with multiple questions
-- **Multiple choice preferred** — easier to answer than open-ended when possible
-- **YAGNI ruthlessly** — remove unnecessary features from all designs
-- **Explore alternatives** — always propose 2-3 approaches before settling
-- **Incremental validation** — present design, get approval before moving on
-- **Capture decisions** — every design decision gets persisted to the vault
-- **Cross-project learning** — check if other projects solved this already
-- **Be flexible** — go back and clarify when something doesn't make sense
-
-## Agent Tools Reference
-
-| Op                             | When to Use                                  |
-| ------------------------------ | -------------------------------------------- |
-| `route_intent`                 | Classify the type of work (BUILD, FIX, etc.) |
-| `search_intelligent`           | Search vault for prior art                   |
-| `vault_tags` / `vault_domains` | Browse knowledge landscape                   |
-| `brain_strengths`              | Check proven patterns                        |
-| `memory_cross_project_search`  | Check if other projects solved this          |
-| `capture_knowledge`            | Persist design decision to vault             |

package/dist/skills/code-patrol.md

@@ -1,178 +0,0 @@
----
-name: code-patrol
-description: Use when the user asks "review this code", "check this against patterns", "code patrol", "does this follow our rules", "validate against vault", "check for anti-patterns", or wants code reviewed not against generic lint rules but against the project's own captured patterns, anti-patterns, and conventions.
----
-
-# Code Patrol — Review Code Against Your Own Knowledge
-
-Review code against the vault's patterns, anti-patterns, and project conventions — not generic lint rules, but YOUR team's captured knowledge applied to new code. Catches violations that no linter knows about.
-
-## When to Use
-
-- Before committing or creating a PR
-- "Does this follow our patterns?"
-- "Check this code against our rules"
-- Code review with institutional knowledge
-- After writing implementation code
-
-## The Magic: Project-Specific Code Intelligence
-
-### Step 1: Understand the Code's Domain
-
-Classify what domain this code belongs to:
-
-```
-YOUR_AGENT_core op:route_intent
-  params: { prompt: "Code review: <brief description of the code>" }
-```
-
-Determine which vault domains are relevant:
-
-```
-YOUR_AGENT_core op:vault_domains
-```
-
-### Step 2: Load Relevant Patterns
-
-Search for patterns in the code's domain:
-
-```
-YOUR_AGENT_core op:search_intelligent
-  params: { query: "<what this code does>" }
-```
-
-Search specifically for anti-patterns to check against:
-
-```
-YOUR_AGENT_core op:search
-  params: { type: "anti-pattern" }
-```
-
-Search for critical rules that must not be violated:
-
-```
-YOUR_AGENT_core op:search
-  params: { severity: "critical" }
-```
-
-Load project-specific rules:
-
-```
-YOUR_AGENT_core op:project_list_rules
-```
-
-```
-YOUR_AGENT_core op:get_behavior_rules
-```
-
-Get proven approaches from the brain:
-
-```
-YOUR_AGENT_core op:brain_strengths
-```
-
-### Step 3: Review the Code
-
-With vault patterns loaded, review the code checking for:
-
-| Check                                  | Source                        | Severity      |
-| -------------------------------------- | ----------------------------- | ------------- |
-| Violates a critical rule               | `search (severity: critical)` | Must fix      |
-| Matches a known anti-pattern           | `search (type: anti-pattern)` | Must fix      |
-| Doesn't follow a proven pattern        | `brain_strengths`             | Should fix    |
-| Breaks project conventions             | `project_list_rules`          | Should fix    |
-| Misses an opportunity to use a pattern | `search_intelligent`          | Could improve |
-
-### Step 4: Present the Review
-
-```
-## Code Patrol Report
-
-### Must Fix (Critical)
-- **[Rule name]**: [What's wrong and why]
-  Vault ref: [entry title] (severity: critical)
-  Fix: [How to fix it]
-
-### Should Fix (Warning)
-- **[Anti-pattern name]**: [What's wrong]
-  Vault ref: [entry title] (type: anti-pattern)
-  Better approach: [The pattern to follow]
-
-### Could Improve (Suggestion)
-- **[Pattern opportunity]**: [The code works but could benefit from...]
-  Vault ref: [entry title] (type: pattern)
-
-### Looks Good
-- [What the code does well — patterns it follows correctly]
-
-### Summary
-X critical issues, Y warnings, Z suggestions
-Patterns followed: [list]
-Patterns missed: [list]
-```
-
-### Step 5: Learn From the Review
-
-If the review reveals a new pattern or anti-pattern not in the vault, capture it:
-
-```
-YOUR_AGENT_core op:capture_quick
-  params: {
-    title: "<new pattern or anti-pattern discovered>",
-    description: "<what it is, when it applies>"
-  }
-```
-
-If the review reveals a knowledge gap, note it:
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<missing convention>",
-    description: "<this should be documented as a project rule>",
-    type: "principle",
-    category: "<domain>",
-    tags: ["convention", "code-review"]
-  }
-```
-
-### Step 6: Verify After Fixes
-
-After the user applies fixes, re-run the patrol to confirm clean:
-
-```
-YOUR_AGENT_core op:search_intelligent
-  params: { query: "<re-check the specific violations>" }
-```
-
-Check system health:
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-## The Magic
-
-This feels like magic because:
-
-1. It's not ESLint — it catches things like "we decided not to use inheritance here" or "this API pattern caused production issues last month"
-2. The rules come from YOUR team's experience, not a generic config file
-3. It gets smarter over time — every captured pattern becomes a new check
-4. It catches institutional knowledge violations that no static analyzer can
-
-A linter checks syntax. Code patrol checks wisdom.
-
-## Agent Tools Reference
-
-| Op                   | When to Use                                   |
-| -------------------- | --------------------------------------------- |
-| `route_intent`       | Classify the code's domain                    |
-| `vault_domains`      | See which domains are relevant                |
-| `search_intelligent` | Find relevant patterns for this code          |
-| `search`             | Find anti-patterns and critical rules         |
-| `project_list_rules` | Project-specific conventions                  |
-| `get_behavior_rules` | Behavioral rules                              |
-| `brain_strengths`    | Proven patterns to check against              |
-| `capture_quick`      | Capture new patterns discovered during review |
-| `capture_knowledge`  | Capture new conventions                       |
-| `admin_health`       | Post-review health check                      |

package/dist/skills/context-resume.md

@@ -1,146 +0,0 @@
----
-name: context-resume
-description: Use when starting a new session, returning to work, or when the user asks "what was I working on", "where did I leave off", "catch me up", "morning standup", "resume", "what's the status". Reconstructs full working context from memory, plans, and sessions.
----
-
-# Context Resume — Pick Up Where You Left Off
-
-Reconstruct your full working context in seconds. Chains memory, plans, sessions, and brain to rebuild exactly where you left off — even across session boundaries and context compactions.
-
-## When to Use
-
-- Starting a new Claude Code session
-- Returning after a break
-- "What was I working on?"
-- "Morning standup"
-- After context compaction (session_capture fires automatically, this reads it back)
-
-## The Magic: Full Context Reconstruction
-
-### Step 1: Load Active Plans
-
-Check for plans in progress — these are your active work streams:
-
-```
-YOUR_AGENT_core op:plan_stats
-```
-
-For each active plan, load its details and task status:
-
-```
-YOUR_AGENT_core op:get_plan
-YOUR_AGENT_core op:plan_list_tasks
-  params: { planId: "<id>" }
-```
-
-Present:
-
-- Plan objective and current status
-- Which tasks are completed, in progress, or pending
-- What's next to do
-
-### Step 2: Search Recent Memory
-
-Load the latest session summaries — these capture what happened before:
-
-```
-YOUR_AGENT_core op:memory_search
-  params: { query: "session summary" }
-```
-
-```
-YOUR_AGENT_core op:memory_list
-```
-
-Also check recent vault captures — what knowledge was added recently?
-
-```
-YOUR_AGENT_core op:vault_recent
-```
-
-### Step 3: Check Active Loops
-
-See if there's a validation loop in progress:
-
-```
-YOUR_AGENT_core op:loop_is_active
-```
-
-If active:
-
-```
-YOUR_AGENT_core op:loop_status
-```
-
-This tells you if an iterative workflow (TDD, debugging, migration) was mid-flight.
-
-### Step 4: Brain Snapshot
-
-Get the latest brain insights relevant to current work:
-
-```
-YOUR_AGENT_core op:brain_strengths
-```
-
-### Step 5: System Health
-
-Quick health check to make sure everything is working:
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-## Presenting the Resume
-
-Format as a concise standup:
-
-```
-## Where You Left Off
-
-**Active Plans:**
-- [Plan name] — X/Y tasks complete, next: [task description]
-
-**Last Session:**
-- [Summary from memory — what was done, key decisions]
-
-**Recent Captures:**
-- [New patterns/anti-patterns added to vault]
-
-**Active Loops:**
-- [Any in-progress validation loops]
-
-**Brain Says:**
-- [Top relevant patterns for current work]
-
-**Health:** [OK / Issues found]
-
-## Recommended Next Step
-[Based on active plans and last session context]
-```
-
-## The Magic
-
-This feels like magic because the user just says "catch me up" and the agent:
-
-1. Knows what plans are active and where they stand
-2. Remembers what happened last session (even across context compactions)
-3. Shows what knowledge was recently captured
-4. Detects in-flight loops
-5. Recommends what to work on next
-
-No other tool does this — the agent has genuine persistent memory.
-
-## Agent Tools Reference
-
-| Op                | When to Use                 |
-| ----------------- | --------------------------- |
-| `plan_stats`      | Find active plans           |
-| `get_plan`        | Load plan details           |
-| `plan_list_tasks` | See task status within plan |
-| `memory_search`   | Find session summaries      |
-| `memory_list`     | Browse recent memories      |
-| `vault_recent`    | Recently captured knowledge |
-| `loop_is_active`  | Check for in-flight loops   |
-| `loop_status`     | Get loop details            |
-| `brain_strengths` | Relevant proven patterns    |
-| `admin_health`    | System health check         |

package/dist/skills/deliver-and-ship.md

@@ -1,123 +0,0 @@
----
-name: deliver-and-ship
-description: >
-  Use when the user says "ship it", "ready to deploy", "package", "release",
-  "pre-PR check", "delivery checklist", "is this ready", "final review", or mentions
-  shipping, deploying, packaging, or releasing work. Runs pre-delivery quality gates
-  to ensure nothing ships without passing stability, knowledge capture, and code quality checks.
----
-
-# Deliver & Ship — Quality Gate Runner
-
-Run all pre-delivery quality gates before shipping. This ensures nothing leaves without passing stability checks, knowledge capture, and code quality verification.
-
-## When to Use
-
-When work is considered "done" and ready to be committed, PR'd, or deployed. This is the last checkpoint before code leaves the developer's hands.
-
-## Orchestration Sequence
-
-### Step 1: Code Quality
-
-Run the project's linter, formatter, and type checker on all modified files:
-
-1. Check for lint/format scripts in `package.json` (or equivalent)
-2. Run `typecheck` / `tsc --noEmit` if TypeScript
-3. Run any project-specific quality gates (clippy for Rust, mypy for Python, etc.)
-
-Any type error or lint failure is a blocker.
-
-### Step 2: Test Suite
-
-Run the full test suite to catch regressions:
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-Verify the agent itself is healthy, then run project tests. All tests must pass.
-
-### Step 3: Stability Assessment
-
-Classify the changes as safe or breaking:
-
-- **Safe**: Internal refactors, bug fixes, additive features (new exports, new ops)
-- **Breaking**: Removed exports, changed signatures, renamed public APIs, schema migrations
-- Breaking changes need migration guidance in the commit/PR description
-
-### Step 4: Knowledge Audit
-
-Check if patterns discovered during this work session should be captured before shipping:
-
-```
-YOUR_AGENT_core op:memory_search
-  params: { query: "current session" }
-```
-
-```
-YOUR_AGENT_core op:brain_stats
-```
-
-Look for:
-
-- Bug fixes that reveal an anti-pattern worth capturing
-- New patterns that should be in the vault for next time
-- Architectural decisions that need documenting
-
-Uncaptured knowledge is lost knowledge. If something should be captured:
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<what was learned>",
-    description: "<the pattern or anti-pattern>",
-    type: "pattern",
-    tags: ["<relevant-tags>"]
-  }
-```
-
-### Step 5: Commit Quality
-
-Verify commit messages follow conventional commits:
-
-- `feat:` for new features
-- `fix:` for bug fixes
-- `refactor:` for refactors
-- `chore:` for maintenance
-- No AI attribution (blocked by engine rules)
-
-### Step 6: Delivery Report
-
-Present a checklist:
-
-- [ ] Code quality: pass/fail (Step 1)
-- [ ] Tests: pass/fail (Step 2)
-- [ ] Stability: safe change / breaking change (Step 3)
-- [ ] Knowledge: captured / needs capture (Step 4)
-- [ ] Commits: clean / needs cleanup (Step 5)
-
-All items must pass before recommending "ship it."
-
-## Domain-Specific Gates
-
-Agents with domain-specific facades may add extra gates. For example:
-
-- **Design system agents**: token validation, contrast checks, accessibility audit
-- **API agents**: schema validation, backward compatibility checks
-- **Security agents**: dependency audit, secret scanning
-
-These are additive — they don't replace the generic gates above.
-
-## Exit Criteria
-
-Delivery is approved when all gates pass. If any gate fails, report the failure and recommend fixes before shipping. Never approve delivery with blocking issues.
-
-## Agent Tools Reference
-
-| Op | When to Use |
-|----|-------------|
-| `admin_health` | Verify agent/system health |
-| `memory_search` | Check for uncaptured session knowledge |
-| `brain_stats` | Review learning state |
-| `capture_knowledge` | Persist patterns before shipping |
-| `capture_quick` | Fast capture for simple learnings |