@withmata/blueprints 0.2.0 → 0.3.1

package/.opencode/commands/scaffold-foundation.md

@@ -1,162 +0,0 @@
----
-description: Set up Turborepo + pnpm monorepo skeleton
----
-
-# 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.
-
-## Step 1: Read the Blueprint
-
-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/**/*
-```
-
-If not found at that path, ask the user for the path to their blueprints repo.
-
-The BLUEPRINT.md contains the full architecture documentation, naming conventions, folder conventions, and file manifest. Follow it precisely.
-
-## Step 2: Read Project Context
-
-Check if `.project-context.md` exists in the target project root:
-
-- **If it has a Discovery section**: use the product name to derive the npm scope (e.g., "Acme Dashboard" -> `@acme`). Use technical constraints to inform any decisions.
-
-- **If it has a Foundation section already**: warn the user. Ask: "Foundation was already set up. Do you want to re-scaffold (destructive — replaces existing structure) or skip?"
-
-- **If no context file exists**: that is fine. Ask the user directly for the product name and npm scope.
-
-## Step 3: Understand Current State
-
-Explore the target project directory:
-
-- Is it empty? Fresh start — scaffold everything.
-- Does it already have files? Ask before overwriting anything.
-- Is there an existing `package.json`? Read it for context.
-
-## Step 4: Ask Configuration Questions
-
-Only three questions — skip any already answered by project context:
-
-1. **npm scope** — "What npm scope should internal packages use? (e.g., @acme)" Default: derive from product name.
-2. **Project name** — "What is the human-readable project name?" (for metadata, page titles). Default: from discovery context.
-3. **Node.js version** — "Target Node.js version?" Default: `>=22`.
-
-## Step 5: Scaffold
-
-Create the monorepo skeleton by adapting all files from the blueprint. Replace placeholders:
-
-- `{{SCOPE}}` -> the npm scope (e.g., `@acme`)
-- `{{APP_NAME}}` -> the human-readable name (e.g., `Acme Dashboard`)
-
-### 5a. Root Configuration
-
-From `files/root/`, create at project root:
-- `package.json` — root monorepo config
-- `turbo.json` — task orchestration
-- `pnpm-workspace.yaml` — workspace patterns
-- `biome.json` — linting + formatting
-- `.gitignore` — from `files/root/gitignore`
-
-### 5b. Config Packages
-
-From `files/config/`, create:
-- `config/typescript-config/` — base.json, nextjs.json, react-library.json, package.json
-- `config/tailwind-config/` — shared-styles.css, postcss.config.js, package.json
-
-### 5c. Next.js App Shell
-
-From `files/apps/web/`, create:
-- `apps/web/package.json`
-- `apps/web/tsconfig.json`
-- `apps/web/next.config.ts`
-- `apps/web/env.ts`
-- `apps/web/postcss.config.mjs`
-- `apps/web/app/layout.tsx`
-- `apps/web/app/page.tsx`
-- `apps/web/app/globals.css`
-
-### 5d. Empty Workspace Directories
-
-Create empty directories for feature blueprints:
-- `apis/` — backend feature blueprint will add servers here
-- `packages/` — feature blueprints will add shared packages here
-
-### 5e. Initialize
-
-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)
-
-## Step 6: Update Project Context
-
-Append the `## Foundation` section to `.project-context.md`:
-
-```yaml
-## Foundation
-monorepo_tool: turborepo
-package_manager: pnpm
-npm_scope: "<scope>"
-node_version: ">=22"
-workspaces:
-  apps: ["web"]
-  apis: []
-  packages: []
-  config: ["typescript-config", "tailwind-config"]
-framework: next.js (app router)
-typescript: strict
-linter: biome
-styling: tailwind-v4
-env_validation: t3-env + zod
-module_resolution: node subpath imports (#prefix)
-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):
-
-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
-
-The maintenance rules content is identical regardless of which file it goes into:
-
-```markdown
-## Maintenance Rules
-
-### 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 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
-- Keep `turbo.json` tasks with `cache: false` for any task with side effects (migrations, code generation)
-```
-
-## Step 7: Summarize
-
-Tell the user:
-
-- Project structure overview (directory tree)
-- What was configured (scope, Node version, tooling)
-- How to start development: `pnpm dev`
-- Available feature blueprints to install next
-- Suggest: "Run `/scaffold-auth` to add authentication. Other feature blueprints: ui-shared-components, tailwind-v4, db-drizzle-postgres."
-
-## Important Notes
-
-- Never overwrite existing files without asking.
-- Preserve all `// CONFIGURE:` comments in generated files so the user can find customization points.
-- The Tailwind config is intentionally minimal — the UI feature blueprint extends it with shadcn, animations, and component-specific styles.
-- Feature blueprints will add scripts to root `package.json` and tasks to `turbo.json` — the foundation provides the base that they extend.