@soleri/forge 9.0.0 → 9.0.1

package/dist/skills/env-setup.md

@@ -1,151 +0,0 @@
----
-name: env-setup
-description: >
-  Use when a developer needs to set up, fix, or restore a local development environment.
-  Triggers on post-clone setup, project onboarding, first-time running a repo, pulled changes
-  that broke the build, missing or misconfigured dependencies, MODULE_NOT_FOUND or Cannot find
-  module errors, gyp ERR or native module build failures, missing .env files or unknown required
-  environment variables, database setup, Docker compose issues, or connection refused during
-  local dev. Covers Node.js, Python, Rust, Go, Ruby, PHP, and Docker-based projects.
----
-
-# Environment Setup
-
-Detect what a project needs, diagnose what's missing, and produce an actionable setup checklist.
-
-## Overview
-
-Scan the project root for configuration files, detect the tech stack and dependencies, identify gaps between what's required and what's present, then generate ordered setup steps. Offer to execute each step.
-
-## When to Use
-
-- Just cloned a repo and need to get it running
-- Getting errors after pulling changes (missing deps, env vars, DB migrations)
-- Onboarding to an unfamiliar project
-- Setting up a project on a new machine
-- Docker/container environment not starting
-- Missing `.env` file or environment variables
-
-## Detection Phase
-
-Scan the project root and identify:
-
-### Package Managers & Dependencies
-
-| File | Stack | Install Command |
-|------|-------|-----------------|
-| `package.json` | Node.js | `npm install` / `yarn` / `pnpm install` (check for lockfile) |
-| `requirements.txt` | Python | `pip install -r requirements.txt` |
-| `pyproject.toml` | Python | `pip install -e .` or `poetry install` or `uv sync` |
-| `Pipfile` | Python | `pipenv install` |
-| `Cargo.toml` | Rust | `cargo build` |
-| `go.mod` | Go | `go mod download` |
-| `Gemfile` | Ruby | `bundle install` |
-| `composer.json` | PHP | `composer install` |
-
-**Lockfile priority:** If a lockfile exists (`package-lock.json`, `yarn.lock`, `pnpm-lock.yaml`, `Pipfile.lock`, `poetry.lock`), use the matching package manager. Don't mix.
-
-### Environment Variables
-
-1. Check for `.env.example`, `.env.sample`, `.env.template`
-2. Check for existing `.env` — if missing, copy from template
-3. Parse template for required variables (lines without defaults or with placeholder values)
-4. Flag variables that need real values (API keys, secrets, database URLs)
-5. **If no template exists:** grep source for `process.env.`, `os.environ`, `env::var`, `os.Getenv` to discover env vars the project actually uses.
-
-### Native Dependencies
-
-| Indicator | What It Means |
-|-----------|--------------|
-| `better-sqlite3`, `sqlite3` in deps | Needs C++ compiler |
-| `node-gyp` in deps or scripts | Needs Python 3 + C++ toolchain |
-| `sharp` in deps | Needs `libvips` |
-| `Cargo.toml` with `[build-dependencies]` | Needs Rust toolchain for build scripts |
-| `setup.py` with `ext_modules` | Needs C compiler for Python extensions |
-
-### Databases
-
-| File/Config | Database | Setup Needed |
-|-------------|----------|-------------|
-| `docker-compose.yml` with postgres/mysql | PostgreSQL/MySQL | Container + migrations |
-| `prisma/schema.prisma` | Prisma-managed | `npx prisma migrate dev` |
-| `drizzle.config.*` | Drizzle-managed | `npx drizzle-kit push` |
-| `alembic.ini` | SQLAlchemy | `alembic upgrade head` |
-| `config/database.yml` | Rails | `rails db:create db:migrate` |
-
-### Infrastructure
-
-| File | What It Means |
-|------|--------------|
-| `docker-compose.yml` | Services to start with `docker compose up` |
-| `Dockerfile` | Can build container locally |
-| `Makefile` | Check for `setup`, `install`, `dev` targets |
-| `.tool-versions` / `.node-version` / `.nvmrc` | Required runtime version |
-| `turbo.json` / `nx.json` / `lerna.json` | Monorepo setup |
-
-### IDE & Tool Integration
-
-| File | Integration |
-|------|------------|
-| `.vscode/` | VS Code settings, extensions |
-| `.mcp.json` / `mcp.json` | MCP server config |
-| `.editorconfig` | Cross-editor formatting |
-
-## Diagnosis Phase
-
-After detection, check what's present vs needed:
-
-1. **Runtime version** — does installed version match version files?
-2. **Dependencies installed?** — does `node_modules/`, `venv/`, `vendor/` exist?
-3. **Native build tools?** — are compilers available?
-4. **Env file present?** — does `.env` exist when a template does?
-5. **Database reachable?** — can the configured DB URL connect?
-6. **Docker running?** — is Docker daemon running if needed?
-7. **Build artifacts** — does the project need an initial build step?
-
-## Checklist Generation
-
-Produce steps in dependency order:
-
-```
-## Setup Checklist
-
-1. [ ] Install runtime (Node 20.x via nvm)
-2. [ ] Install dependencies (pnpm install)
-3. [ ] Copy environment file (cp .env.example .env)
-4. [ ] Fill in required env vars: DATABASE_URL, API_KEY
-5. [ ] Start Docker services (docker compose up -d)
-6. [ ] Run database migrations (npx prisma migrate dev)
-7. [ ] Build the project (pnpm build)
-8. [ ] Start dev server (pnpm dev)
-```
-
-**Order matters:** runtime → deps → env → infrastructure → migrations → build → run.
-
-After presenting the checklist, offer: "Want me to run these steps for you?"
-
-## Execution Phase
-
-If the user says yes, execute steps sequentially. Stop and ask if:
-
-- A step fails
-- A step requires manual input (API keys, passwords)
-- A step would modify system-level config (global installs, PATH changes)
-
-## Monorepo Handling
-
-If monorepo detected (turbo.json, nx.json, pnpm-workspace.yaml):
-
-1. Install root dependencies first
-2. Ask which package/app the user wants to work on
-3. Check for package-specific setup
-4. Run package-specific setup after root
-
-## Common Mistakes
-
-- **Wrong package manager** — using `npm install` when `yarn.lock` exists. Always check lockfiles first.
-- **Skipping env file** — project crashes on first API call. Always check for templates.
-- **Missing native build tools** — `npm install` fails with gyp errors. Check before installing.
-- **Missing runtime version** — subtle bugs from wrong Node/Python version.
-- **Docker not running** — cryptic "connection refused" errors.
-- **Stale dependencies** — after `git pull`, always re-install if lockfile changed.

