@withmata/blueprints 0.3.5 → 0.4.0

package/.claude/skills/scaffold-foundation/SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: scaffold-foundation
-description: Set up a Turborepo + pnpm monorepo skeleton (skip for single-repo apps)
+description: Set up a Turborepo + bun monorepo skeleton (skip for single-repo apps)
 ---
 
 # Scaffold Foundation
@@ -154,9 +154,8 @@ Create the monorepo skeleton by adapting all files from the blueprint. Replace p
 ### 5a. Root Configuration
 
 From `files/root/`, create at project root:
-- `package.json` — root monorepo config
+- `package.json` — root monorepo config (includes `workspaces` field)
 - `turbo.json` — task orchestration
-- `pnpm-workspace.yaml` — workspace patterns
 - `biome.json` — linting + formatting
 - `.gitignore` — from `files/root/gitignore`
 
@@ -188,8 +187,8 @@ Create empty directories for feature blueprints:
 
 After creating all files:
 1. Initialize git if not already a repo: `git init`
-2. Run `pnpm install` to verify the workspace configuration is valid
-3. Verify the dev server starts: `pnpm dev` (briefly — just check it boots)
+2. Run `bun install` to verify the workspace configuration is valid
+3. Verify the dev server starts: `bun dev` (briefly — just check it boots)
 
 ## Step 5.5: Optional Features
 
@@ -244,8 +243,8 @@ When the user opts in to frontend work, apply both tailwind-v4 and ui-shared-com
 ### 5.5d. Re-install
 
 If any optional features were applied:
-1. Run `pnpm install` again to wire new workspace dependencies
-2. Verify `pnpm dev` still boots cleanly
+1. Run `bun install` again to wire new workspace dependencies
+2. Verify `bun dev` still boots cleanly
 
 ## Step 6: Update Project Context
 
@@ -262,7 +261,7 @@ Then append the `## Foundation` section:
 ```yaml
 ## Foundation
 monorepo_tool: turborepo
-package_manager: pnpm
+package_manager: bun
 npm_scope: "<scope>"
 node_version: ">=22"
 project_type: monorepo
@@ -311,11 +310,11 @@ Then append sections for each blueprint applied in this run. Foundation always a
 
 ```markdown
 ### Monorepo maintenance
-- After every code change: format with Biome (`pnpm biome check --write .`) before considering work complete
-- After adding new workspace packages: verify `pnpm-workspace.yaml` patterns match, run `pnpm install`
+- After every code change: format with Biome (`bun biome check --write .`) before considering work complete
+- After adding new workspace packages: verify `workspaces` field in root `package.json` includes the pattern, run `bun install`
 - After modifying shared configs (`config/typescript-config/`, `config/tailwind-config/`): verify all consumers still build
-- After changing `turbo.json`: verify task ordering with `pnpm turbo run <task> --dry`
-- After adding workspace dependencies: run `pnpm install` to create workspace links
+- After changing `turbo.json`: verify task ordering with `bun turbo run <task> --dry`
+- After adding workspace dependencies: run `bun install` to create workspace links
 - Keep `turbo.json` tasks with `cache: false` for any task with side effects (migrations, code generation)
 
 ### env-t3 maintenance
@@ -337,7 +336,7 @@ If frontend UI was applied, also append:
 - Colors use OKLCH color space — do not use hex or RGB
 
 ### ui-shared-components maintenance
-- Add shadcn components via `pnpm dlx shadcn@latest add <name>` from packages/ui/
+- Add shadcn components via `bunx shadcn@latest add <name>` from packages/ui/
 - Use cn() for all className composition — never concatenate class strings manually
 - Internal imports use #prefix (#components/ui/button); cross-package imports use @scope/ui/components/ui/button
 - After adding a new export directory: add to both exports and imports in packages/ui/package.json
@@ -353,8 +352,8 @@ Tell the user:
 - Project structure overview (directory tree — include optional features that were applied)
 - What was configured (scope, Node version, tooling)
 - Which optional features were included
-- How to start development: `pnpm dev`
-- If frontend UI was set up: how to add shadcn components (`cd packages/ui && pnpm dlx shadcn@latest add button`)
+- How to start development: `bun dev`
+- If frontend UI was set up: how to add shadcn components (`cd packages/ui && bunx shadcn@latest add button`)
 - Available feature blueprints to install next: `/scaffold-db`, `/scaffold-auth`
 
 ### Upgrade Mode Summary
