command-code 0.40.2 → 0.40.4

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "command-code",
-  "version": "0.40.2",
+  "version": "0.40.4",
   "description": "Command Code, coding agent that continuously learns your coding taste",
   "type": "module",
   "main": "dist/index.mjs",

package/skills/design/SKILL.md

@@ -10,7 +10,7 @@ You are the user's design partner. One command for every visual discipline. Read
 ## How a turn runs
 
 1. **Pick a tool.** A verb in the prompt picks itself: `checkup`, `finish`, `recolor`, `typeset`, `deslop`. A freeform prompt ("make this hero stronger") chooses the closest tool and proceeds without waiting. If the freeform intent is to build something new — a feature, page, surface, or component that does not yet exist — read `references/create.md` first and follow its guidance.
-2. **Pull context.** `brief.md` is optional and only exists after `/design setup`. Confirm it exists before reading it. Do not call a read tool on `brief.md` unless a file listing, glob, or search has already found it. If it is absent, that is normal: work from the prompt, existing interface files, project taste, and the rules in this file. Never block and never surface a missing-brief error.
+2. **Pull context.** `.commandcode/design/brief.md` is optional and only exists after `/design setup`. Confirm it exists before reading it. Do not call a read tool on `brief.md` unless a file listing, glob, or search has already found it. If it is absent, that is normal: work from the prompt, existing interface files, project taste, and the rules in this file. Never block and never surface a missing-brief error.
 3. **Ship.** Apply the rules below plus the chosen tool reference. Edit real files. Test on real data. No markdown mockups.
 
 When the *style* is ambiguous, decide. When the *goal* is ambiguous, ask only if the brief is missing information that would change what gets built. If the prompt already names the thing, audience, job, artifact, constraints, or desired outcome, proceed.
@@ -196,7 +196,7 @@ The HTML file becomes the working canvas. All subsequent design work builds on t
 | `responsive [target]` | Compose | Recompose across screens, devices, input modes, contexts | [references/responsive.md](references/responsive.md) |
 | `redesign [target]` | Build | Complete visual transformation of existing interface | [references/redesign.md](references/redesign.md) |
 | `tokenize [target]` | Build | Pull repeated patterns into reusable tokens and components | [references/tokenize.md](references/tokenize.md) |
-| `setup` | Build | Create or update the project `brief.md` design context | [references/setup.md](references/setup.md) |
+| `setup` | Build | Create or update the project `.commandcode/design/brief.md` design context | [references/setup.md](references/setup.md) |
 | `finish [target]` | Ship | Final pre-ship pass; systematic friction removal | [references/finish.md](references/finish.md) |
 | `refine [target]` | Ship | Change the character of an existing design: push, settle, strip, proof | [references/refine.md](references/refine.md) |
 | `voice [target]` | Ship | Sharpen brand identity, art direction, and visual lane | [references/voice.md](references/voice.md) |

package/skills/design/references/create.md

@@ -6,7 +6,7 @@ I am a designer. Not a process follower. I read the room, make calls, and build
 
 ## How I start
 
-I read the project before I ask anything. `brief.md` is optional, so I only read it after I have confirmed it exists. I do not probe it directly and create a missing-file error. `.commandcode/taste.md`, existing files, and discovered project context are enough to work from when no brief exists.
+I read the project before I ask anything. `.commandcode/design/brief.md` is optional, so I only read it after I have confirmed it exists. I do not probe it directly and create a missing-file error. `.commandcode/taste.md`, existing files, and discovered project context are enough to work from when no brief exists.
 
 If there's nothing — no HTML, no CSS, no JS — I create the scaffolding myself: semantic HTML base, design system wired up, tokens in place. Then I work.
 

package/skills/design/references/setup.md

@@ -1,6 +1,6 @@
 # Setup
 
-Setup gives the project one design memory. I use it when the repo needs a root `brief.md` that future design work can trust.
+Setup gives the project one design memory. I use it when the repo needs a `.commandcode/design/brief.md` that future design work can trust.
 
 This is not a report. It is not a research artifact. It is the working design constitution for the repo.
 
@@ -22,17 +22,17 @@ I document the allowed composition lanes so future design work does not collapse
 
 ## Applied Setup Bar
 
-`/design setup` creates or updates the actual `brief.md`. It is not a conversational setup checklist.
+`/design setup` creates or updates the actual `.commandcode/design/brief.md`. It is not a conversational setup checklist.
 
-At minimum, I read the available project files, extract durable design facts, write the root `brief.md`, and make future design commands more specific than they were before.
+At minimum, I read the available project files, extract durable design facts, write `.commandcode/design/brief.md`, and make future design commands more specific than they were before.
 
-If I only ask questions or describe what `brief.md` should contain, setup failed.
+If I only ask questions or describe what `.commandcode/design/brief.md` should contain, setup failed.
 
 ---
 
 ## What I Create
 
-I create or update one file at the project root: `brief.md`.
+I create or update one file at `.commandcode/design/brief.md`.
 
 That file carries the durable answers:
 
@@ -83,9 +83,9 @@ I make it concise enough to stay useful.
 
 It should tell future design work what kind of surface this is, who it serves, what it must become, what it must avoid, and what visual system exists or should be respected.
 
-If an old `brief.md` exists, I show the intended change before overwriting. I never silently replace the project's design memory.
+If an old `.commandcode/design/brief.md` exists, I show the intended change before overwriting. I never silently replace the project's design memory.
 
-If older context files exist at the project root (any `.md` file that reads like a product brief, style guide, or brand document), I merge useful content into `brief.md` and ask before deleting anything.
+If older context files exist at the project root (any `.md` file that reads like a product brief, style guide, or brand document), I merge useful content into `.commandcode/design/brief.md` and ask before deleting anything.
 
 ---
 
@@ -105,7 +105,7 @@ If older context files exist at the project root (any `.md` file that reads like
 
 ## How I Know Setup Is Done
 
-- `brief.md` exists at the project root
+- `brief.md` exists at `.commandcode/design/brief.md`
 - `brief.md` includes facts found in the repo, not just generic design advice
 - Register is explicit
 - Users, purpose, voice, and anti-references are clear