How the Default Hallmark Behavior Differs from Its Explicit Verbs

When invoked without arguments, Hallmark enters default mode to generate a brand-new UI from scratch by automatically selecting a macro-structure and running 57 slop-test gates, whereas its three explicit verbs—audit, redesign, and study—operate exclusively on existing assets to analyze, transform, or extract design patterns rather than creating fresh interfaces.

Hallmark is an open-source design skill available in the Nutlope/hallmark repository that provides a structured command-line interface for UI generation and analysis. Understanding how the default Hallmark behavior differs from its explicit verbs is crucial for selecting the appropriate workflow, whether you need to scaffold a new interface or evaluate an existing implementation against anti-patterns.

Understanding the Default Hallmark Behavior

Running the hallmark command without any arguments triggers the default creation pipeline. According to the repository's documentation in README.md (lines 17-24), this mode automatically chooses a macro-structure, applies the full rule-set defined in skills/hallmark/SKILL.md, executes the complete suite of 57 slop-test gates, and returns a finished site.

This default behavior is unique among Hallmark's capabilities because it is the only mode that creates a brand-new page from scratch. It does not require an existing codebase or design asset to function, instead generating fresh HTML, CSS, and structural decisions based on its internal design principles.

# Default mode - generates a completely new UI

hallmark

Hallmark's Explicit Verbs

When you provide a specific verb, Hallmark shifts from generative creation to operations on existing designs. As implemented in the source code, these three explicit verbs work on current assets rather than blank slates.

The Audit Verb

The audit command scores an existing codebase against Hallmark's anti-patterns and produces a punch-list of issues without making any edits to the source files.

Unlike the default behavior, hallmark audit does not generate a UI; it strictly evaluates the current implementation and reports findings. This is useful for quality assurance passes on legacy codebases.

# Audit mode - evaluates existing code

hallmark audit path/to/project

The Redesign Verb

The redesign command preserves your existing copy, information architecture, and brand assets while discarding the current macro-structure. It then rebuilds the page with a different fingerprint, effectively giving your content a new structural container.

This mode differs from the default because it re-structures an existing design rather than starting from a blank slate, maintaining continuity of content while changing the presentation layer.

# Redesign mode - keeps copy, changes layout

hallmark redesign path/to/project

The Study Verb

The study command extracts the "DNA" of a design you admire—analyzing macrostructure, type-pairings, and colour anchors—from either a screenshot file or a URL. It optionally emits a portable design.md file for hand-off to other AI tools.

This mode is investigative rather than generative. Unlike the default behavior that outputs a ready-to-use UI, study produces a description of an existing design for analysis or replication purposes.

# Study mode - extracts design DNA from reference

hallmark study https://example.com/design.png

Source Code Implementation

The distinction between default behavior and explicit verbs is encoded across several key files in the Nutlope/hallmark repository:

• README.md: Documents the four operational modes (default plus three verbs) and their CLI usage patterns
• skills/hallmark/SKILL.md: Contains the core rule-set that powers both the default UI generation pipeline and the verb-specific evaluation criteria
• skills/hallmark/references/custom-theme.md: Details the "Custom" pathway used when overriding the default macrostructure selection
• site/js/main.js: Serves as the client-side entry point that hooks Hallmark commands to the user interface

These files collectively determine whether Hallmark executes its full creation flow or branches into analysis, transformation, or extraction logic.

Summary

• Default mode (hallmark): Creates new UIs from scratch by selecting macro-structures and running 57 slop-test gates; the only generative mode that doesn't require existing assets
• Audit verb: Analyzes existing codebases and reports anti-patterns without modifying files
• Redesign verb: Preserves content and brand assets while rebuilding the macro-structure with a new layout fingerprint
• Study verb: Extracts design DNA from screenshots or URLs into portable documentation without generating usable UI code

Frequently Asked Questions

Can I run Hallmark without any arguments to modify an existing project?

No. The default Hallmark behavior with no arguments is strictly generative and creates a brand-new UI from scratch. To work with an existing project, you must use one of the explicit verbs: audit to evaluate it, redesign to restructure it while keeping content, or study to analyze reference designs.

What happens to my existing content when using the redesign verb?

The redesign verb preserves your copy, information architecture, and brand assets while discarding the current macro-structure. It rebuilds the page with a different fingerprint, effectively giving your existing content a new structural container and visual layout without rewriting the underlying text or brand elements.

Does the study verb generate HTML or CSS like the default mode?

No. Unlike the default behavior that returns a finished site, the study verb is investigative and outputs a description of the design—specifically extracting macrostructure, type-pairings, and colour anchors into a portable design.md file suitable for hand-off to other AI tools or documentation purposes.

Where are the rules for the 57 slop-test gates defined?

The 57 slop-test gates referenced in the default creation pipeline are defined within skills/hallmark/SKILL.md, which serves as the core rule-set powering Hallmark's UI generation and quality assurance behaviors across all modes.

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