structure-information-architecture

Designs and validates information architecture using card sorts and tree tests.

1|Updated Jul 13, 2026
One-click install
npx skills add https://github.com/dineshrevunuru/SuperSkills --skill structure-information-architecture-dineshrevunuru
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: structure-information-architecture
Source: https://github.com/dineshrevunuru/SuperSkills/tree/main/structure-information-architecture
Command: npx skills add https://github.com/dineshrevunuru/SuperSkills --skill structure-information-architecture-dineshrevunuru

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users complain they "can't find" content because navigation structures reflect org charts and internal jargon instead of user mental models. This Skill designs information architecture — organization schemes, hierarchy, labels, polyhierarchy — and proves findability with card sorts and tree tests as one generate-then-evaluate loop, so structure is never shipped untested. ## Core Features & Use Cases - IA Design: Build content inventories, choose organization schemes (topic, task, audience, exact), balance depth vs. breadth, apply information-scent label linting, and handle polyhierarchy with canonical parents. - Card Sort Analysis: Plan open/closed/hybrid sorts, avoid the terminology-match trap, and read similarity matrices and dendrograms to derive categories and user-language labels. - Tree Test Evaluation: Build text-only tree tests with goal-phrased tasks, measure success/directness/first-click against thresholds, and diagnose failures with a per-pattern fix table plus a retest rule. - Use Case: A salon services site has 40 content items and users can't find re-fitting services. Run an open card sort to discover three mental-model clusters, draft a labeled tree, tree test it, find task 4 failing at 61% success due to a missing cross-link, add the alias, retest to 94% success, and ship the validated sitemap. ## Quick Start Use the structure-information-architecture skill to organize our product's content into a sitemap and validate it with a card sort and tree test.

Frequently Asked Questions about structure-information-architecture

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

FAQPage Schema
How do I run a card sort to design a sitemap?

Build an inventory of 40-60 content items as cards with user-facing wording, then run an open card sort where participants group cards and name the groups. Read the similarity matrix and dendrogram at a 60-70% agreement cut to derive candidate categories and labels.

What is the difference between card sorting and tree testing?

Card sorting is generative — it discovers users' mental models and category names. Tree testing is evaluative — it measures whether a drafted hierarchy lets users find items. Run the sort first to generate the structure, then tree test it before shipping.

How many participants do I need for a card sort or tree test?

Use 15 or more unmoderated participants for quantitative results; around 50 gives stable per-task tree-test percentages. Under 15 participants, treat findings as qualitative signal only and never report percentages.

Why do tree test tasks fail even with a good hierarchy?

Failures usually come from label problems: vague umbrella labels, overlapping sibling labels, or tasks that accidentally quote the label being tested. Diagnose per task using success, directness, and first-click patterns, then fix labels and retest the failed tasks.

When should an item appear in two navigation categories?

Allow polyhierarchy only when sort or tree data shows users genuinely split between two locations and both are high-traffic paths. Designate one canonical parent owning the URL, cross-link from the other, and keep it rare — over 15% of items with multiple parents means the top-level scheme is wrong.

When should I use a usability test instead of a tree test?

Tree tests validate text-only structure and labels without visual design. When the question is whether users can complete whole tasks on a live, rendered site, hand off to a full usability test instead.