Hallmark's Navigation Archetypes: How to Choose the Index‑First Pattern

The Index‑First archetype is Hallmark's navigation pattern that renders pages as pure link lists without hero images or narrative flow, designed for maximum scanability and rapid page discovery.

Hallmark (Nutlope/hallmark) treats page layout as a macrostructure system where predefined patterns govern content presentation. Among these, the Index‑First navigation archetype stands out as the definitive choice for building navigation hubs that prioritize link discovery over visual storytelling. This pattern is cataloged as item 13 in Hallmark's macrostructure reference list.

What Are Hallmark's Navigation Archetypes?

Hallmark defines navigation archetypes as macrostructures—top-level layout patterns that determine how content organizes on the page. According to the source code in skills/hallmark/references/macrostructures.md, the navigation archetype is formally named Index‑First and represents a specific approach to information architecture.

The Index‑First Macrostructure Definition

The 13-index-first.md file defines this archetype explicitly: "The page IS a list of links. No hero image, no narrative flow. Pure navigation as design." This macrostructure strips away decorative imagery and storytelling elements to create a flat hierarchy optimized for rapid traversal between peer pages.

When to Choose the Index‑First Navigation Archetype

Select the Index‑First pattern when your design brief emphasizes discovery over immersion. The following decision factors point specifically to this archetype:

Fast discoverability – When users need to scan many options instantly, the flat link list eliminates cognitive load by removing visual distractions.

Peer-level content – Pages with little hierarchical relationship benefit from equal visual weight, as the archetype treats every link as a primary destination rather than nesting content under narrative sections.

Navigation-focused briefs – Keywords like "site map," "catalog," or "navigation hub" in the brief signal this pattern according to the Hallmark source code.

Space constraints – Limited imagery real estate makes hero sections impractical; the Index‑First archetype conserves visual space by design.

Efficiency workflows – When the primary user goal is jumping to a target page quickly rather than consuming current-page content, pure navigation maximizes click‑through efficiency.

If the brief calls for immersive experiences or hero-driven narratives, choose alternative macrostructures like Marquee‑Hero instead.

How to Apply the Index‑First Pattern in Practice

Hallmark implements the Index‑First archetype through CLI flags and skill configuration files. The macrostructure is invoked using the identifier 13 across the codebase.

CLI Commands

Use the --macrostructure flag with the redesign verb to apply the Index‑First pattern:

# Redesign a site using the Index‑First navigation archetype

hallmark redesign <target> --macrostructure=13

# Audit an existing site to verify it matches the navigation archetype

hallmark audit <target> --expect-macrostructure=13

Skill Configuration

When building custom skills, pin the macrostructure in the SKILL.md header located at skills/hallmark/SKILL.md:

---
macrostructure: 13   # Index‑First (pure navigation)

---

Summary

• Hallmark's navigation archetype is the Index‑First macrostructure (item 13), defined in 13-index-first.md as pure link lists without hero images or narrative flow.
• Choose this pattern when the brief emphasizes navigation, catalogs, or site maps, or when users need rapid page discovery across peer-level content.
• Reference the canonical definition in skills/hallmark/references/macrostructures/13-index-first.md and the catalog in skills/hallmark/references/macrostructures.md.
• Apply via hallmark redesign --macrostructure=13 or by setting macrostructure: 13 in SKILL.md.

Frequently Asked Questions

What is Hallmark's Index‑First navigation archetype?

The Index‑First archetype is a macrostructure defined in skills/hallmark/references/macrostructures/13-index-first.md that treats the entire page as a list of links. It eliminates hero images and narrative flow to create a pure navigation hub optimized for scanability, where the page itself functions as a directory rather than a destination.

When should I use the Index‑First pattern versus a hero‑driven layout?

Use Index‑First when the brief contains terms like "navigation," "catalog," or "site map," or when content consists of many peer pages requiring equal visibility. Choose hero‑driven macrostructures like Marquee‑Hero when the goal is immersive storytelling, brand messaging, or showcasing specific featured content above the fold.

How do I audit an existing site for the Index‑First archetype?

Run hallmark audit <target> --expect-macrostructure=13 to verify whether the current page structure matches the Index‑First pattern. This command checks the target against the canonical definition stored in the Hallmark skill reference files, reporting whether the layout conforms to the pure navigation specification.

Can I combine the Index‑First archetype with other macrostructures?

No, macrostructures are mutually exclusive top‑level patterns defined in skills/hallmark/references/macrostructures.md. You must select one macrostructure per page redesign operation. However, individual components within the Index‑First layout may use different micro‑patterns for link styling or grouping, provided the overall page remains a flat navigation hub.

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