Skip to content

nexu-io/open-design / plugins/community/hallmark

hallmark

Flagged

Anti-AI-slop design skill for greenfield pages, audits, redesigns, and design extraction from URLs or screenshots. Use when the user asks to build a new app or landing page, wants to redesign something, invokes Hallmark by name, or uses audit/redesign/study.

FileKindSize
LICENSEother1.1 KB
SKILL.mdskill md61.5 KB
open-design.jsonconfig1.4 KB
references/anti-patterns.mdmarkdown24.6 KB
references/assets.mdmarkdown24.7 KB
references/color.mdmarkdown4.2 KB
references/component-cookbook.mdmarkdown27.9 KB
references/components/c1-outlined-chip.mdmarkdown464 B
references/components/c2-inline-form-as-cta.mdmarkdown672 B
references/components/c3-typographic-link.mdmarkdown280 B
references/components/c4-sticky-bottom-bar.mdmarkdown671 B
references/components/f1-bento-grid.mdmarkdown782 B
references/components/f2-sticky-scroll-stack.mdmarkdown899 B
references/components/f3-tabular-spec-sheet.mdmarkdown419 B
references/components/f4-step-sequence.mdmarkdown448 B
references/components/f5-annotated-screenshot.mdmarkdown410 B
references/components/f6-product-card-grid.mdmarkdown2.7 KB
references/components/ft1-mast-headed.mdmarkdown501 B
references/components/ft2-inline-rule-single-line.mdmarkdown362 B
references/components/ft3-index-style-category-list.mdmarkdown483 B
references/components/ft4-dense-typographic.mdmarkdown501 B
references/components/ft5-statement.mdmarkdown1.3 KB
references/components/ft6-letter-close.mdmarkdown1.1 KB
references/components/ft7-newsletter-first.mdmarkdown1.7 KB
references/components/ft8-marquee-scroll.mdmarkdown1.5 KB
references/components/h1-marquee.mdmarkdown507 B
references/components/h2-split-diptych.mdmarkdown600 B
references/components/h3-quote-led.mdmarkdown420 B
references/components/h4-stat-led.mdmarkdown509 B
references/components/h5-letter-hero.mdmarkdown361 B
references/components/h6-photographic-fold.mdmarkdown586 B
references/components/h7-demo-video-clipped-by-viewport-edge.mdmarkdown1.6 KB
references/components/h8-mockup-split-browser-framed.mdmarkdown1.3 KB
references/components/h9-custom-illustration-centerpiece.mdmarkdown1.4 KB
references/components/n1-wordmark-2-links.mdmarkdown388 B
references/components/n10-floating-on-scroll-morph.mdmarkdown1.4 KB
references/components/n2-floating-chip.mdmarkdown617 B
references/components/n3-side-rail.mdmarkdown536 B
references/components/n4-hidden-behind-k.mdmarkdown373 B
references/components/n5-floating-pill.mdmarkdown1.4 KB
references/components/n6-newspaper-masthead.mdmarkdown1.6 KB
references/components/n7-brutal-slab.mdmarkdown1.3 KB
references/components/n8-terminal-command.mdmarkdown1.6 KB
references/components/n9-edge-aligned-minimal.mdmarkdown867 B
references/components/s1-left-margin-numbered.mdmarkdown495 B
references/components/s2-hanging.mdmarkdown357 B
references/components/s3-sticky-pinned.mdmarkdown1.2 KB
references/components/s4-inline-no-break.mdmarkdown438 B
references/components/s5-bottom-anchored.mdmarkdown358 B
references/components/t1-pull-quote-with-marginalia.mdmarkdown465 B
references/components/t2-logo-wall-hairline.mdmarkdown733 B
references/components/t3-single-huge-quote.mdmarkdown490 B
references/components/t4-numbered-stat-strip.mdmarkdown470 B
references/contract.mdmarkdown1.3 KB
references/copy.mdmarkdown12.0 KB
references/custom-craft.mdmarkdown33.3 KB
references/custom-theme.mdmarkdown19.6 KB
references/design-md.mdmarkdown6.7 KB
references/export-formats.mdmarkdown13.3 KB
references/floating-nav.mdmarkdown5.1 KB
references/genres/atmospheric.mdmarkdown3.9 KB
references/genres/editorial.mdmarkdown3.7 KB
references/genres/modern-minimal.mdmarkdown3.9 KB
references/genres/playful.mdmarkdown3.8 KB
references/hero-enrichment.mdmarkdown30.7 KB
references/imagery-kit.mdmarkdown8.3 KB
references/interaction-and-states.mdmarkdown12.7 KB
references/layout-and-space.mdmarkdown6.0 KB
references/macrostructures.mdmarkdown11.3 KB
references/macrostructures/01-bento-grid.mdmarkdown1.8 KB
references/macrostructures/02-long-document.mdmarkdown1.7 KB
references/macrostructures/03-marquee-hero.mdmarkdown1.6 KB
references/macrostructures/04-stat-led.mdmarkdown1.6 KB
references/macrostructures/05-workbench.mdmarkdown1.7 KB
references/macrostructures/06-conversational-faq.mdmarkdown1.6 KB
references/macrostructures/07-manifesto.mdmarkdown1.7 KB
references/macrostructures/08-photographic.mdmarkdown1.5 KB
references/macrostructures/09-quote-led.mdmarkdown1.8 KB
references/macrostructures/10-specimen.mdmarkdown1.6 KB
references/macrostructures/11-catalogue.mdmarkdown1.2 KB
references/macrostructures/12-letter.mdmarkdown1.2 KB
references/macrostructures/13-index-first.mdmarkdown1.2 KB
references/macrostructures/14-narrative-workflow.mdmarkdown1.4 KB
references/macrostructures/15-split-studio.mdmarkdown1.3 KB
references/macrostructures/16-feature-stack.mdmarkdown1.4 KB
references/macrostructures/17-type-specimen.mdmarkdown1.2 KB
references/macrostructures/18-portfolio-grid.mdmarkdown1.0 KB
references/macrostructures/19-map-diagram.mdmarkdown1.2 KB
references/macrostructures/20-ecosystem-index.mdmarkdown1.2 KB
references/macrostructures/21-component-playground.mdmarkdown1.1 KB
references/microinteractions.mdmarkdown19.7 KB
references/motion.mdmarkdown4.2 KB
references/preview-examples.mdmarkdown2.8 KB
references/responsive.mdmarkdown5.8 KB
references/slop-test.mdmarkdown30.0 KB
references/structure.mdmarkdown15.7 KB
references/study.mdmarkdown41.8 KB
references/typography.mdmarkdown18.0 KB
references/verbs/audit.mdmarkdown2.7 KB
references/verbs/redesign.mdmarkdown13.5 KB

