← Search

Hallmark Design Skill for Muse
Design 🧪 Install ran in our test sandbox · Nov 18, 2026 📌 Pinned version: commit 7ec8682
Install test only, on the date shown. This does not guarantee the code is safe.
🔎 Install prompt analysis · 2026-10-13 : runs commands · uses API keys or tokens
⚙ Needs: none beyond standard skill tooling…

Hallmark Design Skill for Muse

Make AI-generated UIs look made, not generated — the anti-slop design skill.

At a glance
What
Make AI-generated UIs look made, not generated — the anti-slop design skill.
Cost
Free
Needs
none beyond standard skill tooling — no account or paid service is required. Node.js is optional: when it is available, the skill uses it for its bundled theme and sloplint scripts, and the file gives manual fallbacks when it is not. A TOGETHER_API_KEY is optional and only enables the comp step (generated stills); without one, the skill uses your material or its bundled photo library. You bring the page brief (or, naming Hallmark, a target to audit or redesign).
Install
Copy the installer prompt below into your Muse — your agent does the rest.

Version:

Quick answer

Hallmark Design is a free Muse skill that makes AI-generated UIs look made, not generated. As an anti-slop design skill, it pushes interfaces away from generic AI defaults toward deliberate, crafted design. The result feels designed by a human hand, with choices that look intentional rather than templated.

⌁

Install

Copy the install package below, then paste it into Muse🧪 Install ran in our test sandbox · Nov 18, 2026📌 Pinned version: commit 7ec8682

Step 0 — before installing anything: read this install prompt, summarize in a few lines what this build does and what installing it involves, then ask me to confirm before you proceed. Updated October 23, 2026: the upstream SKILL.md was rewritten from v1.1.0 to v2.0.0 (about 87% of its content changed; the file itself shrank from 67,460 to 18,239 bytes as the detail moved into references/ and a new scripts/ folder), and the description below was rewritten to match; where the previous version of this prompt says otherwise, the file now wins. What changed: (1) The study verb is gone: v1.1.0 could extract a design's DNA from a screenshot or a URL, v2.0.0 no longer does that, and its two remaining verbs, audit and redesign, now fire only when you name Hallmark; it never touches an existing design otherwise. (2) The 58-gate slop test is replaced: the gates now live in references/gates.md as a 16-rule non-waivable Floor, waivable Reflex gates and non-blocking Finish checks, and the bundled sloplint script (scripts/sloplint.mjs) checks the built page automatically, with rendered screenshots, before hand-back. (3) The theme catalog grew from 21 to 48 themes, each with its own picture, dealt by scripts/theme.mjs (deal, draw, scaffold, photos, log) against a rotation log; the 21 macrostructures are unchanged. (4) The three opening questions became one "ask once" message with four asks (material, audience, use, tone), and material now comes first: with no photos of your own, the skill places credited library stand-ins instead of inventing proof. (5) New bundled tooling: scripts/capture.mjs screenshots the real product when it can be reached, and an optional comp step can generate stills when a TOGETHER_API_KEY is set (signal 9) — optional only; the previous prompt's flat "no external services or APIs" is corrected accordingly, and the safety check in step 2 names this openly. The previous prompt also said the allowed hosts are declared in the SKILL.md; the new file declares none, so that check is gone. This prompt was updated to match, including the integrity check in step 4. Prerequisites: none beyond standard skill tooling — no account or paid service is required. Node.js is optional: when it is available, the skill uses it for its bundled theme and sloplint scripts, and the file gives manual fallbacks when it is not. A TOGETHER_API_KEY is optional and only enables the comp step (generated stills); without one, the skill uses your material or its bundled photo library. You bring the page brief (or, naming Hallmark, a target to audit or redesign). Install "Hallmark Design Skill for Muse" for me. Anti-"AI slop" design methodology for new web pages, v2.0.0: it makes AI-built pages look made, not generated. It starts with a pre-flight that reads the project before asking anything (a design.md or DESIGN.md at the root is a locked system that overrides everything; a real brand is never themed from memory), then asks once, in a single message (material, audience, use, tone; skipped fields are inferred and stated, facts are never inferred or invented), shapes the page from the material and the anatomy of the job (21 named macrostructures), deals one of 48 themes with the bundled theme script (the deal and the draw are logged in .hallmark/log.json so consecutive builds differ; a custom direction replaces the deal only when you ask for it), states its Picks block once, builds hero-first from the scaffold (tokens.css and base.css), and finishes with a sweep: the bundled sloplint script with rendered screenshots until clean, the judged gates, and a finish review in fresh context. A 16-rule Floor binds every output and cannot be waived: every colour and font goes through a declared token, no transition: all, :focus-visible on every interactive element, a reduced-motion fallback on every animation, no invented metric, testimonial, logo wall or case-study count, about 80 words on any one screen, and eight states on every control. Verbs, only when you name Hallmark: hallmark audit <target> returns a report and edits nothing; hallmark redesign <target> is a full redesign that keeps the target's content and wiring. Component scope, app screens and fast mode live in references/flow.md. Repository: https://github.com/nutlope/hallmark/tree/7ec868225c6caa040558c321ee0fefa0e73f83a8/skills/hallmark (the skill is the whole skills/hallmark/ folder at that commit: SKILL.md plus references/, scripts/ and agents/) Pinned version: install the code at commit 7ec868225c6caa040558c321ee0fefa0e73f83a8 exactly (Skill Harbor tested this version). Do not substitute a newer version. If this commit is unreachable, stop and tell me. 1. Fetch the whole skills/hallmark/ folder at the pinned commit (SKILL.md, references/, scripts/ and agents/) into a temporary folder. 2. Safety check: review the SKILL.md and the bundled scripts (scripts/*.mjs) for anything suspicious (unexpected network calls, shell commands, credential harvesting). This repo should contain zero secrets in code; credentials only via the secure vault. Verify that holds here; STOP on any red flag and tell me. Tell me in plain words what the skill does when used, which services it connects to, whether it reads or sends any personal information or keys, and anything that seems unusual. Confirm these points from the files: - Nothing is sent anywhere during installation itself. In use, the bundled Node scripts run locally when Node is available: theme.mjs deals and draws themes, scaffolds tokens.css and base.css, serves the bundled photo library and writes the rotation log (.hallmark/log.json); sloplint.mjs checks the built page and, with --render, writes screenshots of it; capture.mjs screenshots your own product (a URL, a running dev server or a local app) so the page can show the real thing. - The one optional external service: if a TOGETHER_API_KEY is set in the environment, signal 9 enables an optional comp step (references/comp.md, scripts/imagegen.mjs) that generates still images through Together AI. The skill is fully usable without it (your own material, or credited library photographs). An Inspo MCP server, when one is connected, is an optional signal only. The file declares no allowed-hosts list. - The Floor's honest-copy rule binds every build: never an invented metric, testimonial, logo wall or case-study count; library photographs are stand-ins in slots your own files replace, and each is credited in the footer. Existing projects are protected: name the files you will touch first, never delete a route or a component tree without a file-level plan I approved, and existing stylesheets are append-only. 3. When I say yes, install it as a skill: copy the whole hallmark folder (SKILL.md, references/, scripts/ and agents/) into the agent's skills directory, in a folder named "hallmark", keeping the subfolder structure as it is. 4. Verify with no network calls: frontmatter valid, files in place, and the SHA-256 of the fetched SKILL.md equals 25a1ff92d925b2389e8409f42fb8ad7e033fceca8b5d1f07ed4ca4c28da53dc3 — STOP and tell me if it does not match. 5. Report what was installed, where, and what I still need to do myself (e.g. bring the page brief and whatever material the page can show, or name Hallmark with a target for audit or redesign). GitHub is optional: if I have a GitHub account or the gh CLI, you may use it; otherwise public access is fine. Never require it unless it's in the prerequisites above. Rules: don't touch anything outside the temp folder and the install target. If anything looks off, stop and ask me.

