organize

Designs information architecture, navigation patterns, taxonomies, and labeling systems for digital products.

Updated Jul 21, 2026
One-click install
npx skills add https://github.com/rakedzior/rootine --skill organize-rakedzior
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize
Source: https://github.com/rakedzior/rootine/tree/main/agent/skills/organize
Command: npx skills add https://github.com/rakedzior/rootine --skill organize-rakedzior

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users get lost when product information is poorly structured: they cannot find features, labels confuse them, and navigation mirrors internal org charts instead of user mental models. This Skill structures information so people can find what they need, understand where they are, and navigate confidently. ## Core Features & Use Cases - Navigation Pattern Design: Selects among hierarchical, hub-and-spoke, flat, faceted, dashboard, sequential, and global-plus-local patterns with explicit trade-off analysis for the specific product. - Taxonomy and Labeling Systems: Builds MECE categories, handles polyhierarchy, plans for scale, and creates labels tested via 5-second tests, cloze tests, and A/B variants. - Search, Browse, and Wayfinding: Designs autocomplete, filters, zero-results recovery, breadcrumbs, and orientation cues answering where am I, where can I go, and am I there. - IA Research Methods: Plans card sorts, tree tests, first-click tests, and search log analysis to validate structure with real users. - Use Case: A product team whose users report they cannot find settings asks how to reorganize the app; the Skill produces a site map, navigation specification, labeling guide, and a tree-test plan, optionally rendered as a self-contained HTML diagram, Figma file, or pencil.dev document. ## Quick Start Ask the assistant to use the organize skill to design a navigation structure and site map for your product, and say whether you want an HTML, Figma, or pencil visualization.

Frequently Asked Questions about organize

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

FAQPage Schema
How do I design a navigation structure for a product?

Start by choosing a navigation pattern that fits your content and tasks: hierarchical for clear parent-child content, hub-and-spoke for distinct task modes, faceted for large filterable catalogs. Then validate top-level labels with first-click tests before committing.

How do I test whether users can find things in my site structure?

Run a tree test with 50 or more participants on a text-only version of your hierarchy, measuring success rate and directness. Combine it with open card sorts to discover user mental models and first-click tests on the implemented navigation.

What is the difference between card sorting and tree testing?

Card sorting reveals how users naturally group and name content, informing taxonomy design. Tree testing validates an existing hierarchy by asking users to locate items, isolating structural quality from visual design.

When should I use faceted navigation instead of a hierarchy?

Use faceted navigation for large, attribute-rich collections like catalogs or directories where items have multiple independent properties users filter by. It fails when facets are not truly independent or the dataset is too small to benefit from filtering.

Why do users say they cannot find things even with a clear menu?

Common causes are labels using internal jargon instead of user vocabulary, overlapping categories, more than seven to nine top-level items, and structures mirroring the org chart rather than user mental models. Test labels with 5-second and cloze tests.

Can this skill output a sitemap diagram in Figma or HTML?

Yes. It asks up front which format you want: a self-contained HTML file with embedded CSS and dark mode, a Figma file built via MCP, or a pencil.dev document. If you state a preference in the request, it skips the question.