# Limitations of Hallmark AI: Understanding the Design-Only Skill Boundaries > Discover the design-only skill boundaries of Hallmark AI. Learn what it can and cannot do to ensure trustworthy visual design output from Nutlope. - Repository: [Hassan El Mghari/hallmark](https://github.com/Nutlope/hallmark) - Tags: deep-dive - Published: 2026-07-25 --- **Hallmark AI is strictly bounded to visual design tasks and will politely refuse requests for content creation, business logic, or unsupported visual styles to maintain trustworthy output.** Hallmark AI is a specialized **design-only skill** built for AI coding assistants such as Claude Code, Cursor, and Codex. According to the Nutlope/hallmark repository, its architecture deliberately constrains functionality to prevent over-automation and protect surrounding codebases from unintended changes. These limitations ensure that every output remains within the visual design domain, never crossing into content generation, data manipulation, or deceptive UI patterns. ## Core Design Boundaries (contract.md) The foundational constraints of Hallmark AI are defined in [`skills/hallmark/references/contract.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/contract.md). Lines 18-24 establish explicit "will not" statements that bound the skill's operation to taste-based rearrangement rather than invention. ### No Content Creation Hallmark **does not generate original content**. The skill only rearranges existing copy, typography, colour palettes, and layouts provided by the user. As specified in the contract, Hallmark will not invent product copy, brand identity statements, or marketing messaging. Any missing copy must be supplied by the user rather than fabricated by the AI. ### No Business Logic Implementation The skill **focuses exclusively on the presentation layer**. Hallmark does not write data-fetching hooks, state-management logic, API integrations, or backend code. When business logic is required, the skill expects manual implementation or delegation to another appropriate skill, maintaining strict separation between visual design and functional implementation. ### No Arbitrary Visual Style Enforcement Hallmark **cannot force specific visual aesthetics** such as dark-mode, glass-morphism, or brutalist design. According to [`contract.md`](https://github.com/Nutlope/hallmark/blob/main/contract.md), the visual style strictly follows the *genre* and *theme* the user explicitly chooses. The skill maintains a catalog of 20 named themes and will not override user directives with unsolicited stylistic choices. ## Anti-Pattern Restrictions (anti-patterns.md) The [`skills/hallmark/references/anti-patterns.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/anti-patterns.md) file enumerates specific prohibited behaviors that would degrade output quality or introduce deceptive elements. ### Prohibition on Invented Metrics Hallmark **never fabricates statistics**, percentages, testimonials, or performance data. Per the "Invented metrics" section, all numerical values displayed in UI must be real data, explicit placeholders (marked with "—"), or clearly labelled "to-confirm" values. This prevents the generation of convincing but fraudulent social proof elements. ### Strict Token System Requirements The skill **rejects mid-render token improvisation**. Per the relevant section in [`anti-patterns.md`](https://github.com/Nutlope/hallmark/blob/main/anti-patterns.md), every colour and font must be referenced via design tokens defined in the token block. Direct hex codes, OKLCH values, or inline `font-family` strings are automatically rejected. New values must be formally added to the token system before they can be referenced in generated code. ### Ban on Artificial UI Chrome Hallmark **never generates fake browser frames, IDE windows, or device chrome**. As documented in the "Re-drawn UI chrome" section, the skill only uses real screenshots or minimal borders in presentations. Fake UI chrome is explicitly categorized as "slop" and is universally prohibited to maintain professional presentation standards. ## Technical Constraints Beyond design philosophy, Hallmark enforces rigid technical limitations that affect output structure and compatibility. ### Mobile Responsiveness Requirements Every output **must render cleanly at specific breakpoints**: 320px, 375px, 414px, and 768px. As documented in [`skills/hallmark/references/responsive.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/responsive.md) under "Mobile — non-negotiable", horizontal scroll, hidden overflow, two-line clickable text, or missing `minmax` grid tracks constitute automatic failures. The skill validates mobile compatibility as non-negotiable. ### Component Scope Limitations When operating in **component-scope mode**, Hallmark skips macrostructure, navigation, footer elements, hero enrichment, and diversification rules. As detailed in [`skills/hallmark/SKILL.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/SKILL.md) (lines 60-90), component runs emit only the targeted UI element plus an **8-state demo wrapper** saved as [`.preview.html`](https://github.com/Nutlope/hallmark/blob/main/.preview.html). Page-level scaffolding is deliberately excluded to maintain atomic component purity. ## Quality Control Gates (slop-test.md) Before emitting any design, Hallmark executes a **pre-emit self-critique** defined in [`skills/hallmark/references/slop-test.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/slop-test.md). The skill scores its output against six axes, and any design scoring below 3 on any axis is automatically revised. This gate, documented in the "Pre-emit self-critique" section, prevents low-quality "slop" from reaching the final output and maintains consistent design standards. ## What Happens When Limits Are Exceeded When users request operations outside these boundaries, Hallmark responds with refusal messages rather than silent failure or scope creep. ```bash # Attempting to generate made-up metrics results in refusal hallmark redesign ./src/pages/Pricing.tsx # Response: "I can redesign the layout, but I can't invent conversion # numbers. Please provide real data or leave a placeholder (—)." ``` ```bash # Requesting unsupported visual styles triggers boundary enforcement hallmark redesign ./src/App.vue --theme dark # Response: "The dark-mode theme is a visual style. Hallmark only picks # from its catalog of 20 named themes; it won't force a dark mode. # Choose a catalog theme or request a custom palette." ``` ```bash # Component-scope redesigns exclude page-level elements hallmark redesign ./components/Button.tsx # Output: Self-contained Button component + .preview.html showing 8 states. # No hero, nav, or footer sections are generated. ``` ```bash # Auditing non-UI files returns service refusal hallmark audit ./src/api/auth.ts # Response: "The target is not a UI artifact. I can only audit visual # designs against the anti-pattern list." ``` ## Summary Hallmark AI's limitations create a **tight safety rail** that confines operation to trustworthy visual design: - **Content-safe**: No generation of copy, metrics, or testimonials - **Logic-free**: No implementation of data-fetching, state, or backend code - **Token-strict**: No improvisation outside defined design systems - **Mobile-rigid**: Mandatory compliance with 320px/375px/414px/768px breakpoints - **Scope-aware**: Distinct page-level and component-level operation modes - **Quality-gated**: Six-axis self-critique prevents low-quality emission These boundaries ensure Hallmark operates as a reliable design assistant rather than an unbounded generative agent. ## Frequently Asked Questions ### Can Hallmark AI create marketing copy for my landing page? No. Hallmark AI explicitly refuses to invent product copy, brand identity statements, or marketing content. According to [`skills/hallmark/references/contract.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/contract.md), the skill only rearranges existing copy supplied by the user. Any missing text must be provided manually or left as clearly marked placeholders. ### Why does Hallmark refuse to add dark mode to my application? Hallmark does not enforce visual styles outside its predefined catalog of 20 named themes. The skill will not arbitrarily implement dark-mode, glass-morphism, or other aesthetic trends unless the user explicitly selects a theme from the catalog that incorporates those features. This prevents unsolicited visual changes that conflict with existing design systems. ### What happens if I ask Hallmark to audit a backend API file? Hallmark will decline the request. As implemented in the skill's core logic, the `audit` verb only processes UI artifacts against the anti-pattern list defined in [`skills/hallmark/references/anti-patterns.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/anti-patterns.md). When targeting non-UI files such as [`./src/api/auth.ts`](https://github.com/Nutlope/hallmark/blob/main/./src/api/auth.ts), Hallmark responds that the target is not a visual design and cannot be evaluated against design-specific quality gates. ### Does Hallmark generate responsive designs for all screen sizes? Yes, with strict requirements. According to [`skills/hallmark/references/responsive.md`](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/responsive.md), every output must pass validation at 320px, 375px, 414px, and 768px breakpoints. Designs exhibiting horizontal scroll, hidden overflow, or inaccessible touch targets at these sizes are automatically rejected and revised before delivery.