🔒 Security, provenance and what this touches
🧭 What this touches
  • It can run commands on your Muse’s computer.
  • It works with an API key or a token that you provide.
Install prompt analysis · 2026-10-13
🔒 Security and provenance
📌 Pinned version: commit 7ec8682 · 2026-10-23
🧪 Install ran in our test sandbox · Nov 18, 2026
👁 Observed during the install test · Nov 18, 2026 : no network contact
🔎 Install prompt analysis · 2026-10-13 : runs commands · uses API keys or tokens
What the scan found — excerpts from the install prompt
  • runs commands — - Nothing is sent anywhere during installation itself. In use, the bundled Node scripts run locally when Node
  • uses API keys or tokens — Updated October 23, 2026: the upstream SKILL.md was rewritten from v1.1.0 to v2.0.0 (about 87% of its content · Prerequisites: none beyond standard skill tooling — no account or paid service is required. Node.js is optiona · - The one optional external service: if a TOGETHER_API_KEY is set in the environment, signal 9 enables an opti
🔎 Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify
Wanna be extra careful?

The install prompt below already includes the vetting steps: your agent follows the community checklist before installing anything with executable code. Want more?

How to check a skill before installing →

✓

Verification certificate

Dated facts about what was checked for this listing, and how. This is not a safety certification.

Pinned version
7ec8682 · 2026-10-23
Sandbox install test
Install ran in our test sandbox · Nov 18, 2026
Creator identity
Not verified
Fingerprint watch
Last checked · Nov 19, 2026 : no change detected in the files linked by this install prompt
Install prompt analysis
2026-10-13 : runs commands · uses API keys or tokens

Skill Harbor never reviews the code of a listed skill. These are dated facts about the install prompt and our install test, not a safety certification. Review a skill yourself before you install it. How we verify

?

Questions

How do I install a skill?

Every product page includes a copy-paste install prompt. Paste it into your Muse and it sets the skill up for you — no manual configuration.

Where does my money go?

Straight to the seller. Skill Harbor never processes payments: checkout happens on the seller’s own page, usually Stripe.

What does the ✓ next to a creator’s name mean?

It means we confirmed the identity of the person behind the listing. It says nothing about the code itself — always check a skill before installing it.