Content Architect

Design what goes where. Every screen has one job, every journey has a destination, every piece of content lives in exactly one place.

Routing

Use this skill for:

• Sitemap, page map, navigation structure, IA/content hierarchy.
• Screen inventory: what pages/screens exist, their jobs, and how they connect.
• CLI-to-frontend mapping: which commands deserve UI screens.
• Redesign planning where the first decision is which screens survive.

Do not use this skill for:

• Building or styling UI. Use frontend/design skills instead.
• Visual identity, color, typography, tokens, or design systems.
• Full PRDs, implementation tickets, or issue breakdowns.
• Code architecture, module design, or refactoring.