@withmata/blueprints 0.2.0 → 0.3.1

package/{.opencode/commands/audit.md → .claude/skills/audit/SKILL.md}

@@ -1,5 +1,7 @@
 ---
-description: Run a project health check against available blueprints
+name: audit
+description: Run a project health check against available blueprints (read-only analysis)
+allowed-tools: Read, Glob, Grep, Bash(git *), Bash(ls *)
 ---
 
 # Project Audit
@@ -11,18 +13,18 @@ Run a health check against available blueprints. Analyze this project's current
 Load all available blueprint specs to understand what is possible:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/features/auth-better-auth/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/features/auth-better-auth/BLUEPRINT.md
 ```
 
 Also scan for any additional feature blueprints:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/features/*/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/features/*/BLUEPRINT.md
 ```
 
-Only consider a blueprint "available" if its BLUEPRINT.md has `Status: Complete`. If not found at these paths, ask the user for the path to their blueprints repo.
+Only consider a blueprint "available" if its BLUEPRINT.md has `Status: Complete`. If not found, run `npx @withmata/blueprints` to install.
 
 ## Step 2: Read Project Context
 

package/.claude/skills/blueprint-catalog/SKILL.md

@@ -0,0 +1,52 @@
+---
+name: blueprint-catalog
+description: >
+  Background knowledge about available project blueprints for scaffolding.
+  Invoke when user discusses: databases, authentication, project setup,
+  monorepo, product ideas, scaffolding, or asks "what should I do next?"
+user-invocable: false
+---
+
+## Available Blueprints
+
+| Blueprint | Tier | What it does | Dependencies | Skill |
+|-----------|------|-------------|--------------|-------|
+| Product Discovery | Discovery | Structured session producing product thesis, user archetypes, and competitive analysis. No code. | None | `/discover` |
+| Monorepo Foundation | Foundation | Turborepo + pnpm monorepo with Next.js, Biome, TypeScript strict, Tailwind v4. | None | `/scaffold-foundation` |
+| Database | Feature | Drizzle ORM + PostgreSQL: schema groups, per-group migrations, seed scripts. | None | `/scaffold-db` |
+| Authentication | Feature | Better Auth + Drizzle + PostgreSQL: social login, email/password, organizations, role-based permissions. | Database | `/scaffold-auth` |
+
+## Project Context
+
+!`cat .project-context.md 2>/dev/null || echo "No .project-context.md found — no blueprints have been installed in this project yet."`
+
+## When to Recommend
+
+Suggest a blueprint when you observe these signals. Be helpful, not pushy — mention it once, then follow the user's lead.
+
+**`/discover`** — User describes a new product idea, asks "what should I build", is unsure about scope or target users, is non-technical or building their first product, or project has no product documentation.
+
+**`/scaffold-foundation`** — User wants to set up a monorepo, mentions Turborepo or project structure, or project has no `turbo.json` / `pnpm-workspace.yaml`. Best after discovery. Skip for single-repo apps.
+
+**`/scaffold-db`** — User mentions database, Drizzle, PostgreSQL, schemas, migrations, or needs a structured db layer. Or is writing raw SQL or using an ORM without organized schemas.
+
+**`/scaffold-auth`** — User mentions login, signup, users, accounts, teams, organizations, permissions, or authentication. Or is implementing auth from scratch. Recommend `/scaffold-db` first if not already installed.
+
+**`/audit`** — User asks "what should I do next?", wants to understand their project's state, or has hand-rolled infrastructure that a blueprint could improve.
+
+## Lifecycle & Dependencies
+
+Discovery → Foundation → Features is the recommended flow, but blueprints can be applied at any stage.
+
+- **New project, no code:** Start with `/discover` (especially for non-technical users) or `/scaffold-foundation` (for monorepos)
+- **Single-repo project:** Skip foundation — go directly to feature blueprints (`/scaffold-db`, `/scaffold-auth`)
+- **Has monorepo, missing features:** Suggest specific feature blueprints
+- **Existing project:** Feature blueprints adapt to existing structures — no foundation required
+- **Dependencies:** `/scaffold-auth` works best after `/scaffold-db` (auth builds on db patterns). Install dependencies first.
+
+## Important
+
+- Check `.project-context.md` first — do not recommend blueprints already recorded there.
+- Read the full BLUEPRINT.md before scaffolding. Follow ENGINEERING.md for coding conventions.
+- Only recommend blueprints listed above. Other blueprints are in development and not yet available.
+- Blueprints location: `~/.withmata/blueprints/`

