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.
2.7 KiB
hallmark audit
Read the file(s) the user pointed at. For each finding, return:
- Tell — the named anti-pattern from
anti-patterns.md. - Where — file path and line range.
- Severity —
critical(ships as slop),major(looks AI-generated),minor(small taste issue). - Fix — one-line concrete correction.
Group by severity. Do not edit. Do not redesign. End with a count: N critical · M major · K minor.
Audit also checks structural fingerprint: if the page uses the AI template (centered hero, 3 equal feature cards, CTA, footer, with no asymmetry or surprise), flag it as a critical structural finding even if the visual treatment is fine.
Stamp-vs-page check. If the audited file contains a /* Hallmark · macrostructure: <name> · ... */ stamp, verify the page actually matches that name. If the stamp says Bento Grid but the page is a centered single-column hero with a CTA, flag it as a critical structural finding: stamp lies — the stamp must reflect what shipped or be removed. This catches drift where a previous Hallmark run stamped one thing and a later edit pulled the page back toward the AI template.
Genre-aware audit. If the audited file's stamp names a genre (e.g. genre: atmospheric), apply the genre-scoped overrides from slop-test.md when grading. A radial-gradient background is a critical tell for editorial — but allowed for atmospheric. A pure-white paper is a tell for editorial — but allowed for modern-minimal. The audit verb must respect the genre the page declared.
design.md audit. If the project root has a design.md (or DESIGN.md), read it before grading. Then check every audited page against the system:
- Theme drift. Page uses tokens / fonts / accent that don't match
design.md's declared system → flag ascritical: design-system drift. Per-page theme picks are slop on a system-managed project even if each page is internally fine. - Macrostructure family violation.
design.mdsays marketing pages use Marquee Hero or Stat-Led — the audited page is a Letter format → flag asmajor: outside design.md family. - Stamp mismatch. The page's CSS stamp says
designed-as-appbut readsdesign-system: design.mdand the page actually drifts fromdesign.md→ flag ascritical: stamp lies. The stamp claims compliance the code doesn't deliver. - No stamp at all on a system-managed project → flag as
major: missing system reference. Every page on adesign.mdproject must stamp its allegiance to the system.
Inversely, on a project without design.md, the standard diversification rule applies — flag pages that share macrostructure / theme with a previous Hallmark output as minor: variety drift.