references/design-md.md

View on GitHub
# design.md — opt-in portable design system

Loaded by [`SKILL.md`](../SKILL.md) Step 6 ONLY when the user explicitly asks Hallmark to lock the current build's design system into a portable file. The default verb does NOT auto-emit `design.md`. The user iterates freely until they say the system is settled, then asks for it.

This file is **also** loaded by [`study.md`](study.md) when the user — after a successful `study` diagnosis — asks for the DNA to be emitted as a portable system. The format below is shared between the two paths; the only differences are spelled out in § Two emission paths (default vs study) and in [`study.md`](study.md) § Emitting a `design.md` from `study`.

## Triggers (phrase-only — no new verb)

Fire ONLY when the user says one of:

- *"lock the system"* / *"lock the design system"* / *"lock the DNA"* / *"lock this DNA"*
- *"give me a design.md"* / *"write a design.md"* / *"export this as a design.md"*
- *"extract this to a design system"* / *"extract the tokens"* / *"extract the DNA"*
- *"make this portable"* / *"make the DNA portable"*
- *"I want to use this in another project"*

For everything else — including the default build, the redesign verb on a single page, and free iteration on the same brief — skip. The single-page redesign and default verb stay token-portable via `tokens.css`; `design.md` is the explicit lock-in step.

## Two emission paths (default vs study)

The same `design.md` format is emitted from two different entry points. They differ in which signals seed the file and in how strict the refusal layer is.