package/dist/skills/executing-plans.md

@@ -1,216 +0,0 @@
----
-name: executing-plans
-description: Use when you have a written implementation plan to execute in a separate session with review checkpoints
----
-
-<!-- Adapted from superpowers (MIT License) -->
-
-# Executing Plans
-
-## Overview
-
-Load plan, review critically, execute tasks in batches, report for review between batches.
-
-**Core principle:** Batch execution with checkpoints for architect review.
-
-**Announce at start:** "I'm using the executing-plans skill to implement this plan."
-
-## The Process
-
-### Step 1: Load and Review Plan
-
-First, load the tracked plan from the agent:
-
-```
-YOUR_AGENT_core op:get_plan
-```
-
-List all tasks to understand scope:
-
-```
-YOUR_AGENT_core op:plan_list_tasks
-  params: { planId: "<id>" }
-```
-
-Check plan stats for an overview:
-
-```
-YOUR_AGENT_core op:plan_stats
-```
-
-If no tracked plan exists, read the plan file from `docs/plans/`.
-
-Review critically — identify any questions or concerns about the plan.
-
-- If concerns: Raise them with your human partner before starting
-- If no concerns: Create TodoWrite and proceed
-
-### Step 2: Start Execution Loop
-
-For iterative tasks, start a validation loop:
-
-```
-YOUR_AGENT_core op:loop_start
-  params: { prompt: "<plan objective>", mode: "custom" }
-```
-
-The loop tracks iterations and validates progress automatically.
-
-### Step 3: Execute Batch
-
-**Default: First 3 tasks**
-
-For each task:
-
-1. Mark as in_progress:
-   ```
-   YOUR_AGENT_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "in_progress" }
-   ```
-2. Follow each step exactly (plan has bite-sized steps)
-3. Run verifications as specified
-4. Mark as completed:
-   ```
-   YOUR_AGENT_core op:update_task
-     params: { planId: "<id>", taskIndex: <n>, status: "completed" }
-   ```
-
-After each task, iterate the loop:
-
-```
-YOUR_AGENT_core op:loop_iterate
-```
-
-### Step 4: Report
-
-When batch complete:
-
-- Show what was implemented
-- Show verification output
-- Check loop status:
-  ```
-  YOUR_AGENT_core op:loop_status
-  ```
-- Say: "Ready for feedback."
-
-### Step 5: Continue
-
-Based on feedback:
-
-- Apply changes if needed
-- Execute next batch
-- Repeat until complete
-
-### Step 6: Complete Development
-
-After all tasks complete and verified:
-
-1. Run final verification (use verification-before-completion skill)
-
-2. Complete the validation loop:
-
-   ```
-   YOUR_AGENT_core op:loop_complete
-   ```
-
-3. Reconcile plan — compare what was planned vs what actually happened:
-
-   ```
-   YOUR_AGENT_core op:plan_reconcile
-     params: {
-       planId: "<id>",
-       actualSteps: "<description of what was actually done>",
-       driftNotes: "<what differed from the plan>"
-     }
-   ```
-
-4. Complete plan lifecycle — extract knowledge and archive:
-
-   ```
-   YOUR_AGENT_core op:plan_complete_lifecycle
-     params: { planId: "<id>" }
-   ```
-
-5. Archive the plan for historical reference:
-
-   ```
-   YOUR_AGENT_core op:plan_archive
-     params: { planId: "<id>" }
-   ```
-
-6. Capture a session summary:
-   ```
-   YOUR_AGENT_core op:session_capture
-     params: { summary: "<what was built, key decisions, files modified>" }
-   ```
-
-## Capture Learnings During Execution
-
-If you discover something worth remembering during execution (a gotcha, a better approach, an anti-pattern):
-
-```
-YOUR_AGENT_core op:capture_quick
-  params: {
-    title: "<what you learned>",
-    description: "<context, why it matters, when it applies>"
-  }
-```
-
-Don't wait until the end — capture insights as they happen.
-
-## When to Stop and Ask for Help
-
-**STOP executing immediately when:**
-
-- Hit a blocker mid-batch (missing dependency, test fails, instruction unclear)
-- Plan has critical gaps preventing starting
-- You don't understand an instruction
-- Verification fails repeatedly
-
-**Ask for clarification rather than guessing.**
-
-## When to Revisit Earlier Steps
-
-**Return to Review (Step 1) when:**
-
-- Partner updates the plan based on your feedback
-- Fundamental approach needs rethinking
-
-**Don't force through blockers** - stop and ask.
-
-## Remember
-
-- Review plan critically first
-- Follow plan steps exactly
-- Don't skip verifications
-- Between batches: just report and wait
-- Stop when blocked, don't guess
-- Capture learnings as you go, not just at the end
-- Always reconcile the plan after execution — drift data makes future plans better
-- Never start implementation on main/master branch without explicit user consent
-
-## Agent Tools Reference
-
-| Op                        | When to Use                                   |
-| ------------------------- | --------------------------------------------- |
-| `get_plan`                | Load tracked plan                             |
-| `plan_list_tasks`         | List all tasks in the plan                    |
-| `plan_stats`              | Plan overview and metrics                     |
-| `update_task`             | Mark tasks in_progress / completed            |
-| `loop_start`              | Begin validation loop for iterative execution |
-| `loop_iterate`            | Track each iteration                          |
-| `loop_status`             | Check loop progress                           |
-| `loop_complete`           | Finish validation loop                        |
-| `plan_reconcile`          | Compare planned vs actual (post-execution)    |
-| `plan_complete_lifecycle` | Extract knowledge from execution              |
-| `plan_archive`            | Archive plan for history                      |
-| `session_capture`         | Save session context                          |
-| `capture_quick`           | Capture mid-execution learnings               |
-
-## Integration
-
-**Required workflow skills:**
-
-- writing-plans — Creates the plan this skill executes
-- verification-before-completion — Verify work before claiming completion
-- test-driven-development — Follow TDD for each implementation step

