organize

Name: organize
Author: ghaida

548installs8forks

How to install organize?

ghaida/intent/organize

$npx -y skills add ghaida/intent --skill organize

Installs into the current project.

Summary

Structure information so people can find what they need, understand where they are, and navigate confidently. Covers navigation pattern design, taxonomy, labeling systems, search and browse strategy, wayfinding, and IA research methods. Trigger when designing navigation structure

Files · 1

View on GitHub

SKILL.md

1	# Organize
2
3	## Overview
4
5	Information architecture is the structural design of shared information environments. It determines whether users can find what they need, understand where they are, and navigate confidently. Good IA is invisible — users just "get it." Bad IA makes everything harder: more support tickets, more bounce, more confusion, more time wasted.
6
7	IA is not navigation design (that's one output of IA). It's not content strategy (that's what fills the structure). It's not visual design (that's how the structure looks). IA is the underlying organization — the categories, hierarchies, relationships, and labels that make a product's information findable and understandable.
8
9	Trigger this skill when users ask about:
10	- Designing or restructuring navigation (top-level, secondary, contextual)
11	- Organizing content into categories, sections, or taxonomies
12	- Site maps, content inventories, or structural audits
13	- Labeling and naming conventions for navigation, categories, or features
14	- Search strategy, filtering, or browse experiences
15	- Users reporting they "can't find things" or feel lost
16	- Card sorting, tree testing, or other IA research
17	- "How should we organize this?" or "Where should this live?"
18	- Merging or restructuring product areas after growth or acquisition
19
20	## Skill family
21
22	You work alongside complementary skills that handle interconnected concerns:
23
24	- `/strategize` — Their audience definition and solution fit inform your IA decisions. Who are you organizing for, and how do they think? Their five foundational questions tell you whether the product's scope is stable enough to build a lasting structure, or likely to shift.
25	- `/investigate` — Card sorts, tree tests, and user interviews reveal how users actually categorize and find information. Without their research, your IA is based on internal assumptions about how people think — and those assumptions are almost always wrong.
26	- `/journey` — Your IA provides the structure their flows navigate through. They design the sequence of steps; you design the space those steps move through. When a flow keeps hitting dead ends, the problem is often structural, not sequential.
27	- `/wireframe` — Places your structure on actual screens. You decide the taxonomy, navigation model, and labels; they decide where those structures sit on each screen and how prominent they are. If users can't find things, that's yours; if the structure is sound but the screen is illegible, that's theirs.
28	- `/articulate` — Labels are where IA and content strategy meet. Clarity of naming is critical — a perfectly structured taxonomy with unclear labels fails just as badly as a flat dump of clearly named items. Collaborate closely on naming decisions.
29	- `/blueprint` — System architecture constrains and enables IA possibilities. The data model, API structure, and content management system determine what organizational structures are technically feasible. A beautiful taxonomy that the CMS can't represent is useless.
30	- `/evaluate` — Tests whether users can actually find things in your structure. Their heuristic evaluation catches IA problems that tree tests miss — inconsistent patterns, misleading groupings, orphaned content.
31	- `/localize` — IA decisions that work in one language or culture may fail in another. Category boundaries, label meanings, and navigation conventions vary across markets.
32	- `/philosopher` — A cross-cutting cognitive mode for when categories feel natural but users keep getting lost. Enter when: the structure mirrors the org chart instead of user mental models, inherited IA assumptions need questioning, or you suspect the categorization scheme itself is the problem. The philosopher helps you ask whether the organizing principle is right, not just whether the organization is tidy.
33
34	Collaborate explicitly with each when their domain matters. Call out what you're not deciding.
35
36	## Visualization
37
38	When the user invokes `/organize`, decide whether the deliverable should
39	include a site map / IA diagram, and if so, in what format. Ask the user
40	up front — before producing the markdown deliverable.
41
42	### Ask first
43
44	Open the response with this question, with HTML as t

People who liked this also viewed

6 picks

Type

organize

548installs8forks

View on GitHub

How to install organize?

ghaida/intent/organize

$npx -y skills add ghaida/intent --skill organize

Installs into the current project.

Summary

Files · 1

View on GitHub

SKILL.md

1	# Organize
2
3	## Overview
4
5	Information architecture is the structural design of shared information environments. It determines whether users can find what they need, understand where they are, and navigate confidently. Good IA is invisible — users just "get it." Bad IA makes everything harder: more support tickets, more bounce, more confusion, more time wasted.
6
7	IA is not navigation design (that's one output of IA). It's not content strategy (that's what fills the structure). It's not visual design (that's how the structure looks). IA is the underlying organization — the categories, hierarchies, relationships, and labels that make a product's information findable and understandable.
8
9	Trigger this skill when users ask about:
10	- Designing or restructuring navigation (top-level, secondary, contextual)
11	- Organizing content into categories, sections, or taxonomies
12	- Site maps, content inventories, or structural audits
13	- Labeling and naming conventions for navigation, categories, or features
14	- Search strategy, filtering, or browse experiences
15	- Users reporting they "can't find things" or feel lost
16	- Card sorting, tree testing, or other IA research
17	- "How should we organize this?" or "Where should this live?"
18	- Merging or restructuring product areas after growth or acquisition
19
20	## Skill family
21
22	You work alongside complementary skills that handle interconnected concerns:
23
24	- `/strategize` — Their audience definition and solution fit inform your IA decisions. Who are you organizing for, and how do they think? Their five foundational questions tell you whether the product's scope is stable enough to build a lasting structure, or likely to shift.
25	- `/investigate` — Card sorts, tree tests, and user interviews reveal how users actually categorize and find information. Without their research, your IA is based on internal assumptions about how people think — and those assumptions are almost always wrong.
26	- `/journey` — Your IA provides the structure their flows navigate through. They design the sequence of steps; you design the space those steps move through. When a flow keeps hitting dead ends, the problem is often structural, not sequential.
27	- `/wireframe` — Places your structure on actual screens. You decide the taxonomy, navigation model, and labels; they decide where those structures sit on each screen and how prominent they are. If users can't find things, that's yours; if the structure is sound but the screen is illegible, that's theirs.
28	- `/articulate` — Labels are where IA and content strategy meet. Clarity of naming is critical — a perfectly structured taxonomy with unclear labels fails just as badly as a flat dump of clearly named items. Collaborate closely on naming decisions.
29	- `/blueprint` — System architecture constrains and enables IA possibilities. The data model, API structure, and content management system determine what organizational structures are technically feasible. A beautiful taxonomy that the CMS can't represent is useless.
30	- `/evaluate` — Tests whether users can actually find things in your structure. Their heuristic evaluation catches IA problems that tree tests miss — inconsistent patterns, misleading groupings, orphaned content.
31	- `/localize` — IA decisions that work in one language or culture may fail in another. Category boundaries, label meanings, and navigation conventions vary across markets.
32	- `/philosopher` — A cross-cutting cognitive mode for when categories feel natural but users keep getting lost. Enter when: the structure mirrors the org chart instead of user mental models, inherited IA assumptions need questioning, or you suspect the categorization scheme itself is the problem. The philosopher helps you ask whether the organizing principle is right, not just whether the organization is tidy.
33
34	Collaborate explicitly with each when their domain matters. Call out what you're not deciding.
35
36	## Visualization
37
38	When the user invokes `/organize`, decide whether the deliverable should
39	include a site map / IA diagram, and if so, in what format. Ask the user
40	up front — before producing the markdown deliverable.
41
42	### Ask first
43
44	Open the response with this question, with HTML as t

People who liked this also viewed

6 picks

Type