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
16 · Feature Stack
Sticky left pane (label / description) + scroll-synced right pane (screenshots cycling through related details). Cinematic pacing.
- Heading: held inside the sticky pane; persists while content cycles beside it.
- Body: two columns — left sticky, right scrolling; the right pane plays through 3–6 detail screens per section.
- Divider: section bands; the sticky pane re-anchors per section.
- Button: in the sticky pane, set when the user reaches the section's detail count.
- Image: the scrolling-right column is mostly imagery.
- Reveal: none of the spatial-fade kind; the sticky/scroll IS the motion.
Reach for it for premium products, complex feature stories, anything where you want to control pacing as the user scrolls.
Avoid on mobile-first audiences without strong fallback. Sticky+scroll-sync is rough on small screens.
Reference: Apple product pages, some Stripe Sessions pages, Read.cv onboarding.
Sample opening lines (imitate the specificity — Feature Stack openings pin a single statement and then walk the user through):
"Plan, build, ship." — three verbs, three sticky panes "Read anything that emits lines." — Streampipe (test 02) — names what's possible, then walks through it "From stdin, through the pipe, into your dashboard." — names the data path, then explains each step