organize

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

Updated May 5, 2026
One-click install
npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill organize-thegeekosaurus
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: organize
Source: https://github.com/TheGeekosaurus/blogging-platform-2/tree/main/.agents/skills/organize
Command: npx skills add https://github.com/TheGeekosaurus/blogging-platform-2 --skill organize-thegeekosaurus

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Users get lost when product information is structured around org charts instead of mental models, causing findability failures, support tickets, and abandoned tasks. 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: Select among hierarchical, hub-and-spoke, flat, faceted, dashboard, and sequential patterns with trade-off analysis for the specific product. - Taxonomy & Labeling Systems: Build MECE categories, polyhierarchy rules, and user-language labels validated through card sorts, tree tests, and first-click testing. - Search, Browse & Wayfinding: Design autocomplete, faceted filtering, zero-results recovery, breadcrumbs, and orientation cues as a coherent system. - Use Case: A SaaS team whose users report they "can't find settings" invokes this Skill to audit the IA, run a tree test, and produce a restructured site map with a tested labeling guide and an HTML visualization. ## Quick Start Ask the AI to design the information architecture and navigation structure for your product, choosing HTML, Figma, or pencil.dev for the site map 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 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 attribute-rich catalogs. Validate the structure with tree testing 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?▼

Diagnose whether the problem is structural, labeling, or wayfinding. Check search logs for high-volume queries that should be browsable, run first-click tests on top-level categories, and audit for overlapping or jargon-heavy labels.

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. It fails when facets are not 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. Users do not know which team owns billing versus subscription; they think of both as their account. Organize around user mental models validated by research instead.