How the hallmark redesign Verb Protects Existing Implementation Boundaries

The hallmark redesign verb enforces non-destructive editing rules, scope-aware processing, and design system anchoring to prevent accidental deletion of production code during automated page redesigns.

The hallmark redesign verb in the Nutlope/hallmark repository provides an automated approach to modernizing web interfaces while strictly safeguarding existing implementation boundaries. Unlike destructive scaffolding tools, this verb operates within a protective framework that preserves route hierarchies, component folders, and production assets unless explicitly authorized otherwise. Understanding how the hallmark redesign verb handles boundary protection helps teams safely iterate on visual layers without risking codebase integrity.

Core Protection Principles

The verb implements three defensive mechanisms that collectively prevent accidental breaches of implementation boundaries.

Non-Destructive Implementation Rules

By default, the hallmark redesign verb never removes route files, component folders, or page trees. It performs only in-place edits or adds new components that wire through existing routes. Deletions require explicit user confirmation preceded by a clear, file-level plan. This rule ensures that running the verb against production code cannot accidentally dismantle the application structure.

Intelligent Scope Detection

Before modifying any files, the verb determines whether the request targets a single page or a multi-page redesign. It checks for directory targets, glob patterns, multiple file names, or phrasing like "the whole site". This decision dictates the subsequent flow, preventing large-scale changes from accidentally applying to a single page and vice versa.

Design System Anchoring

For multi-page redesigns, the verb generates a design.md file at the project root that serves as the single source of truth. All subsequent page-level redesigns read this file, ensuring consistent macro-structure, theme, typography, spacing, motion, and CTA voice across the site. Individual pages may only vary within the allowances defined in this anchor document.

The hallmark redesign Workflow

The verb executes a four-step process that enforces boundary protection at each stage.

Detecting Scope: Single vs. Multi-Page

The initial phase analyzes the target parameter to select the appropriate processing path.

// Example: Detecting multi‑page vs single‑page redesign
if (isDirectory(target) || isGlob(target) || multipleFilesListed(target)) {
  // Multi‑page redesign – generate design.md first
  createDesignFile(projectRoot);
} else {
  // Single‑page redesign – edit the page in place
  editPageInPlace(targetFile);
}

Multi-Page Flow and design.md Generation

When scope detection indicates a multi-page operation, the verb walks the target directory to catalogue each page and existing design asset. It then generates a comprehensive design.md file that codifies the design system.

# design.md (generated by the verb)

## Theme

- `--color-paper`   oklch(<L> <C> <H>)
- `--color-ink`     oklch(<L> <C> <H>)
- `--color-accent`  oklch(<L> <C> <H>)

## Typography

- Display: <face>, weight <N>
- Body:    <face>, weight <N>
- Mono:    <face>, weight <N>

Subsequent page redesigns reference this file, preventing divergent visual language across the implementation.

Single-Page In-Place Editing

For single-page targets, the verb directly edits the specified page or component. It modifies only the necessary markup and CSS while strictly preserving the existing route hierarchy and adjacent files. This targeted approach ensures that surrounding implementation boundaries remain intact.

Confirmation Gates for Destructive Operations

If a redesign would require removing multiple components or collapsing the application structure, the verb halts execution and requests explicit user approval.

// Example: Guarding against accidental deletions
if (requiresDeletionOfMultipleComponents(changeSet)) {
  // Pause and ask user for confirmation before proceeding
  await requestUserConfirmation(changeSet);
} else {
  applyChanges(changeSet);
}

This guard prevents automated processes from crossing destructive implementation boundaries without human oversight.

Source Code Implementation

The hallmark redesign logic is distributed across specific files in the Nutlope/hallmark repository. The complete workflow definition, including non-destructive rules and scope detection, resides in skills/hallmark/references/verbs/redesign.md. The generated design.md file appears at the project root during multi-page operations and consumes token definitions from site/css/tokens.css. Consumer logic that respects these design systems exists in site/js/main.js. Together, these components ensure that the verb modernizes visual layers without breaching existing implementation boundaries unless explicitly authorized.

Summary

• The hallmark redesign verb enforces a non-destructive implementation rule that prevents automatic deletion of route files and component folders.
• Scope detection differentiates between single-page and multi-page targets to prevent accidental wide-scale changes.
• Multi-page operations generate a root-level design.md file that anchors the design system and ensures consistency across all pages.
• Explicit confirmation gates block destructive changes unless the user approves a clear file-level plan.
• Source definitions in redesign.md and supporting files in site/js/main.js and site/css/tokens.css implement these boundary protections.

Frequently Asked Questions

Can hallmark redesign delete my existing components automatically?

No, the verb follows a strict non-destructive implementation rule that prevents automatic removal of route files, component folders, or page trees. According to the source code in skills/hallmark/references/verbs/redesign.md, deletions only occur after explicit user confirmation and a clear, file-level plan. The default behavior modifies files in place or adds new components wired through existing routes.

How does the verb decide between single-page and multi-page redesign modes?

The verb analyzes the target path and user intent to detect scope. It checks for directory targets, glob patterns, multiple file names, or phrases like "the whole site". As implemented in the logic, if isDirectory(target), isGlob(target), or multipleFilesListed(target) return true, the verb triggers multi-page mode. This prevents large-scale changes from accidentally applying to individual pages.

What is the purpose of the design.md file in hallmark redesign?

The design.md file acts as a central design system anchor generated at the project root during multi-page redesigns. It codifies theme tokens, typography, spacing, motion guidelines, and CTA voice that all subsequent page redesigns must reference. This ensures visual consistency across the site while allowing individual pages to vary only within the allowances defined in the anchor document.

Where is the redesign verb defined in the source code?

The verb's workflow, non-destructive rules, scope detection logic, and confirmation gates are defined in skills/hallmark/references/verbs/redesign.md. Supporting utilities and design token consumers reside in site/js/main.js and site/css/tokens.css, which interact with the generated design.md file during the redesign process.

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