Codex · trim SKILL.md description under 1024-char limit + document install path

Codex enforces a 1024-char cap on the frontmatter description; ours was 1813,
causing "invalid description: exceeds maximum length of 1024 characters" on
load. Rewrote to 927 chars, lossless on routing signals — all five fire
triggers, all three don't-fire conditions, and the decisive heuristic are
preserved. Stripped duplicate verb listings, parenthetical examples on each
trigger, and padding prose.

README + site install panes now document `~/.codex/skills/hallmark/` (personal)
and `.codex/skills/hallmark/` (project-scoped) for Codex, replacing the prior
"manual / git clone" placeholder.

README.md

@@ -116,7 +116,11 @@ Each page is its own self-contained HTML + CSS — no shared theme, no shared la
 npx skills add nutlope/hallmark
 ```
 
-Or copy [`SKILL.md`](SKILL.md) + [`references/`](references/) into `~/.claude/skills/hallmark/` (Claude Code) or `.cursor/rules/hallmark.mdc` (Cursor — body of `SKILL.md`, no frontmatter).
+Or copy [`SKILL.md`](SKILL.md) + [`references/`](references/) into one of:
+
+- **Claude Code** — `~/.claude/skills/hallmark/`
+- **Cursor** — `.cursor/rules/hallmark.mdc` (body of `SKILL.md`, no frontmatter)
+- **Codex** — `~/.codex/skills/hallmark/` (personal, all projects) or `.codex/skills/hallmark/` (project-scoped, commit to repo)
 
 ## Updating
 

SKILL.md

@@ -1,6 +1,6 @@
 ---
 name: hallmark
-description: Anti-AI-slop design skill — generate distinctive landing pages, audit existing UIs, redesign templated pages, or study an admired URL / screenshot to extract its DNA. Use one of the verbs `audit <target>`, `redesign <target>`, `study <URL or screenshot>`, or just ask Hallmark to build you a new page and it will fire. — Fires when ANY of these match — (1) the user names one of Hallmark's explicit verbs (`audit`, `redesign`, `study`, e.g. "audit this UI", "redesign this page", "study this screenshot", "study this URL"); (2) the user says a UI "feels AI-generated", "looks templated", "looks like every other AI page", or asks to "make it less AI-generated"; (3) the user attaches a screenshot OR pastes a URL of a design they admire and wants the DNA extracted (the `study` verb); (4) the user invokes the skill by name ("use Hallmark", "/hallmark"); OR (5) the user asks for a GREENFIELD full-page or full-site build with no existing styled UI to preserve — e.g. "build me a landing page for X", "make the marketing site for Y", "design the homepage for Z", "create a new product page from scratch", "build a portfolio site". DO NOT trigger on (i) component-scope requests ("design a button", "add a navbar", "fix this form", "build me a modal"); (ii) iteration on an existing styled page or codebase ("tweak the spacing", "update the hero copy on my page", "make the CTA bigger", "add a section to this layout") — anything where preserving the current aesthetic matters; (iii) any request inside a codebase that already has a design system or styled pages, unless the user explicitly invokes Hallmark by name. The decisive signal — is there existing styled UI here that the user wants preserved? If yes, stay silent and let frontend-design or other tools handle it. If no (true greenfield page/site), fire.
+description: Anti-AI-slop design skill — landing pages, audits, redesigns, and DNA-extraction from URLs or screenshots. Four verbs: `audit <target>`, `redesign <target>`, `study <URL | screenshot>`, or default (build new). Fires when ANY: (1) user names a verb; (2) user says a UI feels AI-generated, looks templated, or asks to make it less AI-generated; (3) user attaches a screenshot or URL of a design they admire (`study`); (4) user invokes Hallmark by name; (5) user asks for a greenfield full-page or full-site build with no existing styled UI. Does NOT fire on: (i) component-scope requests (button, navbar, form, modal); (ii) iteration on an existing styled page (tweaks, copy edits, adding a section); (iii) any request inside a codebase with an existing design system, unless Hallmark is invoked by name. Decisive signal: is there existing styled UI the user wants preserved? If yes, stay silent. If no (true greenfield), fire.
 version: 1.0.0
 ---
 

site/index.html

@@ -800,9 +800,9 @@
               <code class="harness__path">.cursor/rules/hallmark.mdc</code>
               <span class="harness__status harness__status--ok">auto-detected</span>
             </li>
-            <li class="harness"> <span class="harness__name">Codex &amp; others</span>
-              <code class="harness__path">git clone · copy skill/</code>
-              <span class="harness__status">manual</span>
+            <li class="harness"> <span class="harness__name">Codex</span>
+              <code class="harness__path">~/.codex/skills/hallmark/</code>
+              <span class="harness__status harness__status--ok">auto-detected</span>
             </li>
           </ul>
         </div>