What Is the Hallmark Redesign Verb? A Deep Dive into the Structural-Reset Operation

The Hallmark redesign verb is a structural-reset command that rebuilds a page or application's visual layout and interaction layer while preserving its existing copy, information architecture, and brand assets. In this guide, you'll learn how the hallmark redesign verb works, when to use single-page versus multi-page mode, and how it handles design systems, moods, and safety checks according to the Nutlope/hallmark source code.

---

What Is the Hallmark Redesign Verb?

The hallmark redesign verb serves as the structural-reset operation in the Hallmark toolchain. According to [skills/hallmark/references/verbs/redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md), it takes existing content—including copy, information architecture (IA), and brand assets—and reconstructs the visual and interactive layers from scratch. The operation stays within current implementation boundaries unless the user explicitly authorizes a full rebuild.

This verb follows a disciplined philosophy: preserve the user's language and IA, rebuild the visual fingerprint.

---

How the Redesign Verb Determines Scope

Before executing any changes, Hallmark performs scope determination. The verb first decides whether the request targets a single page or the entire app (multi-page redesign). This decision flows from lines 17-27 in [redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md) and drives all subsequent behavior.

Single-Page Redesign

For single-page targets, Hallmark:

• Rewrites the target file (e.g., hero.tsx)
• Generates a new macro-structure: component hierarchy, layout rhythm, and CSS tokens
• Preserves the page's existing copy and IA
• Produces fresh index.html and style.css files

As documented in [site/_tests/verbs/redesign/README.md](https://github.com/Nutlope/hallmark/blob/main/site/_tests/verbs/redesign/README.md) (line 8), the output consists of these two files with updated layout and interaction patterns.

Multi-Page Redesign

For multi-page targets, Hallmark:

• Creates or updates a design.md file at the project root
• Captures the new design system for all pages
• Writes a single log entry to .hallmark/log.json with "scope": "app"

See [redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md) lines 47-52 and 218 for the full specification.

---

Design System Integration and Lock Files

The hallmark redesign verb respects existing design constraints through design system detection.

If a project-level design.md (or DESIGN.md) exists at the repository root, Hallmark treats it as a locked design system for the entire application. The redesign then operates within that system rather than creating a fresh, divergent structure. This behavior is defined in [skills/hallmark/SKILL.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/SKILL.md) at line 153.

This lock file mechanism prevents accidental fragmentation of visual identity across pages and ensures consistency in multi-developer environments.

---

Mood and Genre Customization

The hallmark redesign verb supports optional stylistic overrides through flags and genre files.

The --mood Flag

Use --mood <name> to map a redesign to specific tone definitions:

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

This flag references typography and structure definitions in the Hallmark skill references, applying predetermined aesthetic parameters without manual token configuration.

Genre Transformations

For structural genre changes, Hallmark loads rule overlays from the genres/ folder. For example, transforming "this editorial page into a modern SaaS hero" triggers:

1. Genre file loading from genres/
2. Rule overlay application per lines 258-259 in [redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md)
3. Output generation with the new genre's structural patterns

---

Safety Checks and User Confirmation

The hallmark redesign verb implements multiple safety mechanisms to prevent destructive changes.

Structural Impact Detection

If a redesign would require:

• Removing many components
• Collapsing routes
• Drastically altering the application's structure

Hallmark pauses execution and requests explicit user confirmation. This check appears in [redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md) lines 11-12.

Post-Operation Documentation

After completion, Hallmark appends a diagnostic note with:

• Explanation of changes made
• A flag reading studied: no · context: redesign

Downstream verbs like audit can read this flag to verify that the new macro-structure was intentional. See [site/_tests/verbs/redesign/notes.md](https://github.com/Nutlope/hallmark/blob/main/site/_tests/verbs/redesign/notes.md) lines 62-66 for the note format specification.

---

Practical Usage Examples

Basic Single-Page Redesign

# Redesign a single component/page (default behavior)

hallmark redesign ./src/pages/hero.tsx

Result: Fresh index.html and style.css with preserved copy but new layout and component hierarchy.

Mood-Directed Redesign

# Apply a specific aesthetic mood

hallmark redesign ./src/pages/about.tsx --mood minimal

Multi-Page System Redesign

# Redesign entire application scope

hallmark redesign --multi-page

Result: Creates/updates design.md at project root and logs the operation with "scope": "app" in .hallmark/log.json.

---

Key Source Files and Architecture

File Path	Purpose
skills/hallmark/references/verbs/redesign.md	Complete verb specification: flows, moods, genres, safety checks
skills/hallmark/SKILL.md	Skill overview and CLI signature for hallmark redesign
site/_tests/verbs/redesign/notes.md	Example output notes describing changes
site/_tests/verbs/redesign/output.html	Sample generated HTML from redesign execution
design.md (generated)	Project-level design system lock file
.hallmark/log.json	Operation log with scope and metadata

---

Summary

• The Hallmark redesign verb performs structural resets while preserving copy and information architecture.
• Scope determination (single-page vs. multi-page) drives execution flow and output artifacts per [redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md).
• Design system lock files (design.md) constrain redesigns to existing visual systems when present.
• --mood flags and genre files enable stylistic customization without manual configuration.
• Safety checks pause for user confirmation on high-impact structural changes and document operations for downstream audit verbs.

---

Frequently Asked Questions

What happens to my original code when I run hallmark redesign?

The verb preserves your copy, information architecture, and brand assets. It regenerates the visual and interaction layers—component hierarchy, layout rhythm, and CSS tokens—while keeping your content intact. For single-page redesigns, you receive fresh index.html and style.css files. Your original source file is not overwritten unless explicitly configured.

Can I prevent Hallmark from creating a new design system?

Yes. Place a design.md or DESIGN.md file at your repository root. Hallmark treats this as a locked design system and constrains the redesign within those boundaries, as specified in [SKILL.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/SKILL.md) line 153.

What's the difference between --mood and genre files?

--mood applies predefined aesthetic parameters (typography, color treatment) without changing page structure. Genre files apply comprehensive structural rule overlays—transforming an editorial layout into a SaaS hero, for example. Moods are quick stylistic shifts; genres are architectural transformations.

How does Hallmark protect against accidental breaking changes?

The verb implements structural impact detection. If removing components, collapsing routes, or drastic alterations are required, Hallmark pauses for explicit confirmation ([redesign.md](https://github.com/Nutlope/hallmark/blob/main/skills/hallmark/references/verbs/redesign.md) lines 11-12). Post-completion, it writes a contextual flag (studied: no · context: redesign) so audit verbs can verify the redesign was intentional.

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