Youssef
aedca8cb03
The published install command in the README — npx skills add nutlope/hallmark — was failing for users because the skills CLI looks for SKILL.md at the repo root, not at skill/SKILL.md where Hallmark kept it. The clone succeeded but the CLI reported "No skills found." Manual cp was the only working install path. Flattened the layout: - skill/SKILL.md → SKILL.md - skill/references/ → references/ - (skill/ directory removed; was empty after moves) git mv preserved rename history for all 76+ files (SKILL.md + 28 reference files + 21 macrostructures + 46 components + 7 verb/genre subfolders). Updated every cross-reference (36 occurrences across 9 files): - README.md — 4 links (SKILL.md + references/ + the install snippet still reads the same) - ROADMAP.md — 4 links to reference files - package.json — "files" field + "skill" entry/references paths - site/js/main.js — 3 source comments - references/design-md.md — one broken link (was pointing skill/references/export-formats.md from inside references/ — now just export-formats.md as a sibling) - site/_tests/verbs/study/notes.md, diagnosis.md and verbs/audit/audit-report.md, custom/README.md — test-artifact relative paths shortened by one segment (e.g. ../../../skill/SKILL.md → ../../../SKILL.md) No skill content changes. After this lands, 'npx skills add nutlope/hallmark' should clone + install correctly without any manual cp fallback.
1.4 KiB
14 · Narrative Workflow
Numbered stages tell the story of how the user uses the product over time. Each section is a phase (1.0 → 2.0 → 3.0 → 4.0). The page is a process timeline.
- Heading: large numbered stage labels (
1.0 INTAKE,2.0 PLAN). - Body: each stage has a short explanation and a small product visual.
- Divider: thick numbered rule between stages.
- Button: stage-internal links; one global "Start at stage 1 →" at the foot.
- Image: small product capture per stage, often annotated.
- Reveal: sweep horizontal as stages enter the viewport.
Reach for it for products with explicit workflows — project management, design-to-dev pipelines, writing tools.
Avoid for tools that work in one moment. Narrative Workflow needs a real sequence.
Reference: Linear's how-it-works pages, some Figma marketing pages.
Sample opening lines (imitate the specificity — Narrative Workflow openings are stage labels: numbered, declarative, in process language):
"01 · sourdough overnight · 02 · score at dawn · 03 · pull at seven." — three numbered stages, no marketing "1.0 · parse · 2.0 · filter · 3.0 · route." — Streampipe (test 02) — versioned numbers, three concrete verbs "I. We design products that last twelve years. II. A material is sustainable when someone, somewhere, can repair it." — Meridian — Roman numerals + declarative