hallmark

Generates and audits web UI designs that avoid recognizable AI-generated layout patterns.

3|Updated Jul 28, 2026
One-click install
npx skills add https://github.com/marcmarti9/agentit --skill hallmark-marcmarti9
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: hallmark
Source: https://github.com/marcmarti9/agentit/tree/main/skills/hallmark
Command: npx skills add https://github.com/marcmarti9/agentit --skill hallmark-marcmarti9

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? AI coding assistants produce UIs that all look the same: purple-gradient heroes, three-column feature grids, Inter everywhere, and identical nav and footer shapes. Hallmark encodes a rule set of anti-patterns, macrostructures, themes, and typography discipline so generated pages and components look deliberately designed rather than templated. ## Core Features & Use Cases - Design flow for new pages: Runs a pre-flight scan of the existing project (fonts, palette, framework, motion libraries), asks an audience/use-case/tone gate, then picks one of 21 named macrostructures and a rotating theme catalog to build structurally varied pages. - Audit, redesign, and study verbs: hallmark audit scores a target against a named anti-pattern list and returns a ranked punch list; hallmark redesign reworks visual structure inside existing implementation boundaries; hallmark study extracts design DNA from a screenshot or URL into a diagnosis or portable design.md. - Component-scope mode: Detects single-element briefs (button, card, modal) and emits the component plus an 8-state demo wrapper covering default, hover, focus, active, disabled, loading, error, and success states. - Use Case: Ask your coding agent to build a SaaS landing page; Hallmark scans the repo, preserves the existing Tailwind tokens, selects a non-repeating macrostructure and theme, and ships responsive markup verified at 320/375/414/768 px with locked design tokens. ## Quick Start Ask your coding agent to design a landing page for your product and let Hallmark run its pre-flight scan and design flow before writing any code.

Frequently Asked Questions about hallmark

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I make AI-generated landing pages look less generic?▼

Invoke Hallmark before building: it scans your project for existing fonts, palettes, and frameworks, asks about audience, use case, and tone, then picks one of 21 named macrostructures and a rotating theme so the output does not repeat the default hero-grid-CTA template.

How to audit an existing page for AI design slop?▼

Run `hallmark audit <target>`. It reads the target, scores it against a named anti-pattern list (purple-gradient heroes, Inter-everywhere, card-in-card, re-drawn browser chrome, invented metrics), and returns a ranked punch list without editing any files.

Can Hallmark redesign a page without breaking my codebase?▼

Yes. The redesign verb preserves existing routes, component ownership, copy intent, and information architecture, replacing only the visual and interaction layer. It states the exact files it will modify beforehand, and deletions require explicit confirmation.

Does Hallmark work with Tailwind, Next.js, Astro, Vue, or Svelte projects?▼

Yes. The pre-flight scan detects frameworks via package.json and config files, reads existing Tailwind theme extensions and design tokens, and preserves them. Components are emitted in the project's conventions, consuming tokens by name rather than inline values.

What does Hallmark check for mobile responsiveness?▼

Every emitted page is verified at 320, 375, 414, and 768 px widths. Hard requirements include no horizontal scroll with overflow-x: clip, no two-line clickable text, minmax(0, 1fr) on image-bearing grid tracks, and single-column section heads on mobile.

When should I use component scope instead of the full page design flow?▼

Use component scope when the brief names a single UI element like a button, card, or modal, or targets one component file. It skips macrostructure and nav/footer picks, and emits the component plus an 8-state demo wrapper showing default through success states.