| | **Default-verb path** (lock the system) | **Study-verb path** (lock the DNA) |
| --- | --- | --- |
| **Trigger context** | After at least one build the user has iterated on and is satisfied with | After a successful `study` diagnosis (image or URL) |
| **Source of tokens** | The build's in-memory token state | The studied DNA — exact from CSS in URL mode, estimated from bands in image mode |
| **Refusal layer** | None — the user owns the build they iterated on | Tighter — see [`study.md`](study.md) § Emission-refusal layer. URL mode requires attestation; third-party URLs are refused |
| **`## Provenance` block** | Omitted (the system is the user's own work) | Required — records source mode, URL or "image", date, attestation answer, confidence note |
| **`## Notes` block** | Optional — covers any decisions worth remembering | Required — carries the diagnosis's "anti-patterns to NOT carry over" list |

Both paths produce a `design.md` Hallmark can read on subsequent runs; the file format is uniform once written.

## Scope

- **Page-builds only.** Skip on component-scope — a single component is too small to be a system.
- **Multi-page redesign keeps existing behaviour.** `hallmark redesign --multi-page` produces the heavyweight `design.md` per [`verbs/redesign.md`](verbs/redesign.md) § Multi-page flow. That flow already implies a locked system, so the rule there is unchanged.
- **No-overwrite policy.** If `design.md` already exists at the project root, do NOT overwrite. Refresh its `## Exports` section instead and emit one line: *"design.md detected — refreshed Exports, system unchanged."*

## CTA — surface the offer in the Step 5 preview

After every default + redesign page-build, append one quiet line at the bottom of the preview block:

> *System portable? Say `lock the system` to extract this build's tokens + voice into a `design.md`.*

Skip the CTA when (a) the build is component-scope, or (b) `design.md` already exists in the project (system is already locked).

## Format (the tight version)

Write the file at the project root. Match the project's case convention (`design.md` or `DESIGN.md`). Target ~45 lines — enough to seed a real app, not so much that it becomes a wiki to maintain. The format:

````markdown
# Design — <Project name>

Locked design system. Future Hallmark runs read this file first; pages defer
to it. Amend intentionally — the file is the rule.

## System
- Genre · <editorial / modern-minimal / atmospheric / playful>
- Macrostructure · <name>
- Theme · <catalog: NAME · or · custom (vibe: "<4–8 words>")>
- Axes · <paper-band> / <display-style> / <accent-hue>

## Tokens (canonical · `tokens.css` is the source of truth)
```css
:root {
  --color-paper:      oklch(<L> <C> <H>);
  --color-paper-2:    oklch(<L> <C> <H>);
  --color-ink:        oklch(<L> <C> <H>);
  --color-ink-2:      oklch(<L> <C> <H>);
  --color-rule:       oklch(<L> <C> <H>);
  --color-accent:     oklch(<L> <C> <H>);
  --color-accent-ink: oklch(<L> <C> <H>);
  --color-focus:      oklch(<L> <C> <H>);

  --font-display: "<face>", ...;
  --font-body:    "<face>", ...;
  --font-mono:    "<face>", ...;

  /* 4-pt spacing scale, named: --space-3xs … --space-4xl. See tokens.css.   */
  /* Type scale, 1.25 (major-third) ratio: --text-xs … --text-display.       */

  --ease-out: cubic-bezier(0.16, 1, 0.3, 1);
  --dur-fast: 180ms;  --dur-base: 240ms;  --dur-slow: 320ms;

  --radius-card: <px>;  --radius-pill: <px>;  --radius-input: <px>;
}
```

## CTA voice
- Primary · <fill colour> · <radius> · <padding rhythm>
- Secondary · <outline / ghost> · <same radius>

## Motion stance
- <silent · 1–2 reveal primitives · motion-cut>
- Reduced-motion fallback · ≤150 ms opacity crossfade.

## Exports
`tokens.css` (in this project) is the source of truth. For Tailwind v4
`@theme`, DTCG `tokens.json`, or shadcn/ui CSS variables, ask *"extend
design.md with Tailwind exports"* (or the format you want) — Hallmark will
append them per [`export-formats.md`](export-formats.md).
````

State the picks aloud BEFORE writing the file. *"Genre: editorial. Macrostructure: Long Document. Theme: catalog Editorial. Locking this as the project's system."* Then write.

## After the file is written

Once `design.md` exists, [`SKILL.md`](../SKILL.md) Step 0's pre-flight scan detects it on every subsequent run. From that point on:

- All future Hallmark runs READ `design.md` first; subsequent picks (genre / theme / typography / motion / CTA voice) defer to it.
- The diversification rule INVERTS — pages must SHARE the system, not differ from each other.
- If a future page genuinely needs a different system, AMEND `design.md` with a `## Variants` section rather than overriding locally — the file evolves; per-page overrides do not.

## Why opt-in (not auto-emit)

Briefs iterate. The first build is rarely the settled design. Auto-emitting `design.md` on every default build would either churn the file across iterations or lock a weak system before the user has reviewed it. Opt-in mirrors how design teams actually work — formalise the system after the patterns hold, not on day one. The CTA in the preview block keeps the feature discoverable without forcing it.
rea-analysis-optimizationmorluto/reaOptimize REA providers and shared analysis workflows for agent context, latency, CPU, and memory while preserving correctness and Evidence. Use for analysis bottlenecks and cache or query design; CI/test-suite optimization belongs to rea-ci-tests-audit.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-ci-tests-auditmorluto/reaAudit REA CI and test suites for correctness, fixture drift, false passes, and measured performance; use for suite or workflow investigations and efficiency changes, rather than ordinary feature testing or a single test failure.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
rea-tool-designmorluto/reaAudit, investigate, design, or change REA investigation tools, CLI/MCP contracts, provider capabilities, and Evidence semantics.Stars: 472kUpdated Claude CodeCodexVerifiedInstall
ponytail-auditDietrichGebert/ponytailQuality audit of the whole repo: bugs, security, real load, missing tests, speed, and what to delete. Most important first.Stars: 194kUpdated Claude CodeCodexVerifiedInstall