@phuc1403/musketeer 0.2.1 → 0.2.2

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@phuc1403/musketeer",
-  "version": "0.2.1",
+  "version": "0.2.2",
   "description": "Distributable custom Claude Code harness — one declarative command scaffolds a curated company of musketeers (skills/agents/hooks) into any project's .claude/.",
   "type": "commonjs",
   "bin": {

package/template/.claude/skills/knowledge-crunching/SKILL.md

@@ -42,7 +42,7 @@ it's out of scope and offer to hand off afterward.
 
 ### Step 1 — Open the session and name the flow
 
-**First read any prior crunching output for that context** — a `docs/bounded-contexts/<bc>/CONTEXT.md` and read the domain's code; in DDD, document = code. While reading the code, **note the language, idioms, and test framework already in use** — you'll model in those. If the module is a bare scaffold with no language chosen yet, ask the user which language and test framework the context should be modeled in before proposing any code.
+**First read any prior crunching output for that context** — the root-level `CONTEXT.md` and read the domain's code; in DDD, document = code. While reading the code, **note the language, idioms, and test framework already in use** — you'll model in those. If the module is a bare scaffold with no language chosen yet, ask the user which language and test framework the context should be modeled in before proposing any code.
 
 ### Step 2 — Find the first model elements (the "glimmer")
 Listen past the user's solution framing for the **domain nouns and verbs that keep recurring** — Name 2–4 candidate
@@ -105,7 +105,7 @@ that embodies it), then `_Avoid_:` rejected synonyms — grouped under a `###` s
 `CONTEXT.md` identical: rename in code, rename here in the same turn. Distilled-out concepts go under
 `## Deferred`, unresolved ones under `## Flagged ambiguities`.
 
-Edit the context's existing `docs/bounded-contexts/<bc>/CONTEXT.md` directly — it is canonical, and is
+Edit the context's existing root-level `CONTEXT.md` directly — it is canonical, and is
 also your seed (Step 1). If the module is new and has no `CONTEXT.md` yet, create one from
 `assets/context.template.md`.
 

package/template/.claude/skills/knowledge-crunching/assets/context.template.md

@@ -2,8 +2,8 @@
 
 <One line: the slice of the domain this context covers — the flow you crunched, in the expert's words.>
 
-> Starter for a context that has **no `CONTEXT.md` yet**. It lives at
-> `docs/bounded-contexts/<bc>/CONTEXT.md`. If the context already has one, edit that — never a second.
+> Starter for a context that has **no `CONTEXT.md` yet**. It lives at the
+> root folder as `CONTEXT.md`. If the context already has one, edit that — never a second.
 
 ## Language