package/.claude/{commands/discover.md → skills/discover/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: discover
+description: Run a structured product discovery session producing product documentation (no code)
+---
+
 # Run Product Discovery
 
 Run a rigorous product discovery session. This produces product documentation — no code is generated. The session is a structured 60-minute deep dive that transforms a raw idea into a defensible product strategy.
@@ -7,11 +12,11 @@ Run a rigorous product discovery session. This produces product documentation
 Read the full discovery blueprint and all templates:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/discovery/product-discovery/templates/*
+~/.withmata/blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/discovery/product-discovery/templates/*
 ```
 
-If not found at that path, ask the user for the path to their blueprints repo.
+If not found, run `npx @withmata/blueprints` to install.
 
 The BLUEPRINT.md contains the full methodology: phased session structure, frameworks, operating principles, research strategy, challenge patterns, and quality checkpoints. Follow it precisely.
 

package/{.cursor/commands/new-blueprint.md → .claude/skills/new-blueprint/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: new-blueprint
+description: Add a new blueprint to the withmata blueprints repository
+---
+
 # Add a New Blueprint
 
 Guide the user through adding a new blueprint to this repo. This command ensures every blueprint follows the established conventions and is fully wired up.
@@ -214,11 +219,11 @@ Before considering the BLUEPRINT.md done, verify:
 - [ ] Code files use `{{SCOPE}}`, `{{APP_NAME}}`, and `// CONFIGURE:` markers
 - [ ] References link to official docs
 
-## Step 5: Create the Scaffold Command
+## Step 5: Create the Scaffold Skill
 
-Create the command in all three tool directories: `.claude/commands/scaffold-{name}.md`, `.opencode/commands/scaffold-{name}.md`, and `.cursor/commands/scaffold-{name}.md`. The OpenCode version should include YAML frontmatter with a `description` field. The Claude Code and Cursor versions use plain markdown (no frontmatter). The command body is the same across all three.
+Create the skill as `.claude/skills/scaffold-{name}/SKILL.md`. Follow the pattern from existing skills (read `.claude/skills/scaffold-auth/SKILL.md` as the model). Add YAML frontmatter with `name` and `description` fields.
 
-Follow the pattern from existing commands (read `.claude/commands/scaffold-auth.md` as the model). Every scaffold command must:
+Every scaffold skill must:
 
 1. **Read the blueprint** — BLUEPRINT.md and all files
 2. **Read project context** — `.project-context.md` for existing state
@@ -226,14 +231,14 @@ Follow the pattern from existing commands (read `.claude/commands/scaffold-auth.
 4. **Ask clarifying questions** — based on the blueprint's configurable options
 5. **Adapt and scaffold** — replace placeholders, adapt to project structure
 6. **Update project context** — append to `.project-context.md`
-7. **Inject maintenance rules** — detect and append to the target project's rules file(s): CLAUDE.md, AGENTS.md, or both (see the multi-tool injection pattern in existing scaffold commands)
+7. **Create maintenance skill** — as the final step, create a project-level maintenance skill at `<project>/.claude/skills/{name}-maintenance/SKILL.md` with `user-invocable: false` containing the blueprint's maintenance hooks
 8. **Summarize** — packages to install, env vars to set, manual steps remaining
 
-The command should reference the BLUEPRINT.md as the source of truth for methodology and not duplicate its content.
+The skill should reference the BLUEPRINT.md as the source of truth for methodology and not duplicate its content.
 
 ## Step 6: Update the Repo
 
-After the blueprint and command are created:
+After the blueprint and skill are created:
 
 1. **Update README.md** — Add the new blueprint to the appropriate table (Complete or Planned) in the "Available blueprints" section. Add a scaffold command entry to the "Available commands" table.
 
@@ -243,14 +248,14 @@ After the blueprint and command are created:
 
 4. **Check for a planned blueprint placeholder** — If `blueprints/features/{name}/BLUEPRINT.md` already existed as a planned placeholder, replace it entirely with the full BLUEPRINT.md. Don't try to preserve the placeholder content.
 
-5. **Ensure all three directories have the new scaffold command:** `.claude/commands/`, `.opencode/commands/`, and `.cursor/commands/`.
+5. **Ensure the new scaffold skill exists at `.claude/skills/scaffold-{name}/SKILL.md`.**
 
 ## Step 7: Verify
 
 Before considering the blueprint done:
 
 1. Read back the BLUEPRINT.md and verify it meets the quality checklist from Step 4
-2. Read the scaffold command and verify it follows the pattern from Step 5
+2. Read the scaffold skill and verify it follows the pattern from Step 5
 3. Verify all files in files/ use proper placeholders (no hardcoded scopes or app names)
 4. Verify README.md and CHANGELOG.md are updated
 5. Show the user a summary of everything that was created

package/{.cursor/commands/new-project.md → .claude/skills/new-project/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: new-project
+description: Take a product from idea to running code using the full blueprint lifecycle
+---
+
 # New Project
 
 Take a product from idea to running code. This command walks through the full lifecycle — defining the product, setting up the codebase to support it, and wiring in the capabilities it needs. You're a product partner with deep engineering expertise: the product strategy drives every technical decision.
@@ -7,19 +12,19 @@ Take a product from idea to running code. This command walks through the full li
 Load all available blueprints so you understand what's possible:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/discovery/product-discovery/templates/*
-~/Documents/WithMata/my-blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/foundation/monorepo-turbo/files/**/*
+~/.withmata/blueprints/blueprints/discovery/product-discovery/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/discovery/product-discovery/templates/*
+~/.withmata/blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/foundation/monorepo-turbo/files/**/*
 ```
 
 Also scan for available feature blueprints:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/features/*/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/features/*/BLUEPRINT.md
 ```
 
-Only consider a feature blueprint "available" if its BLUEPRINT.md has `Status: Complete` (not a placeholder). If not found at the paths above, ask the user for the path to their blueprints repo.
+Only consider a feature blueprint "available" if its BLUEPRINT.md has `Status: Complete` (not a placeholder). If not found, run `npx @withmata/blueprints` to install.
 
 ## Step 2: Assess Current State
 

package/.claude/{commands/scaffold-auth.md → skills/scaffold-auth/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: scaffold-auth
+description: Scaffold Better Auth + Drizzle authentication into the current project
+---
+
 # Scaffold Auth Blueprint
 
 Scaffold the `auth-better-auth` blueprint into the current project. Read the full blueprint first, then adapt it to this project's stack.
@@ -7,11 +12,11 @@ Scaffold the `auth-better-auth` blueprint into the current project. Read the ful
 Read the full BLUEPRINT.md and all code files from the auth blueprint:
 
 ```
-blueprints/features/auth-better-auth/BLUEPRINT.md
-blueprints/features/auth-better-auth/files/**/*
+~/.withmata/blueprints/blueprints/features/auth-better-auth/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/features/auth-better-auth/files/**/*
 ```
 
-If these files are not in the current project, look for them at `~/Documents/WithMata/my-blueprints/blueprints/features/auth-better-auth/`. If still not found, ask the user for the path to their blueprints repo.
+If not found at these paths, run `npx @withmata/blueprints` to install.
 
 ## Step 1.5: Read Project Context
 
@@ -115,13 +120,13 @@ Based on the project structure, project context, and user answers, adapt the blu
 ### 4a. Database Layer
 
 **If monorepo:**
-- Copy/adapt `files/db/drizzle.config.ts` → `packages/db/drizzle/auth/drizzle.config.ts`
+- Copy/adapt `files/db/drizzle.config.ts` -> `packages/db/drizzle/auth/drizzle.config.ts`
 - Copy `files/db/auth-schema.ts` as a reference (the actual schema will be auto-generated)
 - Add the `"./auth"` export to `packages/db/package.json`
 - Add `auth:generate` and `auth:migrate` scripts to `packages/db/package.json`
 
 **If single-repo:**
-- Copy/adapt `files/db/drizzle.config.ts` → `drizzle/auth/drizzle.config.ts` (at project root)
+- Copy/adapt `files/db/drizzle.config.ts` -> `drizzle/auth/drizzle.config.ts` (at project root)
 - Adjust schema paths to `"./src/db/auth/schema.ts"` (relative to root)
 - Create `src/db/auth/` directory for auth schema
 - No separate package.json export needed — use direct imports
@@ -129,17 +134,17 @@ Based on the project structure, project context, and user answers, adapt the blu
 ### 4b. Server Layer
 
 **If monorepo:**
-- Copy/adapt `files/server/auth.ts` → `apis/server/src/auth/index.ts`
+- Copy/adapt `files/server/auth.ts` -> `apis/server/src/auth/index.ts`
   - Replace `{{APP_NAME}}`, `{{EMAIL_FROM}}`, `{{SCOPE}}`
-- Copy/adapt `files/server/auth-db.ts` → `apis/server/src/db/auth.ts`
-- Copy/adapt `files/server/middleware.ts` → `apis/server/src/middleware/auth.ts`
+- Copy/adapt `files/server/auth-db.ts` -> `apis/server/src/db/auth.ts`
+- Copy/adapt `files/server/middleware.ts` -> `apis/server/src/middleware/auth.ts`
 - Merge auth env vars into `apis/server/src/env.ts`
 
 **If single-repo:**
-- Copy/adapt `files/server/auth.ts` → `src/lib/auth/index.ts`
+- Copy/adapt `files/server/auth.ts` -> `src/lib/auth/index.ts`
   - Replace `{{APP_NAME}}`, `{{EMAIL_FROM}}`
   - Adjust DB import to use direct path: `import { db } from "@/db/auth/client"` or `#db/auth/client`
-- Copy/adapt `files/server/auth-db.ts` → `src/lib/db/auth.ts`
+- Copy/adapt `files/server/auth-db.ts` -> `src/lib/db/auth.ts`
 - Default to Next.js API routes (no separate Hono server)
 - Merge auth env vars into existing `env.ts` (or create one)
 
@@ -221,21 +226,19 @@ If `.project-context.md` does not exist, create it with the standard header and
 
 Also append any significant architectural decisions to the `## Architecture Decisions` section.
 
-### Inject Maintenance Rules
+### Create Maintenance Skill
 
-Append the condensed maintenance rules to the target project's rules file(s):
+Create a project-level maintenance skill for the auth blueprint:
 
-1. If `CLAUDE.md` exists in the target project → append rules there
-2. If `AGENTS.md` exists in the target project → append rules there
-3. If both exist → append to both (keep them in sync)
-4. If neither exists → ask the user which AI coding tool(s) they use:
-   - Claude Code → create CLAUDE.md with a `## Maintenance Rules` section
-   - OpenCode or Cursor → create AGENTS.md with a `## Maintenance Rules` section (both tools read AGENTS.md)
-   - Multiple tools → create all applicable files
+**File:** `<project>/.claude/skills/auth-maintenance/SKILL.md`
 
-The maintenance rules content is identical regardless of which file it goes into:
+```yaml
+---
+name: auth-maintenance
+description: Maintenance rules for Better Auth. Invoke when modifying auth config, providers, session settings, or auth schema.
+user-invocable: false
+---
 
-```markdown
 ### auth-better-auth maintenance
 - After modifying Better Auth server config, plugins, or providers: run `pnpm auth:generate && pnpm auth:migrate`
 - After updating `better-auth` package: run `pnpm auth:generate`, check for schema changes, migrate if needed
@@ -245,8 +248,6 @@ The maintenance rules content is identical regardless of which file it goes into
 - Never edit the auto-generated auth schema directly — modify the Better Auth config and regenerate
 ```
 
-If the `## Maintenance Rules` heading already exists (from another blueprint), only add the `### auth-better-auth maintenance` subsection — do not duplicate the heading.
-
 ## Step 6: Output Summary
 
 After scaffolding, provide the user with a clear summary:

package/{.cursor/commands/scaffold-db.md → .claude/skills/scaffold-db/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: scaffold-db
+description: Scaffold Drizzle ORM + PostgreSQL database package into the current project
+---
+
 # Scaffold DB Blueprint
 
 Scaffold the `db-drizzle-postgres` blueprint into the current project. Read the full blueprint first, then adapt it to this project's stack.
@@ -7,11 +12,11 @@ Scaffold the `db-drizzle-postgres` blueprint into the current project. Read the
 Read the full BLUEPRINT.md and all template files from the db blueprint:
 
 ```
-blueprints/features/db-drizzle-postgres/BLUEPRINT.md
-blueprints/features/db-drizzle-postgres/files/**/*
+~/.withmata/blueprints/blueprints/features/db-drizzle-postgres/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/features/db-drizzle-postgres/files/**/*
 ```
 
-If these files are not in the current project, look for them at `~/Documents/WithMata/my-blueprints/blueprints/features/db-drizzle-postgres/`. If still not found, ask the user for the path to their blueprints repo.
+If not found at these paths, run `npx @withmata/blueprints` to install.
 
 ## Step 1.5: Read Project Context
 
@@ -188,21 +193,19 @@ scripts_added:
 
 If `.project-context.md` does not exist, create it with the standard header and the Installed Blueprints section. Log a note: "No discovery or foundation context found. Consider running `/discover` and `/scaffold-foundation` for a complete project context."
 
-### Inject Maintenance Rules
+### Create Maintenance Skill
 
-Append the condensed maintenance rules to the target project's rules file(s):
+Create a project-level maintenance skill for the database blueprint:
 
-1. If `CLAUDE.md` exists in the target project -> append rules there
-2. If `AGENTS.md` exists in the target project -> append rules there
-3. If both exist -> append to both (keep them in sync)
-4. If neither exists -> ask the user which AI coding tool(s) they use:
-   - Claude Code -> create CLAUDE.md with a `## Maintenance Rules` section
-   - OpenCode or Cursor -> create AGENTS.md with a `## Maintenance Rules` section (both tools read AGENTS.md)
-   - Multiple tools -> create all applicable files
+**File:** `<project>/.claude/skills/db-maintenance/SKILL.md`
 
-The maintenance rules content is identical regardless of which file it goes into:
+```yaml
+---
+name: db-maintenance
+description: Maintenance rules for Drizzle + PostgreSQL database. Invoke when modifying schemas, adding entities, or running migrations.
+user-invocable: false
+---
 
-```markdown
 ### db-drizzle-postgres maintenance
 - After creating a new schema file: add it to `drizzle/<group>/drizzle.config.ts` schema array AND the group's `index.ts` barrel export
 - After any schema change: run `pnpm <group>:generate && pnpm <group>:migrate`
@@ -211,8 +214,6 @@ The maintenance rules content is identical regardless of which file it goes into
 - Never use glob patterns in drizzle.config.ts schema — always list files explicitly, excluding index.ts
 ```
 
-If the `## Maintenance Rules` heading already exists (from another blueprint), only add the `### db-drizzle-postgres maintenance` subsection — do not duplicate the heading.
-
 ## Step 6: Output Summary
 
 After scaffolding, provide the user with a clear summary:

package/.claude/{commands/scaffold-foundation.md → skills/scaffold-foundation/SKILL.md}

@@ -1,3 +1,8 @@
+---
+name: scaffold-foundation
+description: Set up a Turborepo + pnpm monorepo skeleton (skip for single-repo apps)
+---
+
 # Scaffold Foundation
 
 Set up the monorepo project skeleton using the foundation blueprint. **For single-repo applications** (standalone Next.js, Node, or Bun apps), skip this command and go directly to feature blueprints (`/scaffold-db`, `/scaffold-auth`) — they detect single-repo projects and adapt automatically.
@@ -7,11 +12,11 @@ Set up the monorepo project skeleton using the foundation blueprint. **For singl
 Read the full foundation blueprint and all template files:
 
 ```
-~/Documents/WithMata/my-blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
-~/Documents/WithMata/my-blueprints/blueprints/foundation/monorepo-turbo/files/**/*
+~/.withmata/blueprints/blueprints/foundation/monorepo-turbo/BLUEPRINT.md
+~/.withmata/blueprints/blueprints/foundation/monorepo-turbo/files/**/*
 ```
 
-If not found at that path, ask the user for the path to their blueprints repo.
+If not found, run `npx @withmata/blueprints` to install.
 
 The BLUEPRINT.md contains the full architecture documentation, naming conventions, folder conventions, and file manifest. Follow it precisely.
 
@@ -114,22 +119,18 @@ foundation_completed: <date>
 
 If `.project-context.md` does not exist, create it with the standard header and the Foundation section.
 
-### Inject Maintenance Rules
-
-Append the condensed maintenance rules to the target project's rules file(s):
+### Create Maintenance Skill
 
-1. If `CLAUDE.md` exists in the target project → append rules there
-2. If `AGENTS.md` exists in the target project → append rules there
-3. If both exist → append to both (keep them in sync)
-4. If neither exists → ask the user which AI coding tool(s) they use:
-   - Claude Code → create CLAUDE.md with a `## Maintenance Rules` section
-   - OpenCode or Cursor → create AGENTS.md with a `## Maintenance Rules` section (both tools read AGENTS.md)
-   - Multiple tools → create all applicable files
+Create a project-level maintenance skill for the monorepo foundation:
 
-The maintenance rules content is identical regardless of which file it goes into:
+**File:** `<project>/.claude/skills/monorepo-maintenance/SKILL.md`
 
-```markdown
-## Maintenance Rules
+```yaml
+---
+name: monorepo-maintenance
+description: Maintenance rules for the Turborepo monorepo foundation. Invoke when modifying workspace configs, shared packages, or Turbo tasks.
+user-invocable: false
+---
 
 ### Monorepo maintenance
 - After every code change: format with Biome (`pnpm biome check --write .`) before considering work complete

package/ENGINEERING.md

@@ -41,7 +41,7 @@ These preferences apply to ALL blueprints in this repo and to any project scaffo
 - **Project types:** Blueprints support both `monorepo` and `single-repo` project types. Monorepo conventions (workspaces, Turbo, shared config packages) are conditional on project type. Single-repo apps skip Foundation and go directly to Features.
 - **Blueprint dependencies:** Declared in `## Blueprint Dependencies` in each BLUEPRINT.md. Two types: `required` (checked during scaffolding, user prompted) and `recommended` (mentioned once). Auth requires DB. See individual BLUEPRINT.md files for the full dependency graph.
 - **Project context:** Every blueprint appends to `.project-context.md` in the target project root — tool-agnostic location readable by any AI coding tool
-- **Commands live in `.claude/commands/` (Claude Code), `.opencode/commands/` (OpenCode), and `.cursor/commands/` (Cursor)** — each tool auto-discovers from its own directory
+- **Skills live in `.claude/skills/<name>/SKILL.md`** — single source of truth. Installed globally to `~/.claude/skills/`, `~/.config/opencode/skills/`, `~/.cursor/skills/` via the CLI. OpenCode and Cursor also read `~/.claude/skills/` as a cross-tool fallback.
 - **Rules/preferences are in `ENGINEERING.md`** — tool-specific files (`CLAUDE.md`, `AGENTS.md`, `.cursor/rules/engineering.mdc`) point to it
-- **Available commands:** `/new-project`, `/discover`, `/scaffold-foundation`, `/scaffold-auth`, `/scaffold-db`, `/audit`
+- **Available skills:** `/new-project`, `/discover`, `/scaffold-foundation`, `/scaffold-auth`, `/scaffold-db`, `/audit`, plus `blueprint-catalog` (background, auto-invoked)
 - **BLUEPRINT.md required** in every blueprint directory. Placeholder blueprints must still have a BLUEPRINT.md documenting intended scope.