package/dist/skills/fix-and-learn.md

@@ -1,167 +0,0 @@
----
-name: fix-and-learn
-description: Use AFTER systematic-debugging completes to execute the fix and capture the learning in the vault. Invoke this skill when moving from diagnosis to repair for bugs, broken behavior, errors, regressions, or unexpected results. Chains with systematic-debugging — debugging finds root cause, this skill fixes and captures the anti-pattern.
----
-
-# Fix & Learn — Debug, Repair, Capture
-
-Fix bugs through a structured recovery workflow, then capture the root cause as a reusable anti-pattern. The learning step is what makes fixes compound across sessions.
-
-## When to Use
-
-Any time something is broken, behaving unexpectedly, or producing errors. This includes runtime bugs, visual regressions, type errors, and "it used to work" situations.
-
-## The Search Order — MANDATORY
-
-**Never jump to writing code.** Always follow this lookup order:
-
-1. **Vault first** — has this been solved before?
-2. **Web search** — is there a known solution or pattern?
-3. **Plan the fix** — design the approach before touching code
-4. **Implement** — only after steps 1-3
-
-Skipping to implementation is the #1 cause of wasted time and recurring bugs.
-
-## Orchestration Sequence
-
-### Step 1: Classify and Route
-
-Classify the intent to confirm this is a FIX and get routing context:
-
-```
-YOUR_AGENT_core op:route_intent
-  params: { prompt: "<user's bug description>" }
-```
-
-### Step 2: Check Vault First
-
-Search for this bug or similar issues:
-
-```
-YOUR_AGENT_core op:search_intelligent
-  params: { query: "<error message or bug description>" }
-```
-
-Check memory for patterns across sessions:
-
-```
-YOUR_AGENT_core op:memory_search
-  params: { query: "<bug description>" }
-```
-
-Check memory topics — are bugs clustering in a specific area?
-
-```
-YOUR_AGENT_core op:memory_topics
-```
-
-Check memory stats to understand the debugging landscape:
-
-```
-YOUR_AGENT_core op:memory_stats
-```
-
-If vault returns a match with high confidence — **use it**. Don't re-investigate what's already been solved.
-
-### Step 3: Search the Web
-
-If the vault has no answer, search for existing solutions before investigating from scratch:
-
-- Known issues in the library/framework
-- Stack Overflow answers for the exact error
-- GitHub issues on relevant repos
-- Official documentation for the API or feature involved
-
-A 30-second web search can save hours of investigation.
-
-### Step 4: Start Fix Loop
-
-For complex bugs requiring multiple iterations, start a validation loop:
-
-```
-YOUR_AGENT_core op:loop_start
-  params: { prompt: "Fix: <bug description>", mode: "custom" }
-```
-
-### Step 5: Diagnose and Fix
-
-Only if Steps 2-3 didn't produce a solution, apply the systematic debugging approach (use systematic-debugging skill):
-
-1. Reproduce the issue
-2. Isolate the root cause
-3. **Plan the fix before writing code** — even a one-line mental plan
-4. Implement the fix
-5. Verify the fix resolves the issue without regressions
-
-Track each iteration:
-
-```
-YOUR_AGENT_core op:loop_iterate
-```
-
-### Step 6: Validate the Fix
-
-Run the project's test suite to ensure the fix didn't introduce regressions. Use the verification-before-completion skill to confirm all checks pass.
-
-Complete the loop when validated:
-
-```
-YOUR_AGENT_core op:loop_complete
-```
-
-### Step 7: Capture the Learning
-
-This step is critical — it's what makes the agent smarter over time.
-
-```
-YOUR_AGENT_core op:capture_knowledge
-  params: {
-    title: "<bug title>",
-    description: "<root cause, solution, what made it hard to find>",
-    type: "anti-pattern",
-    category: "<domain>",
-    tags: ["<error-type>", "<component>"]
-  }
-```
-
-For quick captures:
-
-```
-YOUR_AGENT_core op:capture_quick
-  params: { title: "<bug>", description: "<root cause and fix>" }
-```
-
-### Step 8: Post-Capture Quality
-
-Run duplicate detection to ensure we didn't create redundant entries:
-
-```
-YOUR_AGENT_core op:curator_detect_duplicates
-```
-
-### Step 9: Verify Health
-
-```
-YOUR_AGENT_core op:admin_health
-```
-
-## Exit Criteria
-
-Fix is complete when: the bug is resolved, tests pass (Step 6), and the root cause is captured in vault (Step 7). A fix without a capture is an incomplete fix.
-
-## Agent Tools Reference
-
-| Op                          | When to Use                    |
-| --------------------------- | ------------------------------ |
-| `route_intent`              | Classify as FIX intent         |
-| `search_intelligent`        | Check vault for known bugs     |
-| `memory_search`             | Search across session memories |
-| `memory_topics`             | See if bugs cluster in an area |
-| `memory_stats`              | Understand debugging landscape |
-| `loop_start`                | Begin iterative fix cycle      |
-| `loop_iterate`              | Track each fix attempt         |
-| `loop_complete`             | Finish fix cycle               |
-| `capture_knowledge`         | Full anti-pattern capture      |
-| `capture_quick`             | Fast capture                   |
-| `curator_detect_duplicates` | Prevent redundant entries      |
-| `admin_health`              | Verify system health           |