scaffold

1# /scaffold — Project-Aware File Generator
2 
3## Orientation
4 
5**Use when:** Creating a new component, module, service, route, hook, domain, or utility with existing examples in the project.
6 
7**Do NOT use when:** The file has no precedent (use `/marshal` for unconstrained generation), you're modifying existing files (use `/refactor`), or the project has no conventions yet.
8 
9**Needs:** target type, name, and optional description.
10 
11## Protocol
12 
13### Step 1: IDENTIFY THE TARGET
14 
15Parse the user's request into:
16- **type**: component | module | service | route | hook | domain | utility | custom
17- **name**: the name the user gave (e.g., "UserProfile", "auth-service", "settings route")
18- **description**: what it does, if provided (otherwise leave blank for now)
19 
20If the type is ambiguous, ask ONE clarifying question. Do not ask more than one.
21 
22### Step 2: FIND EXEMPLARS
23 
24Search the codebase for 2-3 existing files of the same type.
25 
26**Search strategy by type:**
27 
28| Type | Search Pattern | What to Look For |
29|---|---|---|
30| component | `**/*.tsx` in the same directory or sibling directories | Functional components with similar complexity |
31| module | Same directory as where new module will live | Registration pattern, exports, config shape |
32| service | `**/services/**`, `**/lib/**` | Class vs function, singleton vs factory, error handling |
33| route | Router config files, `**/routes.*`, `**/pages/**` | Route definition format, lazy loading, guards |
34…