layout-and-information-architecture

Organize screen or flow content into a ranked information architecture and layout reasoning plan.

15|5|Updated May 4, 2026
One-click install
npx skills add https://github.com/eugenelim/agent-ready-repo --skill layout-and-information-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: layout-and-information-architecture
Source: https://github.com/eugenelim/agent-ready-repo/tree/main/packs/design-craft/.apm/skills/layout-and-information-architecture
Command: npx skills add https://github.com/eugenelim/agent-ready-repo --skill layout-and-information-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill helps you turn a cluttered screen or multi-step flow into a clear, user-oriented information architecture. It explains what belongs first, what should be secondary, and how people stay oriented while moving through the experience.

Core Features & Use Cases

  • Content Hierarchy: Identifies the primary, secondary, and tertiary elements so the surface has a clear focal point.
  • Reading Flow Planning: Chooses an appropriate scanning pattern and arranges content to match how users naturally read.
  • Progressive Disclosure and Wayfinding: Stages complexity, organizes navigation, and clarifies where users are, where they can go, and how they get back.
  • Use Case: Use this Skill when a dashboard, signup flow, settings page, or landing page feels crowded and needs a structured layout rationale instead of visual mockups.

Quick Start

Ask the layout-and-information-architecture skill to analyze your screen or flow and produce a ranked content structure with reading flow, disclosure, navigation, and wayfinding guidance.

Frequently Asked Questions about layout-and-information-architecture

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I organize a cluttered dashboard layout into a clear information architecture?▼

To organize a cluttered dashboard layout, establish a content hierarchy that ranks elements as primary, secondary, or tertiary. This creates a clear focal point and structured reading order for users navigating complex screens.

What is the best way to structure progressive disclosure for a multi-step signup flow?▼

Progressive disclosure for a multi-step flow stages complexity by revealing secondary information only when needed. This organizes navigation and clarifies wayfinding, showing users where they are and how to return.

How do I choose between F-pattern and Z-pattern scanning for a landing page layout?▼

Choosing between F-pattern and Z-pattern scanning depends on your content density and hierarchy. The layout ranks screen elements, selects the matching visual pattern, and arranges content to guide natural reading flow.

Can I use information architecture planning for empty, loading, and error states?▼

Information architecture planning explicitly accounts for empty, loading, and error states. Structuring these partial states ensures your navigation hierarchy and wayfinding remain clear during abnormal screen conditions.

Does this layout reasoning approach provide visual mockups or styling code?▼

This layout reasoning approach produces concept-only deliverables and explicitly avoids markup or styling code. It focuses entirely on structured information architecture, reading flow, and navigation hierarchy planning.

When should I use wayfinding and navigation structure planning for a settings page?▼

Wayfinding and navigation structure planning should be used when a settings page feels crowded and lacks orientation. It clarifies where users are, where they can go, and how to get back without visual mockups.