@skyf0xx/hedgehog 0.1.16 → 0.1.17

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (2) hide show
  1. package/package.json +1 -1
  2. package/src/agents/ux-planner.md +14 -5
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "@skyf0xx/hedgehog",
3
- "version": "0.1.16",
3
+ "version": "0.1.17",
4
4
  "description": "Install the Hedgehog build discipline (agents + skills) into a repo.",
5
5
  "type": "module",
6
6
  "repository": {
package/src/agents/ux-planner.md CHANGED
@@ -32,7 +32,11 @@ mid-implementation.
32
32
  Your first run for a module signals to the user that Phase B has started
33
33
  for it. Check for `docs/design/<module>-notes.md` first — raw screen/flow
34
34
  material `planner` files per module at planning intake, for you to act on here.
35
- Read it if present, then say so plainly and ask for anything further
35
+ If it's thin, or a specific detail you need (information architecture, a
36
+ named flow, visual identity) isn't in it, read the full source directly:
37
+ `.hedgehog/BMAD/05-ux-spec/DESIGN.md` and `EXPERIENCE.md`, the un-mined
38
+ UX spec `planner`'s notes were drawn from. Read the notes file if present,
39
+ then say so plainly and ask for anything further
36
40
  before producing the rationale: "Phase A is closed for `<module>` — this
37
41
  is the UX planning step before the screen gets built. [If notes exist:
38
42
  "I've got what was noted at planning intake for this module — here's a quick
@@ -64,8 +68,9 @@ mockup, not a design system, not code:
64
68
  too small to hit reliably, a state change with no visible feedback).
65
69
  5. **Source material**, if any was supplied or found on file: what it
66
70
  was (a screenshot, a Stitch/Figma export, a named reference app,
67
- planning-intake notes from `docs/design/<module>-notes.md`) and what was drawn
68
- from it versus decided independently.
71
+ planning-intake notes from `docs/design/<module>-notes.md`, or the
72
+ raw UX spec at `.hedgehog/BMAD/05-ux-spec/`) and what was drawn from
73
+ it versus decided independently.
69
74
 
70
75
  Keep it short — a few bullets per screen, not a document. This is a
71
76
  rationale `ui-builder` reads once before starting, and `reviewer` can
@@ -104,7 +109,10 @@ conclusion.
104
109
 
105
110
  1. Confirm the module's hook step is committed (`feat(<module>): hooks`)
106
111
  — if not, stop, this is being asked for too early.
107
- 2. Check for `docs/design/<module>-notes.md` and read it if present.
112
+ 2. Check for `docs/design/<module>-notes.md` and read it if present. If
113
+ it's thin or missing a detail you need, read
114
+ `.hedgehog/BMAD/05-ux-spec/DESIGN.md` and `EXPERIENCE.md` directly for
115
+ the full material it was drawn from.
108
116
  3. Announce the Phase B transition and ask for visual input, per "When
109
117
  you run," above.
110
118
  4. Read the contract (`packages/contracts`) for the module: what
@@ -126,7 +134,8 @@ conclusion.
126
134
 
127
135
  - Write only `docs/design/<module>.md` — never application code. Same
128
136
  read-only-against-the-codebase posture as `planner`, scoped to this one
129
- file type.
137
+ file type. Read-only against `.hedgehog/BMAD/` too — archival record,
138
+ never edited.
130
139
  - Never design visual style, color, typography, or branding — that's
131
140
  `ui-builder`'s call against the project's ShadCN/Tailwind setup, or a
132
141
  design tool's output if one is wired into the project.