@@ -372,3 +371,4 @@ Tell the user:
 - If the user has customized colors in `shared-styles.css` or added variables to `env.ts`, ask before replacing. Offer to merge their customizations into the new version.
 - Feature blueprints will add scripts to root `package.json` and tasks to `turbo.json` — the foundation provides the base that they extend.
 - The individual `/scaffold-env`, `/scaffold-tailwind`, and `/scaffold-ui` skills still exist for projects that didn't use foundation or want to add features later. The foundation's optional feature steps follow the same blueprints — no duplication.
+- Monorepo detection: check for `"workspaces"` in `package.json` as the primary indicator, or `turbo.json`, or `pnpm-workspace.yaml` (legacy).

package/.claude/skills/scaffold-tailwind/SKILL.md

@@ -59,10 +59,24 @@ If `tailwind-v4` is found in `.project-context.md` under `## Installed Blueprint
 
 Check `.project-context.md` for `project_type`. If not present, detect:
 
-- **Monorepo indicators**: `pnpm-workspace.yaml`, `turbo.json`, or `"workspaces"` in root `package.json`
+- **Monorepo indicators**: `turbo.json`, `"workspaces"` in root `package.json`, or `pnpm-workspace.yaml`
 - **Single-repo indicators**: Single `package.json` at root, `src/` directory
 
-### 2b. Check Existing Tailwind Setup
+### 2b. Check for Design System
+
+Check if `docs/design/shared-styles.css` exists in the project root.
+
+If found:
+- Use it as the shared-styles.css **instead of the blueprint's generic template**
+- Inform user: "Found custom design system tokens at `docs/design/shared-styles.css` — using your design instead of defaults."
+- Verify it has all required CSS variables (31 semantic colors, radius, fonts). If any are missing, warn and fill with defaults.
+- Still apply the standard `@import` directives and `@theme inline` structure if they're missing from the design system file.
+
+If not found:
+- Proceed with the generic template as before
+- Mention: "Using default shadcn tokens. Run `/design-system` to create a custom visual identity for your product."
+
+### 2c. Check Existing Tailwind Setup
 
 - Does `config/tailwind-config/` exist? (Foundation blueprint creates this)
 - Read existing `shared-styles.css` — is it the minimal version or already upgraded?
@@ -125,7 +139,7 @@ Skip questions if the user has indicated preferences or if the project type make
 
 ### 4c. Install Dependencies
 
-Run `pnpm install` (or the project's package manager) to fetch new dependencies.
+Run `bun install` (or the project's package manager) to fetch new dependencies.
 
 ## Step 5: Update Project Context
 

package/.claude/skills/scaffold-ui/SKILL.md

@@ -14,6 +14,7 @@ Read the full BLUEPRINT.md and all template files from the UI blueprint:
 ```
 ~/.withmata/blueprints/blueprints/features/ui-shared-components/BLUEPRINT.md
 ~/.withmata/blueprints/blueprints/features/ui-shared-components/files/**/*
+~/.withmata/blueprints/blueprints/features/ui-shared-components/files/ui/components/ui/**/*.tsx
 ```
 
 If not found at these paths, run `npx @withmata/blueprints` to install.
@@ -39,7 +40,7 @@ If `ui-shared-components` is in Installed Blueprints, switch to upgrade mode (St
 If `ui-shared-components` is found in `.project-context.md` under `## Installed Blueprints`, switch to upgrade mode.
 
 1. **Read installed state** — from project context, get `files_created`, `choices`, and `installed_at`
-2. **Compare templates against installed files:**
+2. **Compare config/utility templates against installed files:**
    - `packages/ui/package.json` — compare exports, imports, dependencies. Look for new export patterns, updated deps.
    - `packages/ui/components.json` — compare shadcn config. Look for updated aliases or style changes.
    - `packages/ui/utils/cn.ts` — compare utility implementation.
