Information architecture
Skill ulpi-io/plugin-marketplace/plugins/aj-geddes/skills/information-architecture
Organize and structure information for clarity and discoverability. Design navigation systems, hierarchies, and mental models that match user needs.From its SKILL.md
npx -y skills add ulpi-io/plugin-marketplace --skill information-architectureAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
2.4 KB, 499 tokens by cl100k_base, as published. Nobody here has run it
Information Architecture
Table of Contents
Overview
Information Architecture creates logical structures that help users find and understand information easily.
When to Use
- Website or app redesign
- Large information spaces (documentation, e-commerce)
- Navigation structure planning
- Taxonomy and categorization
- Search functionality design
- User journey mapping
Quick Start
Minimal working example:
IA Process:
1. Research & Discovery
- Interview users about mental models
- Card sorting sessions (open and closed)
- Analyze current usage patterns
- Competitive analysis
2. Structure Development
- Create organization scheme (hierarchical, faceted, etc.)
- Define categories and relationships
- Build taxonomy
- Plan navigation
3. Wireframing
- Sitemap creation
- Navigation structure
- Page templates
- User flows
4. Validation
- User testing with prototypes
- Tree testing (navigation only)
- Iterate based on feedback
// ... (see reference guides for full implementation)
Reference Guides
Detailed implementations in the references/ directory:
| Guide | Contents |
|---|---|
| Card Sorting & Taxonomy | Card Sorting & Taxonomy |
| Sitemap & Navigation Structure | Sitemap & Navigation Structure |
| Search & Discovery | Search & Discovery |
Best Practices
✅ DO
- Start with user research
- Conduct card sorting studies
- Use user mental models
- Keep hierarchy 3 levels deep max
- Use clear, simple labels
- Enable multiple ways to find content
- Test navigation with users
- Update based on usage data
- Document taxonomy
- Provide search functionality
❌ DON'T
- Impose organizational structure without research
- Use jargon or technical terms
- Make hierarchy too deep
- Bury important content
- Rely only on navigation (provide search)
- Change navigation frequently
- Create ambiguous labels
- Forget about edge cases
- Ignore accessibility
- Assume desktop-only navigation
What ships with it: 5 files
5.0 KB alongside SKILL.md, 2 of them executable
references/
scripts/
- scaffold-tests.shruns574 B
templates/
- test-template.jsruns541 B