--- name: "content-structure-information-architecture" description: "Plan website content structure and information architecture. Use for page maps, nav, section sequencing, user questions, service pages, product pages, portfolios, case studies, blogs, docs, ecommerce, and any site where content order and naming affect clarity and perceived quality." ---

# Content Structure Information Architecture

## Overview

Make the page understandable before making it pretty. Good visual design cannot rescue a confusing information path.

## Website Nonnegotiables

- Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands. - Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix. - Use existing project conventions first. Explain major new dependencies before adding them. - Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes. - Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again. - Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly. - Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

## Workflow

1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability. 2. Inspect the project before editing when code exists. 3. Apply this skill's specific rules from `references/content-structure-information-architecture-guide.md`. 4. Explain planned files before major changes unless the user has clearly said to proceed. 5. Build, inspect, polish, and verify before final delivery.

## Reference

Read `references/content-structure-information-architecture-guide.md` when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

--- name: "content-structure-information-architecture" description: "Plan website content structure and information architecture. Use for page maps, nav, section sequencing, user questions, service pages, product pages, portfolios, case studies, blogs, docs, ecommerce, and any site where content order and naming affect clarity and perceived quality." ---

# Content Structure Information Architecture

## Overview

Make the page understandable before making it pretty. Good visual design cannot rescue a confusing information path.

## Website Nonnegotiables

- Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands. - Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix. - Use existing project conventions first. Explain major new dependencies before adding them. - Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes. - Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again. - Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly. - Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

## Workflow

1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability. 2. Inspect the project before editing when code exists. 3. Apply this skill's specific rules from `references/content-structure-information-architecture-guide.md`. 4. Explain planned files before major changes unless the user has clearly said to proceed. 5. Build, inspect, polish, and verify before final delivery.

## Reference

Read `references/content-structure-information-architecture-guide.md` when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

--- name: "content-structure-information-architecture" description: "Plan website content structure and information architecture. Use for page maps, nav, section sequencing, user questions, service pages, product pages, portfolios, case studies, blogs, docs, ecommerce, and any site where content order and naming affect clarity and perceived quality." ---

# Content Structure Information Architecture

## Overview

Make the page understandable before making it pretty. Good visual design cannot rescue a confusing information path.

## Website Nonnegotiables

- Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands. - Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix. - Use existing project conventions first. Explain major new dependencies before adding them. - Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes. - Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again. - Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly. - Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

## Workflow

1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability. 2. Inspect the project before editing when code exists. 3. Apply this skill's specific rules from `references/content-structure-information-architecture-guide.md`. 4. Explain planned files before major changes unless the user has clearly said to proceed. 5. Build, inspect, polish, and verify before final delivery.

## Reference

Read `references/content-structure-information-architecture-guide.md` when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.

--- name: "content-structure-information-architecture" description: "Plan website content structure and information architecture. Use for page maps, nav, section sequencing, user questions, service pages, product pages, portfolios, case studies, blogs, docs, ecommerce, and any site where content order and naming affect clarity and perceived quality." ---

# Content Structure Information Architecture

## Overview

Make the page understandable before making it pretty. Good visual design cannot rescue a confusing information path.

## Website Nonnegotiables

- Inspect before coding: structure, framework, homepage or main entry file, styling system, JavaScript or interaction system, assets, and build commands. - Before major changes, explain planned files and wait unless the user clearly says proceed, build, create, implement, or fix. - Use existing project conventions first. Explain major new dependencies before adding them. - Never ship generic visual work: no default card grids, placeholder copy, weak type, random gradients, stock-like media, or template heroes. - Build version 1, inspect the rendered result, improve spacing, type, hierarchy, motion, media, hover states, and responsiveness, then run checks again. - Run available lint, build, and test commands when possible. Report commands, changed files, and any untested areas honestly. - Check desktop and mobile. Respect accessibility, semantic markup, focus states, and reduced-motion preferences.

## Workflow

1. Read the user's brief and identify the website category, audience, content reality, visual references, and asset availability. 2. Inspect the project before editing when code exists. 3. Apply this skill's specific rules from `references/content-structure-information-architecture-guide.md`. 4. Explain planned files before major changes unless the user has clearly said to proceed. 5. Build, inspect, polish, and verify before final delivery.

## Reference

Read `references/content-structure-information-architecture-guide.md` when this skill triggers for a concrete website build, redesign, visual review, or implementation plan.