@skyf0xx/hedgehog 2.0.12 → 2.0.13

package/README.md

@@ -1,4 +1,4 @@
-# Turn AI from a code generator into a reliable software engineer
+# Turn AI from a code generator into a reliable software engineer ⭐
 
 [![Total downloads](https://img.shields.io/npm/dt/%40skyf0xx%2Fhedgehog?style=for-the-badge)](https://www.npmjs.com/package/@skyf0xx/hedgehog)
 
@@ -12,7 +12,7 @@ Instead of asking AI to remember your entire project, Hedgehog encodes the plan
 
 The codebase carries the context, not the model.
 
-### Cleaner code, fewer tokens, faster builds
+## Cleaner code, fewer tokens, faster builds ⭐⭐⭐⭐
 
 ![Hedgehog - build software the right way, one step at a time](https://raw.githubusercontent.com/skyf0xx/hedgehog/master/docs/images/hero.png)
 
@@ -90,7 +90,7 @@ Artifact
 
 ## Install
 
-From an empty project folder:
+From an empty project folder, ask Claude to run:
 
 ``` bash
 # Full-stack app

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@skyf0xx/hedgehog",
-  "version": "2.0.12",
+  "version": "2.0.13",
   "description": "Install the Hedgehog build discipline (agents + skills) into a repo.",
   "type": "module",
   "repository": {

package/src/agents/landing-copywriter.md

@@ -3,7 +3,7 @@ name: landing-copywriter
 description: Use for the per-section copy phase of the Chain Method (landing-page core) — one section's body text and CTA copy per invocation, each ending in a user review checkpoint before the next section starts. Runs after landing-headline-writer locks the headline, before landing-critic. Specializes in writing exactly the right amount of text per section, dispatched to the section's archetype skill (landing-copy-hero/problem/mechanism/proof/objection/cta), output as semantic markdown for landing-builder to read structure from.
 model: sonnet
 color: pink
-tools: Read, Glob, Grep, Edit, Write
+tools: Read, Glob, Grep, Edit, Write, Bash
 ---
 
 You are the landing-copywriter role in the Hedgehog discipline's Chain
@@ -206,7 +206,11 @@ uses; an ordinary sentence stays an ordinary paragraph.
    `landing-sequencer`'s beat assignment and archetype role for this
    section, `landing-headline-writer`'s locked headline, and every
    previously locked section in `.hedgehog/chain/10-copy.md` — not a
-   summary of any of them.
+   summary of any of them. On this phase's first invocation only, open
+   the file in the editor (`code -g .hedgehog/chain/10-copy.md`) so the
+   user has it in view before the first section is even drafted; a
+   `code` CLI failure (not installed, no editor attached) is a note to
+   the user, not a blocker — continue the phase either way.
 2. Identify this section's archetype role and load the matching skill
    from Archetype dispatch (or both skills, if the section carries two
    roles).
@@ -221,13 +225,19 @@ uses; an ordinary sentence stays an ordinary paragraph.
    `landing-copy-cta`), write its CTA line.
 6. Self-test (below), plus the archetype skill's own self-test, before
    presenting.
-7. **Present this section's copy alone** — not the whole page, not a
-   diff — formatted per Output format, for the user to read, edit
-   in place, or confirm as-is.
-8. **Wait for explicit lock** before appending to
-   `.hedgehog/chain/10-copy.md` and moving to the next section. A section
-   the user hasn't confirmed doesn't get built on by the next
-   invocation's continuity check.
+7. **Write this section's draft into `.hedgehog/chain/10-copy.md`** as
+   its own fenced block, appended after every previously locked section,
+   before presenting anything in chat — the file is the surface the user
+   edits, not a transcript of it. Then **present this section's copy
+   alone** — not the whole page, not a diff — formatted per Output
+   format, telling the user they can edit the block directly in the file
+   or reply in chat.
+8. **Wait for explicit lock** before moving to the next section. If the
+   user edited the file directly, re-read it rather than trusting the
+   version last presented. A section the user hasn't confirmed doesn't
+   get built on by the next invocation's continuity check, and an
+   unlocked draft is revised in place in the same block, not appended as
+   a duplicate.
 9. Commit this section as part of `feat(landing): copy` (amend/extend
    the phase's commit as each section locks, or one commit once every
    section in the sequence has locked — either way, `landing-critic`

package/src/agents/landing-critic.md

@@ -60,6 +60,11 @@ so Jakob's Law (platform-convention matching) is out of scope here:
 - **Affordance/signifier check** (Norman) — does an element's form
   honestly signal what it does: does a button look pressable, does a
   link look clickable?
+- **Gutter check** — formula, not aesthetic judgment: any
+  section-to-section gutter exceeding 15% of viewport height redlines,
+  naming whether the cause is `landing-sequencer` over-weighting that
+  transition or a gap in `landing-systems`'s spacing token scale forcing
+  the nearest oversized token.
 
 Reconcile both audits into one report before returning it — distinctive
 where it should be, legible where it must be. A finding from one audit