What Information Does the Hallmark Design-Context Gate Request?

The Hallmark Design-context gate requests three essential inputs—Audience, Use case, and Tone—to guide every subsequent design decision before generating any code.

The Design-context gate serves as Hallmark's initial checkpoint immediately following the optional pre-flight scan, establishing the foundational constraints that shape layout, typography, and interaction flow. According to the Nutlope/hallmark source code, this gate is strictly enforced for most operations and ensures the AI understands user intent before proceeding with implementation.

The Three Required Inputs

The gate collects information across three distinct dimensions that determine language choices, visual hierarchy, and overall aesthetic direction.

Audience

Audience defines who will use the page and what they already know about the subject matter. This input directly influences terminology complexity, accessibility requirements, and information architecture. For example, a page targeting junior developers requires different explanatory depth than one aimed at senior engineers.

Use Case

Use case identifies the single core action the page should enable. Valid examples include sign-up, subscribe, read, or buy. This parameter drives decisions regarding call-to-action prominence, layout structure, and interaction flow. The gate rejects vague objectives in favor of specific, measurable actions that can be optimized through design.

Tone

Tone specifies an extreme stylistic direction rather than generic descriptors. Acceptable values include editorial, brutalist, soft, utilitarian, luxury, playful, technical, or austere. Notably, phrases like "clean and modern" are explicitly invalid—the system requires polar stylistic choices that clearly dictate color palettes, typography selections, and spacing rhythms.

Interaction Flow and Fallback Behavior

When triggered, the Design-context gate presents users with a standardized prompt format:

**Before I build, I need three things:**

1. **Audience** – Who will use this? What do they care about?
2. **Use case** – What's the one action the page should drive? (Sign up? Subscribe? Read? Buy?)
3. **Tone** – Pick an extreme: editorial · brutalist · soft · utilitarian · luxury · playful · technical · austere.

Users may provide specific answers, skip individual fields, or respond with "go ahead" to allow Hallmark to infer values from the project brief. When inference occurs, the system explicitly restates its assumptions before proceeding:

Going with: audience = developers · use = sign‑up · tone = playful. If any of those is wrong, tell me and I'll redirect.

The gate remains silent only for specific command verbs including audit, study, and redesign --mood, which read context directly from a target rather than querying the user.

Implementation in the Source Code

The complete specification for the Design-context gate resides in skills/hallmark/SKILL.md at lines 203–225. This file defines the prompt templates, acceptable tone values, and fallback logic governing the gate's behavior. Additional usage examples appear throughout site/_tests/*/brief.md, demonstrating how the three inputs translate into concrete design implementations across different project scenarios.

Summary

• The Design-context gate requires three specific inputs: Audience (who uses the page), Use case (the core action), and Tone (an extreme stylistic direction).
• Users may answer directly, skip fields, or type "go ahead" to trigger automatic inference from context.
• Valid tone options include editorial, brutalist, soft, utilitarian, luxury, playful, technical, and austere—generic descriptions like "clean" are rejected.
• The gate definition lives in skills/hallmark/SKILL.md and is bypassed only for specific commands like audit or study.

Frequently Asked Questions

What happens if I skip the Design-context gate questions?

If you skip individual fields or reply "go ahead," Hallmark infers the three values from your project brief and explicitly states these assumptions before generating code. You retain the ability to correct any incorrect inferences before the design process continues.

Can I use "clean and modern" as a tone value?

No. The Design-context gate explicitly rejects generic descriptors like "clean and modern" in favor of extreme stylistic directions such as brutalist, playful, or austere. These polar choices provide the concrete constraints necessary for coherent visual language generation.

When does the Design-context gate remain silent?

The gate is silent only when processing specific command verbs including audit, study, and redesign --mood. These commands read context directly from an existing target rather than requesting new design parameters from the user.

Where is the Design-context gate defined in the codebase?

The complete gate specification, including prompt templates and validation rules, is defined in skills/hallmark/SKILL.md between lines 203 and 225. Test implementations demonstrating gate usage appear in site/_tests/*/brief.md.

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}