organize

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

Updated Aug 26, 2026
One-click install
npx skills add https://github.com/danieliudi/trackforge-os --skill organize-danieliudi
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: organize
Source: https://github.com/danieliudi/trackforge-os/tree/main/.cursor/skills/organize
Command: npx skills add https://github.com/danieliudi/trackforge-os --skill organize-danieliudi

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users get lost in products when information is structured around internal org charts instead of user mental models. This Skill designs the underlying organization of a product — categories, hierarchies, labels, and navigation — 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, and sequential patterns with trade-off analysis specific to your product. - Taxonomy & Labeling Systems: Builds MECE-informed classification schemes, handles polyhierarchy, and tests labels with 5-second tests, cloze tests, and A/B variants. - IA Research Methods: Plans card sorts, tree tests, first-click tests, and search log analysis to validate structure with real users instead of assumptions. - Visualization Output: Produces site map diagrams as self-contained HTML, Figma frames via MCP, or pencil.dev documents. - Use Case: A SaaS team whose support tickets show users "can't find billing settings" invokes this Skill to audit the IA, run a tree test, and ship a restructured navigation with validated labels. ## Quick Start Ask the assistant to use the organize skill to design a site map and navigation structure for your product, and say whether you want the diagram as HTML, Figma, or markdown only.

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 website or app?

Start by choosing a navigation pattern that fits your content: hierarchical for clear parent-child relationships, hub-and-spoke for task-focused apps, faceted for large filterable catalogs. Then validate the structure with tree tests before implementation.

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 find items in a text-only structure, measuring success rate and directness.

How do I fix users reporting they can't find things in my product?

Diagnose whether the problem is structural or labeling-based using search log analysis and first-click testing. High search volume for browsable items indicates IA gaps; wrong first clicks indicate labels that don't communicate their contents.

When should I use faceted navigation instead of hierarchical?

Use faceted navigation for large, attribute-rich collections like e-commerce catalogs where items have multiple independent properties users filter by. Avoid it when facets aren't truly independent or the dataset is too small to benefit from filtering.

What are the limitations of organizing navigation by team structure?

Org-chart-based IA optimizes for internal ownership, not user findability, and is wrong more often than right. Users think in terms of their tasks, so categories should reflect user mental models discovered through card sorts, not departmental boundaries.