@@ -47,25 +48,52 @@ If `ui-shared-components` is found in `.project-context.md` under `## Installed
    - `packages/ui/styles/globals.css` — compare style imports.
    - `packages/ui/tsconfig.json` — compare TypeScript config.
    - Check consuming app `globals.css` — verify `@import` and `@source` directives are present and correct.
-3. **Present findings:**
+3. **Compare base component templates against installed versions:**
+
+   The 31 base component templates are **blueprint-owned** and can be updated during upgrades:
+   - Primitives: `button.tsx`, `input.tsx`, `label.tsx`, `textarea.tsx`, `badge.tsx`, `separator.tsx`
+   - Compound: `card.tsx`, `alert-dialog.tsx`, `select.tsx`, `combobox.tsx`, `dropdown-menu.tsx`, `sidebar.tsx`, `field.tsx`, `input-group.tsx`
+   - Navigation: `breadcrumb.tsx`, `collapsible.tsx`, `popover.tsx`
+   - Form widgets: `form-field.tsx`, `tag-input.tsx`, `pill-select.tsx`, `card-select.tsx`, `entity-select.tsx`, `selected-entity-card.tsx`
+   - Data display: `pagination.tsx`, `empty-state.tsx`, `avatar.tsx`
+   - App shell: `user-menu.tsx`, `org-switcher.tsx`, `page-header.tsx`, `status-filter.tsx`, `search-input.tsx`
+
+   Any components in `components/ui/` that are NOT in the above list are **user-owned** (added via `shadcn add` or custom) — never touch those.
+
+   For each blueprint-owned component:
+   - Diff the blueprint template against the installed version
+   - Track which files have changes vs which are unchanged
+4. **Present findings:**
    ```
    ui-shared-components was installed on <date>. Checking for updates...
 
-   Updated files:
+   Updated config files:
      ☐ packages/ui/package.json — new export patterns or dependencies
      ☐ packages/ui/components.json — updated shadcn configuration
 
