When Does Hallmark Switch to the Custom Genre and What Are Its Depths?
Hallmark switches to the Custom genre during the initial "Genre detection" stage when a brief contains an explicit custom request, brand-mood reference, or singular structural vision, offering two depths: Tuned Custom (palette and font pairing) and Bespoke Custom (full structural redesign from first principles).
The open-source Hallmark repository by Nutlope implements a sophisticated design flow that determines when to abandon default catalog themes in favor of fully custom executions. Understanding when Hallmark switches to the Custom genre and what depths are available is essential for developers extending the system or writing briefs that trigger bespoke outputs. This analysis examines the trigger conditions defined in custom-theme.md and the decision logic in SKILL.md to explain exactly how the Custom branch activates and what design latitude it permits.
Trigger Conditions for the Custom Genre Switch
During Step 1 of the design flow, Hallmark silently defaults to the editorial genre unless specific signals fire. According to SKILL.md, the genre detection logic evaluates the brief against three explicit conditions documented in /skills/hallmark/references/custom-theme.md【L18-L24】.
Explicit Custom Requests
The most direct trigger occurs when users include keywords like custom, custom theme, or make it ours in their brief. Hallmark's parser scans for the custom keyword to immediately flag the request for the Custom theme branch.
Brand-Mood References
Visual brand cues automatically trigger the switch. When a brief contains attached colour assets—such as Pantone chips, moodboards, or colour swatches—Hallmark detects the presence of a brand-mood reference and routes to the Custom genre to accommodate the specific chromatic requirements.
Singular Structural Vision
The third trigger involves narrative demands for unique page architecture. Phrases indicating "no theme", "from scratch", or "fully bespoke" composition signal that the user requires a structural redesign rather than a themed template, forcing Hallmark into the deepest Custom depth.
The Two Depths of Hallmark's Custom Theme
The Custom genre is not binary; it offers a spectrum of depth that determines how much of the page is bespoke. The /skills/hallmark/references/custom-theme.md file defines two distinct levels【L3-L5】【L12-L14】.
Tuned Custom (Lightweight Depth)
At its lightest, Tuned Custom generates a complete OKLCH colour palette paired with a free-font selection while retaining Hallmark's existing macrostructures. This depth suits brand-aligned projects that need unique chromatic identity without rebuilding layout systems. Hallmark injects custom CSS properties like --color-paper and --font-display into the stylesheet while preserving the underlying grid and component architecture.
Bespoke Custom (Maximum Depth)
Bespoke Custom represents the deepest implementation, where Hallmark designs the page from first principles. This depth triggers only when the brief contains a singular structural vision, resulting in a new palette, new typography, and a brand-new composition that discards all catalog macrostructures. Even at this maximum depth, the output must still satisfy the universal "slop-test" gates for accessibility and branding constraints defined in /skills/hallmark/references/slop-test.md.
Implementation Examples in the Hallmark Source
The following code examples demonstrate how Hallmark marks custom-theme runs and implements the generated tokens.
Tuned Custom Stamp
Hallmark generates this comment block when executing a Tuned Custom run:
/* Hallmark · route: custom (tuned) · theme: custom · vibe: "archival warmth, hand‑set, no varnish" · paper: oklch(94% 0.020 65) · accent: oklch(58% 0.16 35) */
Source: Example in custom-theme.md【L28-L30】.
Bespoke Custom Stamp
For Bespoke Custom depths, Hallmark outputs a stamp indicating structural redesign:
/* Hallmark · route: custom (bespoke) · structure: <one‑line shape> · idea: "the page feels like a flowing paper‑trail that reveals data as you scroll" */
Source: custom-theme.md "Bespoke depth" section【L50-L54】.
CSS Token Injection
Hallmark injects these custom properties into the page’s stylesheet during a Tuned Custom execution:
:root {
--color-paper: oklch(94% 0.020 65);
--color-accent: oklch(58% 0.16 35);
--font-display: "Fraunces", serif;
--font-body: "Source Serif 4", serif;
}
See the "Export formats" reference for how Hallmark emits these tokens【L49-L56】.
Prompt Interaction Trigger
This example shows how a user prompt activates the Custom genre branch:
User: "I want a landing page for Coffeebox with a warm, hand‑set feel – make a custom theme."
Hallmark: (detects explicit "custom" request → loads custom-theme.md)
Summary
- Hallmark evaluates briefs during the "Genre detection" stage in
SKILL.md【L230-L238】 to determine whether to switch from the default editorial genre to the Custom genre. - The switch activates upon detecting one of three signals: explicit custom keywords, attached brand-mood colour assets, or narrative demanding bespoke composition.
- The Custom genre provides two depths: Tuned Custom (OKLCH palette plus fonts, existing structures) and Bespoke Custom (first-principles design of palette, typography, and layout).
- Both depths must pass the universal slop-test gates for quality assurance.
- Generated themes output CSS custom properties as documented in
/skills/hallmark/references/export-formats.md【L49-L56】.
Frequently Asked Questions
What triggers Hallmark to use the Custom genre instead of the default catalog?
Hallmark switches to the Custom genre when the brief contains an explicit request for custom work (keywords like "custom" or "make it ours"), includes visual brand assets such as colour swatches or Pantone references, or demands a unique structural composition using phrases like "from scratch" or "fully bespoke". These conditions are evaluated during Step 1 of the design flow defined in SKILL.md.
What is the difference between Tuned and Bespoke Custom depths?
Tuned Custom generates a complete OKLCH colour palette and free-font pairing while preserving Hallmark's existing macrostructures, making it ideal for brand-tuned but structurally standard pages. Bespoke Custom discards all catalog macrostructures to design the page's structure and composition from first principles, triggered only when the brief explicitly demands a unique layout architecture.
Where is the Custom genre logic documented in the Hallmark repository?
The primary documentation resides in /skills/hallmark/references/custom-theme.md, which defines the trigger signals and depth spectrum. The decision logic that routes to this file during genre detection is implemented in /skills/hallmark/SKILL.md within the "Genre detection" section. Quality constraints that apply to all custom work are listed in /skills/hallmark/references/slop-test.md.
Does a Bespoke Custom theme still follow Hallmark's quality constraints?
Yes. Even when operating at the deepest Bespoke Custom depth, Hallmark must satisfy the universal "slop-test" gates. These constraints ensure that fully bespoke pages maintain accessibility standards, branding coherence, and avoid AI-generation fingerprints, regardless of how radically the structure diverges from catalog templates.
Have a question about this repo?
These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:
curl -s "https://instagit.com/install.md" Maintain an open-source project? Get it listed too →