@slamb2k/mad-skills 2.0.7 → 2.0.8

package/skills/build/instructions.md

@@ -1,293 +0,0 @@
-# Build Instructions
-
-Execute a detailed design/plan through the full feature-dev lifecycle with
-maximum context isolation. Every heavy stage runs in a subagent so the primary
-conversation only accumulates structured reports.
-
-Stage prompts: `references/stage-prompts.md`
-Report budgets: `references/report-contracts.md`
-Agent selection: `references/architecture-notes.md`
-Project detection: `references/project-detection.md`
-
-## Flags
-
-Parse optional flags from the request:
-- `--skip-questions`: Skip Stage 2 (clarifying questions)
-- `--skip-review`: Skip Stage 5 (code review)
-- `--no-ship`: Stop after Stage 8 docs update
-- `--parallel-impl`: Split implementation into parallel agents when independent
-
----
-
-## Pre-flight
-
-Before starting, check all dependencies in this table:
-
-| Dependency | Type | Check | Required | Resolution | Detail |
-|-----------|------|-------|----------|------------|--------|
-| ship | skill | `.claude/skills/ship/SKILL.md` | yes | stop | Install with: npx @slamb2k/mad-skills --skill ship |
-| feature-dev:code-explorer | agent | — | no | fallback | Uses general-purpose agent |
-| feature-dev:code-architect | agent | — | no | fallback | Uses general-purpose agent |
-| feature-dev:code-reviewer | agent | — | no | fallback | Uses general-purpose agent |
-
-For each row, in order:
-1. Run the Check command (for cli/npm) or test file existence (for agent/skill)
-2. If found: continue silently
-3. If missing: apply Resolution strategy
-   - **stop**: notify user with Detail, halt execution
-   - **url**: notify user with Detail (install link), halt execution
-   - **install**: notify user, run the command in Detail, continue if successful
-   - **ask**: notify user, offer to run command in Detail, continue either way (or halt if required)
-   - **fallback**: notify user with Detail, continue with degraded behavior
-4. After all checks: summarize what's available and what's degraded
-
-1. Capture **PLAN** (the user's argument) and **FLAGS**
-2. Detect project type using `references/project-detection.md` to populate
-   **PROJECT_CONFIG** (language, test_runner, test_setup)
-3. Check for outstanding questions from previous work:
-   - Search CLAUDE.md for a "Known Issues" or "Open Questions" section
-   - Search `goals/` for files containing "open_question" or "unresolved"
-   - Search memory (if available) for recent items of type "task" or
-     "open_question" that are unresolved
-   - Check for `DEBRIEF_ITEMS` in any recent build logs
-4. If outstanding items found, present via AskUserQuestion:
-   ```
-   "Found {count} outstanding items from previous work:"
-   {numbered list with summary of each}
-   "Address any of these before starting the build?"
-   ```
-   Options:
-   - **"Yes, let me choose which ones"** → present each; options:
-     "Incorporate into this build" / "Skip for now" / "Explain more"
-     Items marked "incorporate" get appended to the PLAN as additional
-     requirements for Stage 1 to explore.
-   - **"No, proceed with the build"** → continue normally
-5. Create a task list tracking all stages
-
----
-
-## Stage 1: Explore
-
-Launch **feature-dev:code-explorer** (fallback: general-purpose):
-
-```
-Task(
-  subagent_type: "feature-dev:code-explorer",
-  description: "Explore codebase for build plan",
-  prompt: <read from references/stage-prompts.md#stage-1>
-)
-```
-
-Substitute `{PLAN}` into the prompt.
-Parse EXPLORE_REPORT. Extract `questions` for Stage 2.
-
----
-
-## Stage 2: Clarifying Questions
-
-**Skip if `--skip-questions` or no questions found.**
-
-Runs on the **primary thread** (requires user interaction).
-
-1. Review EXPLORE_REPORT `questions` and `potential_issues`
-2. Present questions to user via AskUserQuestion
-3. Store answers as CLARIFICATIONS
-
----
-
-## Stage 3: Architecture Design
-
-Launch **feature-dev:code-architect** (fallback: general-purpose):
-
-```
-Task(
-  subagent_type: "feature-dev:code-architect",
-  description: "Design implementation architecture",
-  prompt: <read from references/stage-prompts.md#stage-3>
-)
-```
-
-Substitute `{PLAN}`, `{EXPLORE_REPORT}`, `{CLARIFICATIONS}`.
-Parse ARCH_REPORT. Present `approach_summary` to user for confirmation.
-
-If rejected, incorporate feedback and re-run.
-
----
-
-## Stage 4: Implementation
-
-If `--parallel-impl` and ARCH_REPORT has independent `parallel_groups`,
-launch **multiple general-purpose subagents in parallel**.
-
-Otherwise launch **one general-purpose subagent**:
-
-```
-Task(
-  subagent_type: "general-purpose",
-  description: "Implement plan",
-  prompt: <read from references/stage-prompts.md#stage-4>
-)
-```
-
-Substitute `{PLAN}`, `{ARCH_REPORT}`, conventions, `{PROJECT_CONFIG.test_runner}`.
-Parse IMPL_REPORT(s). If any failed, assess retry or abort.
-
----
-
-## Stage 5: Code Review
-
-**Skip if `--skip-review`.**
-
-Launch **3 feature-dev:code-reviewer subagents in parallel** (fallback: general-purpose):
-
-1. Simplicity & DRY
-2. Bugs & Correctness
-3. Conventions & Integration
-
-Prompts in `references/stage-prompts.md#stage-5`.
-
-Consolidate reports. Present **only critical and high severity findings**.
-Ask: "Fix these now, or proceed as-is?"
-
----
-
-## Stage 6: Fix Review Findings
-
-**Only if Stage 5 found issues AND user wants them fixed.**
-
-Launch **general-purpose subagent**:
-
-```
-Task(
-  subagent_type: "general-purpose",
-  description: "Fix review findings",
-  prompt: <read from references/stage-prompts.md#stage-6>
-)
-```
-
----
-
-## Stage 7: Verify
-
-Launch **Bash subagent** (haiku):
-
-```
-Task(
-  subagent_type: "Bash",
-  model: "haiku",
-  description: "Run verification tests",
-  prompt: <read from references/stage-prompts.md#stage-7>
-)
-```
-
-Substitute `{PROJECT_CONFIG.test_runner}` and `{PROJECT_CONFIG.test_setup}`.
-
-If tests fail:
-- First failure: launch general-purpose agent to fix, retry
-- Second failure: report to user and stop
-
----
-
-## Stage 8: Update Progress Documentation
-
-**Skip if EXPLORE_REPORT has no `source_docs`.**
-
-Launch **general-purpose subagent**:
-
-```
-Task(
-  subagent_type: "general-purpose",
-  description: "Update progress documentation",
-  prompt: <read from references/stage-prompts.md#stage-8>
-)
-```
-
-**If `--no-ship`: Stop here and present final summary.**
-
----
-
-## Stage 9: Ship
-
-Invoke the `/ship` skill:
-
-```
-/ship {approach_summary from ARCH_REPORT}. Files: {files from IMPL_REPORT}
-```
-
----
-
-## Stage 10: Debrief
-
-**Always runs** on the primary thread (requires user interaction).
-
-1. Scan all stage reports for unresolved items:
-   - EXPLORE_REPORT: `potential_issues` not addressed by implementation
-   - ARCH_REPORT: `risks` with deferred mitigations
-   - REVIEW_REPORT: `medium`/`low` findings not fixed in Stage 6
-   - TEST_REPORT: warnings, skipped tests, flaky results
-   - DOCS_REPORT: `docs_skipped` items
-   - IMPL_REPORT: `issues_encountered` that were worked around
-
-2. Compile into DEBRIEF_ITEMS (see `references/stage-prompts.md#stage-10`).
-   Categorise each as: unresolved_risk, deferred_fix, open_question,
-   assumption, or tech_debt.
-
-3. **If no items found, skip to Final Report.**
-
-4. Present numbered summary via AskUserQuestion grouped by category.
-   Each item shows: `[category] summary (effort)`.
-
-   Options:
-   - **"Fix now"** → create a task list of resolution activities for
-     each item; present for user confirmation, then work through them
-   - **"Create goals for future sessions"** → write goal files to `goals/`
-     (if GOTCHA structure exists) or append to CLAUDE.md as Known Issues
-   - **"Note and continue"** → acknowledge items without formal tracking;
-     log to memory (if exists) or as source file comments. No further action.
-   - **"Let me choose per item"** → present each individually with full
-     description, evidence, and impact. Options per item:
-     "Fix now" / "Add to goals" / "Explain more" / "Note and continue".
-     "Explain more" reads source files cited in evidence, provides
-     expanded context, then re-presents the item for decision.
-
-5. After resolution, include debrief summary in the Final Report.
-
----
-
-## Final Report
-
-```
-Build complete
-
-  Plan:     {first line of PLAN}
-  Approach: {approach_summary}
-
-  Files modified: {count}
-  Files created:  {count}
-  Tests:          {passed}/{total}
-
-  Docs updated: {count or "none"}
-
-  PR: {pr_url} (merged at {merge_commit})
-
-  Key decisions:
-  - {decision 1}
-  - {decision 2}
-
-  Review findings addressed: {count fixed} / {count found}
-
-  Debrief: {count resolved} / {count surfaced} items addressed
-    {list of items created as goals or tasks, if any}
-```
-
-If any stage failed, report the failure point and what was accomplished.
-
----
-
-## Rollback
-
-If implementation succeeds but later stages fail:
-- Tests fail: fix agent attempts repair, then reports to user
-- Review critical: user decides fix or proceed
-- Ship fails: code is still committed locally; user can manually push
-- Never silently revert completed implementation work

package/skills/distil/instructions.md

@@ -1,255 +0,0 @@
-# Distil Instructions
-
-Generate multiple unique, creative web interface designs for any website or
-web application. The primary agent acts as a thin orchestrator — all heavy
-reading and file creation is delegated to subagents to protect the primary
-context window.
-
-## Arguments
-
-Parse the following from the skill invocation:
-- **count** (required): Number of designs to create (e.g., 5)
-- **--spec** (optional): Path to a file containing site specification
-- **--url** (optional): URL to existing site to review for context
-- **--port** (required): Port for the Vite dev server
-- **--favorites** (optional): Comma-separated list of design numbers for iteration mode
-
-### Examples
-```
-/distil 5 --spec ./site-spec.md --port 5173
-/distil 3 --favorites 2,4 --port 5173
-```
-
-If `--favorites` is provided, follow `references/iteration-mode.md` instead
-of the steps below.
-
----
-
-## Pre-flight
-
-Before starting, check all dependencies in this table:
-
-| Dependency | Type | Check | Required | Resolution | Detail |
-|-----------|------|-------|----------|------------|--------|
-| npm | cli | `npm --version` | yes | stop | https://bun.sh or use npm |
-| bencium-innovative-ux-designer | skill | `~/.claude/skills/bencium-innovative-ux-designer/SKILL.md` | no | ask | `npx skills add bencium/bencium-claude-code-design-skill@bencium-innovative-ux-designer -g -y` |
-| web-animation-design | skill | `~/.claude/skills/web-animation-design/SKILL.md` | no | ask | `npx skills add connorads/dotfiles@web-animation-design -g -y` |
-| design-system | skill | `~/.claude/skills/design-system/SKILL.md` | no | ask | `npx skills add lobbi-docs/claude@design-system -g -y` |
-
-For each row, in order:
-1. Run the Check command (for cli/npm) or test file existence (for agent/skill)
-2. If found: continue silently
-3. If missing: apply Resolution strategy
-   - **stop**: notify user with Detail, halt execution
-   - **url**: notify user with Detail (install link), halt execution
-   - **install**: notify user, run the command in Detail, continue if successful
-   - **ask**: notify user, offer to run command in Detail, continue either way (or halt if required)
-   - **fallback**: notify user with Detail, continue with degraded behavior
-4. After all checks: summarize what's available and what's degraded
-
----
-
-## Site Specification
-
-The specification can be provided via:
-
-1. **--spec flag**: Read the file at the provided path
-2. **Pasted text**: Check conversation for a description of the site
-3. **--url flag**: Use WebFetch to analyze an existing site
-
-**If no specification is found, ask the user before proceeding.**
-
----
-
-## Step 1: Load Site Specification
-
-Parse and store the site context for use when generating each design.
-This is the only file the primary agent reads directly (specs are typically small).
-
-## Step 2: Reconnaissance (launch in parallel)
-
-Launch two subagents **in parallel** to gather context without bloating
-the primary agent.
-
-### 2a: Verify Design Skills
-
-Design skill availability is checked in the Pre-flight section above.
-Use the results from pre-flight to populate SKILL_REPORT:
-- For each design skill: name, installed (yes/no)
-- If any skill was missing and the user declined to install, note it as unavailable
-
-### 2b: Scan Existing Project
-
-```
-Task(
-  subagent_type: "Explore",
-  model: "haiku",
-  description: "Scan existing design project",
-  prompt: "Check if src/designs/ directory exists. If it does:
-    1. List all DesignN.tsx files (glob for src/designs/Design*.tsx)
-    2. For each file, read ONLY the first 10 lines to extract the
-       metadata comment (style name, key traits)
-    3. Determine the highest design number
-    Return PROJECT_REPORT (max 20 lines):
-    - project_exists: true/false
-    - package_manager: detected from lockfile (bun.lockb/pnpm-lock/yarn.lock/package-lock)
-    - design_count: N
-    - highest_number: N
-    - designs: list of (number, style_name) pairs
-    If no src/designs/ directory, return project_exists: false."
-)
-```
-
-### Parse Recon Results
-
-From SKILL_REPORT: Gate on missing skills before proceeding.
-From PROJECT_REPORT:
-- If `project_exists`: set `START_INDEX = highest_number + 1`, skip Step 3
-- If not: set `START_INDEX = 1`, proceed to Step 3
-
-## Step 3: Initialize Project
-
-**Skip this step if an existing project was detected in Step 2b.**
-
-Launch **Bash subagent** (haiku) to set up the project:
-
-```
-Task(
-  subagent_type: "Bash",
-  model: "haiku",
-  description: "Initialize distil project",
-  prompt: "Follow the project setup instructions:
-    1. Detect package manager (bun -> pnpm -> yarn -> npm)
-    2. Create Vite React-TS project
-    3. Install dependencies: tailwindcss, postcss, autoprefixer,
-       react-router-dom, lucide-react
-    4. Configure Tailwind (content paths, index.css directives)
-    5. Copy {skill_dir}/assets/DesignNav.tsx to src/components/DesignNav.tsx
-    Return SETUP_REPORT (max 10 lines): status, package_manager, errors."
-)
-```
-
-Parse SETUP_REPORT. If setup fails, fall back through the package manager
-chain (bun -> pnpm -> yarn -> npm).
-
-## Step 4: Create Designs via Subagent
-
-Launch a **general-purpose subagent** to create all new designs.
-
-**CRITICAL**: The subagent reads skill files and design guides directly.
-Do NOT read them in the primary agent — pass file paths only.
-
-```
-Task(
-  subagent_type: "general-purpose",
-  description: "Create design variations",
-  prompt: "
-    You are creating {COUNT} new web design variations for a distil project.
-
-    ## Site Specification
-    {SITE_SPEC from Step 1}
-
-    ## Design Knowledge — Read These Files
-    Load design principles and the 50+ style catalog from these skill files:
-    - ~/.claude/skills/bencium-innovative-ux-designer/SKILL.md
-    - ~/.claude/skills/bencium-innovative-ux-designer/MOTION-SPEC.md
-    - ~/.claude/skills/web-animation-design/SKILL.md
-    - ~/.claude/skills/design-system/SKILL.md
-    - ~/.claude/skills/design-system/references/style-guide.md
-
-    Also read the project design guide:
-    - {skill_dir}/references/design-guide.md
-
-    ## Existing Designs (avoid these styles)
-    {Compact list from PROJECT_REPORT: number + style_name pairs,
-     or 'None — fresh project'}
-
-    ## Task
-    Create designs numbered {START_INDEX} through {START_INDEX + COUNT - 1}.
-
-    For each design, create `src/designs/Design{N}.tsx`:
-    - Pick a DISTINCT style from the 50+ style catalog in the design-system skill
-    - Do NOT reuse styles already used by existing designs
-    - Apply the site specification to all content and sections
-    - Follow anti-AI-slop rules strictly (no Inter, no default blue, no cookie-cutter layouts)
-    - Include purposeful animations with proper easing
-    - Each design must be self-contained in a single file
-    - Import and render DesignNav from '../components/DesignNav'
-
-    After creating all designs, update:
-    1. `src/App.tsx` — Add import and route for EVERY design (existing + new)
-    2. Each design file's DesignNav `designs` array — Include ALL designs (existing + new)
-
-    ## Design File Requirements
-    Each design file must have:
-    - A metadata comment at the top: style name, key visual traits, color palette
-    - Import DesignNav from '../components/DesignNav'
-    - A `designs` array listing ALL designs (existing + new) with id and name
-    - ALL sections from the site specification with realistic content
-    - Custom color palette (not default Tailwind)
-    - Animations with proper easing (ease-out for entrances, ease-in-out for movement)
-    - Responsive layout (mobile-first)
-    - Lucide React icons for iconography
-
-    ## App.tsx Requirements
-    The App.tsx must:
-    - Import ALL design components (existing + new)
-    - Have a route for each: <Route path='/{N}' element={<DesignN />} />
-    - Default route redirects to /1
-
-    Return DESIGN_REPORT (max 30 lines):
-    - List each design created: number, style name, key visual traits
-    - Total design count (existing + new)
-    - Files created and modified
-    - Any issues encountered
-  "
-)
-```
-
-Parse DESIGN_REPORT. If any design failed, report the error and offer retry.
-
-## Step 5: Start Dev Server
-
-Launch as a **background Bash** to avoid blocking the primary agent:
-
-```
-Task(
-  subagent_type: "Bash",
-  run_in_background: true,
-  description: "Start Vite dev server",
-  prompt: "{package_manager} run dev --port {PORT}"
-)
-```
-
-If the dev server is already running, HMR should pick up the new files
-automatically — skip this step.
-
-## Step 6: Present Designs
-
-Inform the user:
-- Dev server is running at `http://localhost:{PORT}`
-- Each design is available at `/1`, `/2`, `/3`, etc.
-- Briefly describe each design's unique approach (from DESIGN_REPORT)
-- Note which designs are new vs existing (if appending)
-- Remind they can iterate with `--favorites` to refine preferred designs
-
-## Context Protection Summary
-
-| Step | Agent | Model | Why |
-|---|---|---|---|
-| 1: Load spec | Primary | — | Small file, needed for subagent prompt |
-| 2a: Skill check | Explore | haiku | Avoids reading 2000+ lines of skill content |
-| 2b: Project scan | Explore | haiku | Avoids reading existing design files |
-| 3: Init project | Bash | haiku | Shell commands only |
-| 4: Create designs | general-purpose | default | Heavy lifting: reads skills, writes files |
-| 5: Dev server | Bash (background) | — | Non-blocking, no output in primary |
-| 6: Present | Primary | — | User-facing, uses compact DESIGN_REPORT |
-
-## Troubleshooting
-
-- If package manager commands fail, try the next in the fallback chain
-- If port is in use, suggest killing the process or using a different port
-- If design imports fail, check file naming consistency
-- If no site spec is found, always ask the user before proceeding
-- If a design skill is missing, offer to install it before proceeding
-- If the subagent fails, check error details and retry with adjusted parameters

package/skills/prime/instructions.md

@@ -1,73 +0,0 @@
-# Prime Instructions
-
-Load project context to inform agent decisions. Raw file contents stay in a
-subagent — the primary thread only sees a structured PRIME_REPORT.
-
-## Step 1: Parse Arguments
-
-Extract domain hints from the request (comma-separated). Valid domains are
-listed in `references/domains.md`. If no domain specified, load core context only.
-
-## Step 2: Load Context via Subagent
-
-Launch a **general-purpose subagent** to read files and build the report:
-
-```
-Task(
-  subagent_type: "general-purpose",
-  description: "Load and summarise project context",
-  prompt: <see below>
-)
-```
-
-### Subagent Prompt
-
-```
-Load project context and return a structured summary. Raw file contents must
-NOT appear in the report — summarise only.
-
-Limit PRIME_REPORT to 30 lines maximum.
-
-## Core Files (always load)
-
-1. CLAUDE.md — System handbook, operating procedures
-2. goals/manifest.md — Phase status, available goals, project roadmap
-3. tools/manifest.md — Available tools and their locations
-
-If CLAUDE.md is missing, record as NOT FOUND and continue.
-
-## Domain Files
-
-{For each requested domain, list files from references/domains.md}
-
-For each file:
-- If it exists: read and summarise (2-3 lines max per domain)
-- If it doesn't exist: record as NOT FOUND and continue
-
-## Output Format
-
-PRIME_REPORT:
-- core_files_loaded: {count}/{total}
-- missing_files: {list or "none"}
-- domains_loaded: {list}
-- per_domain_summary:
-  - {domain}: {2-3 line summary}
-- branch: {current branch from git branch --show-current}
-- ready_for: {inferred from loaded context}
-```
-
-## Step 3: Present Summary
-
-Parse PRIME_REPORT and present a clean summary to the user:
-
-```
-Context loaded:
-- Core: {status from core_files_loaded}
-- {Domain}: {summary from per_domain_summary}
-
-Current branch: {branch}
-Ready to assist with: {ready_for}
-```
-
-If CLAUDE.md was missing, warn the user and note that only domain context
-was loaded.