External/hallmark
1
0
Fork 0
mirror of https://github.com/Nutlope/hallmark.git synced 2026-08-14 12:35:33 +02:00
Code Issues Packages Projects Releases Wiki Activity

Fix · /hallmark slash-picker description leads with what the skill does

Browse Source 
The frontmatter description opened with "Use this skill when ANY of these fire" — agent-facing trigger logic. Users typing /hall in the slash picker saw the truncated preview as "Use this skill when ANY of these fire — (1) the user names one of Hallmark's explicit verbs..." which says nothing about what Hallmark actually does.

Prepended a one-line user-facing summary so the picker preview reads as: "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." plus a usage hint with the four verbs. The full 5-condition trigger logic stays underneath unchanged so Claude's auto-fire behaviour is preserved.
This commit is contained in:
Youssef
2026-05-18 16:43:14 +01:00
parent 9f907ad38e
commit 1552cd2b21
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files
skill/SKILL.md
+1 -1
View File
@@ -1,6 +1,6 @@
---
name: hallmark
description: Use this skill when ANY of these fire — (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 — 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: (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.
version: 1.0.0
---