hallmark-designlisted

# Hallmark Design Adapted from `Nutlope/hallmark`, commit `aeb42fb354ff4efa36ab475773a082315a3af2ce`, MIT. Use this as an opt-in creative-direction workflow. It complements the general frontend skills; it is not the default for ordinary application UI, dashboards, forms, or small component changes. ## Modes - **Build:** create a new page whose structure and visual language fit the actual brief. - **Audit:** inspect existing UI and return a ranked visual/UX punch list. Do not edit. - **Redesign:** preserve routes, copy intent, information architecture, and existing ownership; change only the visual and interaction layer in scope. - **Study:** extract portable design DNA from a user-provided screenshot or a public reference URL. Describe structure, type, colour, spacing, imagery, and interaction patterns. Never pixel-clone, copy a paid template, or reproduce protected artwork. If the user supplies only a screenshot or URL, ask whether they want a study or a fresh build inspired by it. ## Before Editing 1. Identify whether this is a page or a component. For a component, follow the existing project system and verify relevant states; do not invent a page-wide visual system. 2. Inspect the repository for its framework, design tokens, type stack, spacing scale, component library, responsive conventions, and motion support. 3. State the files expected to change. Do not delete routes, production components, or asset directories without explicit confirmation. 4. Preserve the exi