Purpose-Led Site Layouts

What it does

Plans page structure around the site's dominant task, audience decision stage and conversion goal.

When to use it

Use for sitemaps, homepages, landing pages, or deciding the most defensible section order for a type of site.

Problems it prevents

Stops every page defaulting to the same hero-then-three-cards-then-testimonials template regardless of purpose.

Typical workflow

1. Identify the dominant task and decision stage
2. Choose section order from purpose, not convention
3. Draft the deliverable layout
4. Hand off with the reasoning attached

Example output

A page structure whose section order is justified by what the visitor actually needs to decide, in that order.

What's included

1. 01
   The complete prompt

   The full manual as a ready-to-save SKILL.md file, matched exactly to what ships in the T7 library.

2. 02
   Install walkthrough

   Personal (~/.claude/skills/) and project (.claude/skills/) folder instructions, whichever fits how you work.

3. 03
   Use notes

   How Claude invokes it, what a good result looks like, and what to check before you trust the output.

Works well with

• SystemProject Planner

  Turns a loose client brief into routes, features, content needs, dependencies, risks and acceptance checks.

• SystemPremium Content Hierarchy

  Writes message architecture and copy hierarchy from a real offer, audience, evidence and objections, not filler.

• SystemUI/UX Designer

  Designs interfaces around real user journeys (hierarchy, responsive behaviour, interaction states) instead of visual filler.