Apply an anti-AI-slop design workflow to pages, components, audits, and redesigns with Hallmark
Give coding agents a design skill for greenfield UI, component work, audits, redesigns, and visual DNA extraction from screenshots or URLs.
npx skills add agentskillexchange/skills --skill apply-an-anti-ai-slop-design-workflow-to-pages-components-audits-and-redesigns-with-hallmark
npx skills add nutlope/hallmark, or copy skills/hallmark/SKILL.md and references into the documented Claude Code, Cursor, or Codex skill/rules directory.Use Hallmark when a coding agent needs to review, generate, or redesign UI with a bounded design workflow rather than producing another generic page. The skill routes briefs into design, audit, redesign, study, or component-scope flows; reads existing project signals before editing; applies theme and layout discipline; and requires responsive checks across narrow mobile widths. A user should invoke it instead of using a design product normally when the work is inside a codebase or agent-generated artifact and the missing piece is design judgment, critique, or visual structure. The scope boundary is design guidance and implementation discipline for coding agents: page generation, component demos, audits, redesigns, and style extraction. It is not a full UI framework, asset marketplace, or standalone design app.
What this skill actually does
Inputs and prerequisites: A supported coding agent such as Claude Code, Cursor, or Codex; project files or a target screenshot/URL for audit, study, redesign, or implementation work.
Setup notes: Install with npx skills add nutlope/hallmark , or copy skills/hallmark/SKILL.md and references into the documented Claude Code, Cursor, or Codex skill/rules directory.
Source and verification boundary: use https://www.usehallmark.com/ as the canonical reference before running the workflow; keep commands, API calls, CLI usage, and generated outputs reviewable against that upstream source.
Framework fit: publish this as a Multi-Framework workflow only when the operator can invoke the documented toolchain directly, rather than treating the upstream project as a generic product listing.