+   Updated base components:
+     ☐ components/ui/button.tsx — updated variant styles
+     ☐ components/ui/combobox.tsx — new Base UI pattern
+
    New files:
      ☐ packages/ui/utils/cva.ts — new utility (didn't exist in previous version)
 
    Unchanged:
      ✓ packages/ui/utils/cn.ts — no changes
+     ✓ components/ui/card.tsx — no changes
+     ... (N more unchanged)
+
+   User-owned (never touched):
+     ✓ components/ui/dialog.tsx — added by user via shadcn
+     ✓ components/ui/toast.tsx — added by user via shadcn
 
    Apply updates?
    ```
-4. **Apply selectively** — `package.json` exports and `components.json` are blueprint-owned. `components/ui/` files are user-owned (shadcn-generated) — never touch those.
-5. **Update project context** — update `installed_at` date
-6. **Skip to Step 6 (Output Summary)**
+5. **Apply selectively** — config files and base components are blueprint-owned. User-added components (anything not in the 31-component list) are user-owned — never touch those.
+6. **Update project context** — update `installed_at` date
+7. **Skip to Step 6 (Output Summary)**
+
+**Important:** Base components may have been customized by the user after initial scaffold. When presenting updates, show the diff so the user can decide whether to accept each change. Config files (`package.json`, `components.json`) are safe to update automatically.
 
 ## Step 2: Understand the Target Project
 
@@ -73,18 +101,18 @@ If `ui-shared-components` is found in `.project-context.md` under `## Installed
 
 Check `.project-context.md` for `project_type`. If not present, detect:
 
-- **Monorepo indicators**: `pnpm-workspace.yaml`, `turbo.json`, or `"workspaces"` in root `package.json`
+- **Monorepo indicators**: `turbo.json`, `"workspaces"` in root `package.json`, or `pnpm-workspace.yaml`
 - **Single-repo indicators**: Single `package.json` at root, `src/` directory
 
-### 2b. Check Blueprint Dependencies
+### 2b. Auto-install Tailwind Design System
 
-**Required: `tailwind-v4`**
+**Required: `tailwind-v4`** — auto-installed as a prerequisite, no user prompt needed.
 
 Check if `tailwind-v4` is in `.project-context.md` Installed Blueprints, OR check if `config/tailwind-config/shared-styles.css` contains `@import "tw-animate-css"` (indicator of the full tailwind-v4 blueprint).
 
-If NOT installed: ask "UI components need the Tailwind design system. Run `/scaffold-tailwind` first? (Y/n)"
-- If yes: tell the user to run `/scaffold-tailwind` first, then come back
-- If no: proceed with basic Tailwind defaults and warn about missing design tokens
+If NOT installed: **automatically run the scaffold-tailwind process first** before continuing with UI scaffolding. Inform the user: "Installing Tailwind design system (required prerequisite for UI components)..." then read and execute the scaffold-tailwind blueprint (`~/.withmata/blueprints/blueprints/features/tailwind-v4/BLUEPRINT.md`) using the same project context. After tailwind-v4 is scaffolded, continue with the UI scaffold steps below.
+
+Do NOT ask the user whether to install — just do it. The design system is a hard requirement, not optional.
 
 ### 2c. Explore Structure
 
@@ -102,11 +130,15 @@ If NOT installed: ask "UI components need the Tailwind design system. Run `/scaf
 
 ## Step 3: Ask Clarifying Questions
 
-1. **shadcn style** — "Which shadcn style do you prefer? (Default: new-york)" Only ask if the user hasn't specified.
+1. **shadcn style** — "Which shadcn style do you prefer? (Default: base-maia)" Only ask if the user hasn't specified.
+
+2. **Icon library** — "Which icon library? Phosphor (default, richer icon set with weight variants), Lucide (shadcn default), or custom?"
 
-2. **Icon library** — "Which icon library? Lucide (default, shadcn default), Phosphor (richer set), or custom?"
+3. **Include base components** — "Include the 31 base component templates? (Default: yes)" If no, only config/utility files are scaffolded and the user adds components later via `shadcn add`.
 
-3. **Existing `packages/ui/`** — If it exists: "I found an existing `packages/ui/`. I'll merge the new files without overwriting existing ones."
+4. **Include form system** — "Include the form system components (field, form-field, tag-input, pill-select)? (Default: yes)" Only ask if base components are included.
+
+5. **Existing `packages/ui/`** — If it exists: "I found an existing `packages/ui/`. I'll merge the new files without overwriting existing ones."
 
 Skip questions where the answer is obvious.
 
@@ -117,10 +149,10 @@ Skip questions where the answer is obvious.
 1. Create `packages/ui/` directory (if it doesn't exist)
 2. Copy `package.json` — replace `{{SCOPE}}` with the project's npm scope
 3. Copy `tsconfig.json` — replace `{{SCOPE}}`
-4. Copy `components.json` — update style if user chose something other than `new-york`, update iconLibrary if user chose something other than `lucide`
+4. Copy `components.json` — update style if user chose something other than `base-maia`, update iconLibrary if user chose something other than `phosphor`
 5. Create `styles/` directory and copy `globals.css` — replace `{{SCOPE}}`
 6. Create `utils/` directory, copy `cn.ts` and `cva.ts`
-7. Create empty directories: `components/ui/`, `icons/`, `icons/logos/`
+7. Create empty directories: `icons/`, `icons/logos/`
 
 ### 4b. Single-Repo — Create UI Directory
 
@@ -128,7 +160,7 @@ Skip questions where the answer is obvious.
 2. Copy utility files (`cn.ts`, `cva.ts`) to `src/ui/utils/`
 3. Copy `styles/globals.css` to `src/ui/styles/` — adjust import to direct path
 4. Copy `components.json` to project root — update aliases for single-repo paths
-5. Create empty directories: `src/ui/components/ui/`, `src/ui/icons/`
+5. Create empty directories: `src/ui/icons/`
 6. Add UI deps to root `package.json`
 
 ### 4c. Update Consuming App
@@ -152,9 +184,20 @@ Compute the `@source` relative path based on the consuming app's location relati
 
 **Important:** Don't overwrite the entire `globals.css` — merge the new imports. If the file already has `@import "tailwindcss"` and `@import "{{SCOPE}}/tailwind-config"`, add the new lines after them.
 
-### 4d. Dependency Installation
+### 4d. Copy Base Component Templates (if included)
+
+1. Create `components/ui/` directory if not exists
+2. Copy all 31 component `.tsx` files from blueprint templates
+3. No `{{SCOPE}}` replacement needed (components use `#` subpath imports)
+4. If form system declined: skip `field.tsx`, `form-field.tsx`, `tag-input.tsx`, `pill-select.tsx`, `card-select.tsx`, `entity-select.tsx`, `selected-entity-card.tsx`
+5. These are blueprint-owned templates — NOT shadcn-generated
+
+**Monorepo:** files go to `packages/ui/components/ui/`
+**Single-repo:** files go to `src/ui/components/ui/`
+
+### 4e. Dependency Installation
 
-Run `pnpm install` to wire workspace dependencies.
+Run `bun install` to wire workspace dependencies.
 
 ## Step 5: Update Project Context
 
@@ -165,17 +208,54 @@ Append an entry to `.project-context.md` under `## Installed Blueprints`:
 blueprint: ui-shared-components
 installed_at: <date>
 choices:
-  shadcn_style: <style>
-  icon_library: <library>
-  include_cva: true
+  shadcn_style: base-maia
+  icon_library: phosphor
+  include_base_components: true
+  include_form_system: true
 files_created:
-  - <list of all files created>
+  - packages/ui/package.json
+  - packages/ui/tsconfig.json
+  - packages/ui/components.json
+  - packages/ui/styles/globals.css
+  - packages/ui/utils/cn.ts
+  - packages/ui/utils/cva.ts
+  - packages/ui/components/ui/button.tsx
+  - packages/ui/components/ui/input.tsx
+  - packages/ui/components/ui/label.tsx
+  - packages/ui/components/ui/textarea.tsx
+  - packages/ui/components/ui/card.tsx
+  - packages/ui/components/ui/badge.tsx
+  - packages/ui/components/ui/separator.tsx
+  - packages/ui/components/ui/alert-dialog.tsx
+  - packages/ui/components/ui/select.tsx
+  - packages/ui/components/ui/combobox.tsx
+  - packages/ui/components/ui/dropdown-menu.tsx
+  - packages/ui/components/ui/breadcrumb.tsx
+  - packages/ui/components/ui/collapsible.tsx
+  - packages/ui/components/ui/popover.tsx
+  - packages/ui/components/ui/sidebar.tsx
+  - packages/ui/components/ui/field.tsx
+  - packages/ui/components/ui/form-field.tsx
+  - packages/ui/components/ui/input-group.tsx
+  - packages/ui/components/ui/tag-input.tsx
+  - packages/ui/components/ui/pill-select.tsx
 globals_css_updated:
   - <list of globals.css files modified>
 packages_added:
-  - <list of packages>
+  - "@radix-ui/react-slot"
+  - "@base-ui/react"
+  - "@phosphor-icons/react"
+  - "@radix-ui/react-collapsible"
+  - "@radix-ui/react-popover"
+  - class-variance-authority
+  - clsx
+  - tailwind-merge
+  - tw-animate-css
+  - shadcn
 ```
 
+If `.project-context.md` does not exist, create it with the standard header and the Installed Blueprints section.
+
 ### Create Maintenance Skill
 
 Append to the shared project-level maintenance skill at `<project>/.claude/skills/project-maintenance/SKILL.md`.
@@ -194,10 +274,14 @@ Then append:
 
 ```markdown
 ### ui-shared-components maintenance
-- Add shadcn components via `pnpm dlx shadcn@latest add <name>` from packages/ui/
+- Add shadcn components via `bunx shadcn@latest add <name>` from packages/ui/ (uses base-maia style)
 - Use cn() for all className composition — never concatenate class strings manually
+- Use data-slot attribute on every component root element for CSS targeting
+- Import Phosphor icons from @phosphor-icons/react or @phosphor-icons/react/<IconName>
+- Base UI primitives: import from @base-ui/react/<primitive-name>
 - Internal imports use #prefix (#components/ui/button); cross-package imports use @scope/ui/components/ui/button
-- After adding a new export directory: add to both exports and imports in packages/ui/package.json
+- Base components (31 files) are blueprint-owned — update via /scaffold-ui upgrade mode
+- After adding new export directory: add to both exports and imports in packages/ui/package.json
 - After adding a new consuming app: add @import and @source directive to the app's globals.css
 ```
 
@@ -205,40 +289,73 @@ If a `### ui-shared-components maintenance` section already exists in the file,
 
 ## Step 6: Output Summary
 
+After scaffolding, provide the user with a clear summary:
+
 ### Packages to Install
 
 ```bash
-# Should be handled by pnpm install, but verify these are in packages/ui/package.json:
-# Dependencies: @radix-ui/react-slot, class-variance-authority, clsx, tailwind-merge, tw-animate-css, shadcn
-# DevDeps: @tailwindcss/postcss, tailwindcss, typescript, @types/react, @types/react-dom
+# Should be handled by bun install, but verify these are in packages/ui/package.json:
+# Dependencies:
+#   @radix-ui/react-slot, @base-ui/react, @phosphor-icons/react
+#   @radix-ui/react-collapsible, @radix-ui/react-popover
+#   class-variance-authority, clsx, tailwind-merge, tw-animate-css, shadcn
+# DevDeps:
+#   @tailwindcss/postcss, tailwindcss, typescript, @types/react, @types/react-dom
 ```
 
 ### Files Created
 
-List every file created or modified with a one-line description.
+List every file created or modified with a one-line description. Note that 31 base components come pre-installed alongside the 6 config/utility files (37 files total).
 
 ### How to Add Components
 
 ```bash
-# From packages/ui/
+# From packages/ui/ — uses base-maia style (configured in components.json)
 cd packages/ui
-pnpm dlx shadcn@latest add button
-pnpm dlx shadcn@latest add card
-pnpm dlx shadcn@latest add input
+bunx shadcn@latest add dialog
+bunx shadcn@latest add toast
+bunx shadcn@latest add tabs
 ```
 
+Components added via `shadcn add` are user-owned and will not be modified during upgrades. The 31 pre-installed base components are blueprint-owned and can be updated via `/scaffold-ui` upgrade mode.
+
 ### How to Use in Apps
 
 ```typescript
+// Import components from the UI package
 import { Button } from "@scope/ui/components/ui/button";
+import { Card, CardHeader, CardTitle, CardContent } from "@scope/ui/components/ui/card";
 import { cn } from "@scope/ui/utils/cn";
+
+// Import Phosphor icons
+import { MagnifyingGlass, Plus, Check } from "@phosphor-icons/react";
+
+// Base UI primitive usage (used internally by components like Select, Combobox)
+import { Select } from "@base-ui/react/select";
+
+// Form system components
+import { Field } from "@scope/ui/components/ui/field";
+import { FormField } from "@scope/ui/components/ui/form-field";
+import { TagInput } from "@scope/ui/components/ui/tag-input";
+import { PillSelect } from "@scope/ui/components/ui/pill-select";
 ```
 
+### Base Components Included
+
+| Category | Components |
+|----------|-----------|
+| Inputs | `button`, `input`, `label`, `textarea`, `input-group` |
+| Layout | `card`, `badge`, `separator`, `breadcrumb` |
+| Overlays | `alert-dialog`, `dropdown-menu`, `popover`, `collapsible`, `select`, `combobox` |
+| Navigation | `sidebar` |
+| Forms | `field`, `form-field`, `tag-input`, `pill-select` |
+
 ### Next Steps
 
-- Add your first shadcn components with the commands above
+- Add more shadcn components as needed with `bunx shadcn@latest add <name>`
 - Create brand icons in `packages/ui/icons/logos/`
 - Build custom components in `packages/ui/components/`
+- Use the form system (`Field`, `FormField`) for consistent form layouts
 
 ## Important Notes
 
@@ -246,3 +363,5 @@ import { cn } from "@scope/ui/utils/cn";
 - Never overwrite existing files without asking. If `packages/ui/` exists, merge new files.
 - The `@source` directive path must be correct relative to the consuming app — verify it resolves.
 - If `tailwind-v4` is not installed and the user proceeds anyway, the UI package will work but may have missing design tokens (no animations, no sidebar colors, etc.).
+- Base components use `data-slot` attributes on root elements for CSS targeting — preserve these when customizing.
+- Components use `#` subpath imports internally (e.g., `#components/ui/button`) — these are defined in `package.json` imports.

package/ENGINEERING.md

@@ -28,7 +28,7 @@ These preferences apply to ALL blueprints in this repo and to any project scaffo
 
 ## Conventions
 
-- Use `pnpm` as the package manager
+- Use `bun` as the package manager (pnpm is a supported alternative)
 - Prefer named exports over default exports
 - Use Node.js subpath imports (`#prefix`) for internal module resolution within apps/packages
 - Shared config packages live in `config/` (separate from `packages/`)
@@ -43,5 +43,5 @@ These preferences apply to ALL blueprints in this repo and to any project scaffo
 - **Project context:** Every blueprint appends to `.project-context.md` in the target project root — tool-agnostic location readable by any AI coding tool
 - **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 skills:** `/new-project`, `/discover`, `/scaffold-foundation`, `/scaffold-env`, `/scaffold-tailwind`, `/scaffold-ui`, `/scaffold-auth`, `/scaffold-db`, `/audit`, plus `blueprint-catalog` (background, auto-invoked)
+- **Available skills:** `/new-project`, `/discover`, `/copywrite`, `/copywrite-landing`, `/design-system`, `/scaffold-foundation`, `/scaffold-env`, `/scaffold-tailwind`, `/scaffold-ui`, `/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.