Hallmark Redesign Command Options: Scope, Mood, and Multi-Page Flags

The hallmark redesign command accepts a target path plus three optional flags—--mood, --multi-page, and --genre—to control whether the tool rebuilds a single component, an entire site, or switches design genres while preserving original content and information architecture.

The hallmark redesign verb is the primary mechanism in the Nutlope/hallmark repository for rebuilding the visual structure of web pages or entire sites. According to the source specification in skills/hallmark/references/verbs/redesign.md, the command replaces only the visual and interaction layers—macrostructure, component voice, reveal patterns, and visual rhythm—while keeping copy, information architecture (IA), brand identity, and routing intact.

Command Syntax and Core Arguments

The base command requires a target and supports optional modifiers:

hallmark redesign <target> [--mood <name>] [--multi-page] [--genre <genre>]

The <target> Argument

The <target> positional argument identifies the file, directory, or glob pattern that Hallmark will redesign. As implemented in skills/hallmark/references/verbs/redesign.md, Hallmark inspects this target to determine execution scope:

  • Single file (e.g., ./src/pages/landing.tsx) triggers single-page redesign mode by default.
  • Directory (e.g., ./src/pages/), glob (e.g., "./src/**/*.tsx"), or multiple files trigger automatic multi-page detection.

Optional Flags for Tone and Scope

Three flags fine-tune the redesign behavior: --mood, --multi-page, and --genre.

--mood <name> (Tone Selection)

The --mood flag selects a tonal preset that drives the structural fingerprint of the output. The name provided is looked up in the tone libraries defined in skills/hallmark/references/typography.md and skills/hallmark/references/structure.md.

  • If omitted, Hallmark prompts the user for a one-word feeling.
  • Valid mood names map to predefined typography scales and structural rhythms.
  • Example: hallmark redesign ./hero.tsx --mood luxury

--multi-page (Force Multi-Page Mode)

While Hallmark automatically detects multi-page scenarios, the --multi-page flag forces this mode explicitly. According to skills/hallmark/references/design-md.md, this flag triggers the creation or update of a project-wide design.md (or DESIGN.md) file at the project root.

  • The design.md becomes the single source of truth for all subsequent page redesigns in the target set.
  • Ensures visual consistency across the entire site by locking the design system before applying it to individual pages.

--genre <genre> (Genre Escape-Hatch)

The --genre flag allows switching the fundamental design genre—such as from "editorial" to "modern-minimal"—by loading a genre definition from skills/hallmark/references/genres/<genre>.md.

  • This is considered an escape-hatch option only applied when the user explicitly requests a genre change.
  • Overrides default genre assumptions while still preserving the original copy and IA.

Single-Page vs. Multi-Page Redesign Logic

Hallmark determines scope through a two-tier decision tree defined in the verb specification:

  1. Single-Page Redesign: Default when the target is a single file and no multi-page signals (directory, glob, multiple files, or "whole site" references) are present. The tool redesigns the individual component or page in isolation.

  2. Multi-Page Redesign: Triggered automatically when multi-page signals are detected or when --multi-page is supplied. In this flow, Hallmark first generates the design.md file, then applies that locked design system to every page in the target set.

Both flows share immutable constraints: they preserve existing copy, information architecture, brand assets, and routing unless the user explicitly authorizes deletions or full rebuilds.

Practical Examples

These commands demonstrate the hallmark redesign options in common scenarios:


# Redesign a single component (default single-page flow)

hallmark redesign ./src/components/hero.tsx

# Redesign with a specific tonal mood

hallmark redesign ./src/pages/landing.tsx --mood luxury

# Force multi-page mode on a directory

hallmark redesign ./src/pages/ --multi-page

# Target multiple files via glob pattern

hallmark redesign "./src/**/*.tsx"

# Switch genre while redesigning a specific page

hallmark redesign ./src/pages/about.tsx --genre modern-minimal

In each execution, Hallmark announces the files it plans to modify, requests confirmation if needed, then emits redesigned markup accompanied by a brief explanation of the chosen structural fingerprint.

Source File Reference

The following files in the Nutlope/hallmark repository define the command options and behavior:

Summary

  • The hallmark redesign command requires a <target> (file, directory, or glob) and accepts --mood, --multi-page, and --genre flags.
  • --mood selects tonal presets from typography.md and structure.md to drive the visual fingerprint.
  • --multi-page forces creation of a design.md file and applies a locked design system across multiple pages.
  • --genre switches design genres by loading definitions from the genres/ folder.
  • Single-page mode is the default for individual files; multi-page mode triggers automatically for directories/globs or explicitly via flag.

Frequently Asked Questions

What happens if I don't specify a mood when running hallmark redesign?

If the --mood flag is omitted, Hallmark will interactively prompt you for a one-word feeling that describes the desired tone. The tool then maps that input to the closest matching preset in the typography and structure libraries.

Can I redesign an entire website without using the --multi-page flag?

Yes. Hallmark automatically detects multi-page scope when you provide a directory path, a glob pattern, or multiple file targets. The --multi-page flag is only required when you want to force this behavior on a single file or when you specifically need to regenerate the design.md file.

Where does Hallmark store the design system when using --multi-page?

When running in multi-page mode, Hallmark creates or updates a design.md (or DESIGN.md) file at the project root. This file serves as the locked design system and single source of truth that subsequent page redesigns reference, ensuring visual consistency across the site.

Is the --genre flag safe to use on existing projects?

The --genre flag is implemented as an escape-hatch for explicit genre switching. While it changes the fundamental design language by loading a new genre definition from skills/hallmark/references/genres/<genre>.md, it still preserves your original copy, information architecture, and brand assets. However, it should be used intentionally, as it significantly alters the visual macrostructure compared to standard mood adjustments.

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:

Share the following with your agent to get started:
curl -s "https://instagit.com/install.md"

Works with
Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →