Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set.

MITAuto-check: notesFrontend & Design

Install Draft Ia

skills CLI
$ npx skills add jeremylongshore/tons-of-skills-marketplace --skill draft-ia -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install jeremylongshore/tons-of-skills-marketplace draft-ia --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/jeremylongshore/tons-of-skills-marketplace.git skills-src && mkdir -p .claude/skills && cp -r skills-src/plugins/ai-agency/tonone/skills/draft-ia .claude/skills/draft-ia && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
draft-ia
GitHub stars
2.8k
Token cost
~2.3k tokens
SKILL.md length
961 words
Files
2
Skills in repo
3,342
Repo updated
First seen
Licence
MIT

At a glance

Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set.

  • Works in 7 steps: Identify the Jobs → Content Inventory → Group by User Mental Model → …
  • Asked to organize the navigation
  • SKILL.md covers When IA Work Is Actually…, Phase 1: Identify the Jobs, Phase 2: Content Inventory and Phase 3: Group by User Mental…, plus 7 more sections
  • Instructions only: no scripts, shell commands, URLs or credentials in SKILL.md

What it does

Draft Ia is an agent skill from jeremylongshore/tons-of-skills-marketplace. Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".

Its SKILL.md is about 2.3k tokens, which your agent loads only when the skill is triggered. The skill folder holds 2 other files (for example `.claude-plugin/plugin.json`).

It sits in Frontend & Design, covering UX design. The repository describes itself as: Model-agnostic agent-skills platform with a harness-free canonical layer, verified adapters, and the ccpi package manager. Explore at tonsofskills.com. The licence is MIT.

When your agent uses it

  • Asked to organize the navigation
  • Information architecture
  • How should content be structured
  • Where should X live

Example prompts

  • “organize the navigation”
  • “information architecture”
  • “how should content be structured”
  • “/draft-ia”

Requirements

  • Pre-approved tools (allowed-tools): Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Workflow steps

7 steps, taken from the step headings in SKILL.md.

  1. Identify the Jobs
  2. Content Inventory
  3. Group by User Mental Model
  4. Sitemap
  5. Navigation Pattern Decision
  6. IA Issues
  7. Migration Path (if restructuring)

What it can do on your machine

Read from SKILL.md and the folder at commit cfae287. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves these tools, so the agent can use them without asking each time:

    • Read
    • Write
    • Edit
    • Bash
    • Glob
    • Grep
    • WebFetch
    • WebSearch
    • Task
    • TodoWrite

    …and 1 more on the same allowed-tools line.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    No scripts in the folder and no shell commands in SKILL.md.

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Draft Ia loads about 2.3k tokens when it runs. Until then it costs about 80 tokens; SKILL.md has 961 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~80
When it runs · the whole SKILL.md, loaded when a task matches
~2.3k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check: notes

The automated check noted patterns worth knowing about, such as sudo or a known installer.

  • NotePre-approves every shell command (allowed-tools: Bash)SKILL.md
    allowed-tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from jeremylongshore/tons-of-skills-marketplace at commit cfae287, republished under its MIT licence (© jeremylongshore). 961 words, ~2,286 tokens.

Download SKILL.mdSave it as .claude/skills/draft-ia/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
draft-ia
description
Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Use when asked to "organize the navigation", "information architecture", "how should content be structured", "sitemap", "nav redesign", "where should X live", or "content hierarchy".
allowed-tools
Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion
version
0.6.4
author
tonone-ai <hello@tonone.ai>
license
MIT

Information Architecture

You are Draft — the UX designer on the Product Team. Structure information around what users are trying to do — not around how the product was built.

Follow the output format defined in docs/output-kit.md — 40-line CLI max, box-drawing skeleton, unified severity indicators, compressed prose.

Default to executing. With a product description or existing nav, you have enough to produce a sitemap and nav recommendation. Ask only when permission/access logic or multi-tenant complexity would materially change the output.


When IA Work Is Actually Necessary

IA is a tool, not a ritual. Before starting, make the call:

SituationWhat to do
≤5 features, single user typeFlat list. Skip IA. No taxonomy needed.
6–15 features, 1–2 user typesLight IA — one-level nav, done in 30 min
15+ features or 3+ user typesFull IA — sitemap, grouping, nav pattern
Existing nav is actively causing support tickets or drop-offRestructure IA with user job mapping
Existing nav is just "feeling messy"Probably a labeling problem, not a structure problem

If someone asks for IA work and the product has 4 features, say so. Overengineered IA is worse than no IA.


Phase 1: Identify the Jobs

Before inventorying content, identify what users are trying to accomplish. Navigation structure follows jobs — not org structure, not feature chronology.

For each distinct user type, list their top 3–5 jobs:

User type: [e.g., Project manager]
Jobs:
  1. See what needs my attention right now
  2. Check status of work in progress
  3. Add or reassign a task
  4. Review what shipped this week

User type: [e.g., Individual contributor]
Jobs:
  1. See what I'm supposed to do today
  2. Update the status of my work
  3. Find context on a task

These jobs become the test for every structural decision: "Does this grouping serve the job, or does it serve the internal taxonomy?"

If you're working from a Helm brief, extract the jobs from user_context and success_criteria. If working from a product description, infer and confirm.


Phase 2: Content Inventory

List every distinct place in the product — every page, section, or feature area. Be complete.

ItemTypePrimary job it servesAccess levelCurrent location
DashboardPageSee what needs attentionAll users/
Project settingsPageConfigure a projectOwners only/settings/project
Team membersPageManage accessAdmins only/settings/team
ExportFeatureDownload dataPro usersburied in menu

Flag items with no clear job in the "Primary job it serves" column — these are candidates for removal, not reorganization.


Phase 3: Group by User Mental Model

Group items as users would reach for them — not as engineering built them.

Grouping rules:

  • Items used in the same workflow belong together
  • Frequency of use determines depth: daily use = top nav, weekly = second level, rare = settings
  • Items that cause confusion when separated should be co-located (even if they're architecturally different)
  • Settings is always last; it is not a dumping ground for anything that doesn't fit elsewhere

Produce 3–6 top-level groups. Fewer is better. If you have 7+, you have a labeling problem or you're not grouping aggressively enough.

Label rule: Navigation labels are verbs or nouns from the user's vocabulary, not the product's. "Workspace" might mean nothing to a user who thinks "my stuff." Test labels against the jobs list.


Phase 4: Sitemap

Present the full navigation hierarchy:

[Product Name]
│
├── [Primary nav 1]           ← daily job; use user's word, not product's
│     ├── [Sub-section A]
│     └── [Sub-section B]
│
├── [Primary nav 2]
│     ├── [Sub-section A]
│     └── [Sub-section B]
│
├── [Primary nav 3]           ← single item, no sub-sections needed
│
└── Settings                  ← always last
      ├── Profile
      ├── Account / Billing
      ├── Team                (admin only)
      └── Integrations        (pro only)

Access level notation inline:

  • (all) — all users
  • (admin) — owner/admin only
  • (pro) — paid tier
  • (new) — recently added; may need discovery treatment (tooltip, badge)

Phase 5: Navigation Pattern Decision

Recommend the right navigation component. Structural decision — affects every screen in the product.

PatternWhen to use
Top nav≤6 primary sections; marketing sites; simple apps with wide screens
Left sidebar6–15 sections; complex apps; power users who navigate frequently
Bottom tab barMobile-first; 3–5 core sections; thumb-reachable primary actions
BreadcrumbsDeep content hierarchy; docs; CMS; always secondary to primary nav
Contextual navSection-specific secondary actions within a section

State the recommendation and the reason in one sentence. If mobile and desktop need different patterns, say so explicitly.


Show full SKILL.md (360 more words)Show less

Phase 6: IA Issues

Flag structural problems. Be specific — vague "it could be better organized" is not useful.

  • Orphaned pages — pages with no clear nav path; user can only reach them via direct URL or search
  • Buried critical features — high-frequency jobs more than 2 levels deep
  • Overcrowded sections — a nav group with 8+ items (needs sub-grouping or splitting)
  • Missing category — a clear user job with no home in the current structure
  • Org-structure navigation — sections named after teams or internal systems, not user goals
  • Duplicate paths — same content reachable from 2+ unrelated locations (inconsistent, erodes mental model)

For each issue: state it, state why it's a problem, state the fix.


Phase 7: Migration Path (if restructuring)

If restructuring existing navigation, define the migration path. Users have muscle memory.

  • What moves — item, current location, new location
  • What gets renamed — old label → new label (and why)
  • What gets removed — and where that content/feature goes instead
  • Redirect strategy — old URLs that need redirects
  • Discovery treatment — items that moved need a tooltip or "moved to X" banner for 30 days

Skip this if building from scratch.


"Done Enough to Build" Gate

Before handing off:

[ ] User jobs identified and used as grouping anchor
[ ] Every nav item maps to at least one job
[ ] Items with no clear job are flagged for removal, not reorganization
[ ] Nav labels use user vocabulary, not internal product vocabulary
[ ] Navigation pattern selected with rationale
[ ] Access levels noted inline
[ ] IA issues called out with specific fixes
[ ] Migration path included if restructuring

If all checked: ship it. IA does not require validation workshops before the product exists. Ship, instrument navigation clicks, and restructure when you have real behavioral data.


Anti-Patterns

  • IA before jobs — grouping content without knowing what users are trying to do produces org charts, not navigation
  • Navigation that mirrors the engineering architecture or the company's team structure
  • Treating Settings as overflow — if important features live in Settings, the IA has a structural gap
  • More than 6 top-level nav items — beyond this, users stop reading the nav and start searching
  • Taxonomy projects for products with fewer than 10 features
  • Validating IA with card sorts before any users exist — you don't have enough signal; ship and measure
  • "Miscellaneous" or "Other" as a nav category — if it needs a catch-all, the grouping is wrong

Delivery

If output exceeds the 40-line CLI budget, invoke /atlas-report with the full findings. The HTML report is the output. CLI is the receipt — box header, one-line verdict, top 3 findings, and the report path. Never dump analysis to CLI.

© jeremylongshore, MIT. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in plugins/ai-agency/tonone/skills/draft-ia of jeremylongshore/tons-of-skills-marketplace.

  • SKILL.md
  • .claude-plugin/plugin.json

Open the folder on GitHubat commit cfae287

Compare with similar skills

Draft Ia next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Draft Ia compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Draft Ia this skilljeremylongshore/tons-of-skills-marketplace2.8k—~2.3kAutomated safety check: NotesMIT
Impeccablebestofjs/bestofjs3.1k26 repos~2.6kAutomated safety check: PassMIT
Interface Design for Dashboards and Appsholaboss-ai/holaOS11k3 repos~6kAutomated safety check: PassMIT
Animategrowupanand/ConvoForm1026 repos~1.9kAutomated safety check: PassApache-2.0
Migrate Content Iadocker/docs4.7k—~5.1kAutomated safety check: PassApache-2.0
UX WalkthroughXiaoMi/hiui879—~1.3kAutomated safety check: PassMIT

Similar skills

  • Impeccable

    bestofjs/bestofjs

    A skill your agent uses when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a…

    3.1k GitHub starsUsed in 26 repos~2.6k tokens
    Frontend & DesignAuto-check passed
  • Pushes an agent past generic defaults when designing dashboards, admin panels, SaaS apps and tools, with attention to structure, type, navigation and how data is shown.

    11k GitHub starsUsed in 3 repos~6k tokens
    Frontend & DesignAuto-check passed
  • Animate

    growupanand/ConvoForm

    Review a feature and enhance it with purposeful animations, micro-interactions, and motion effects that improve usability and delight.

    102 GitHub starsUsed in 6 repos~1.9k tokens
    Frontend & DesignAuto-check passed
  • Official

    Handle Hugo docs information-architecture moves: discover old vs new URLs, add front matter aliases (Phase 1), update in-repo links (Phase 2), interactive List 2 resolution and fragment validation…

    4.7k GitHub stars~5.1k tokensUpdated yesterday
    Frontend & DesignAuto-check passed
  • UX Walkthrough

    XiaoMi/hiui

    体验走查 skill。适用于代码库、URL、截图三种输入,输出结构化体验问题报告,并同步生成本地 docx 报告。触发词:体验走查、UX review、交互走查、界面审查、体验问题。

    879 GitHub stars~1.3k tokensUpdated 2 mo ago
    Frontend & DesignAuto-check passed
  • Color Audit

    rome-os/rome

    Audit a design system's color palette against measurable color-science disciplines — WCAG/APCA contrast of declared token pairs, perceptual (OKLCH) ramp uniformity, color-blindness safety of…

    743 GitHub stars~2.7k tokensUpdated today
    Frontend & DesignAuto-check passed

More from jeremylongshore/tons-of-skills-marketplace

All 3,342 skills in this repo
  • Performing Security Code Review

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to conduct a security-focused code review using the security-agent plugin.

    2.8k GitHub starsUsed in 2 repos~1.3k tokens
    Auto-check: notes
  • Adapting Transfer Learning Models

    jeremylongshore/tons-of-skills-marketplace

    Build this skill automates the adaptation of pre-trained machine learning models using transfer learning techniques.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Agent Context Loader

    jeremylongshore/tons-of-skills-marketplace

    Execute proactive auto-loading: automatically detects and loads agents.md files.

    2.8k GitHub stars~1.1k tokensUpdated yesterday
    Auto-check passed
  • Aggregating Performance Metrics

    jeremylongshore/tons-of-skills-marketplace

    Aggregate and centralize performance metrics from applications, systems, databases, caches, and services.

    2.8k GitHub stars~1.2k tokensUpdated yesterday
    Auto-check passed
  • Analyzing Capacity Planning

    jeremylongshore/tons-of-skills-marketplace

    Execute this skill enables AI assistant to analyze capacity requirements and plan for future growth.

    2.8k GitHub stars~947 tokensUpdated yesterday
    Auto-check passed
  • Analyzing Database Indexes

    jeremylongshore/tons-of-skills-marketplace

    Process use when you need to work with database indexing. An agent skill from jeremylongshore/tons-of-skills-marketplace.

    2.8k GitHub stars~2k tokensUpdated yesterday
    Auto-check passed

Questions about Draft Ia

What does Draft Ia do?

Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set. Draft Ia is an agent skill from jeremylongshore/tons-of-skills-marketplace. Information architecture — design navigation structure, content hierarchy, sitemap, and taxonomy for a product or feature set.

When should I use Draft Ia?

Draft Ia fits situations like: asked to organize the navigation; information architecture; how should content be structured; where should X live.

How do I install Draft Ia in Claude Code?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill draft-ia -a claude-code`. Or copy the skill folder (plugins/ai-agency/tonone/skills/draft-ia in jeremylongshore/tons-of-skills-marketplace) into .claude/skills/draft-ia in your project. Claude Code loads it when a task matches its description.

How do I install Draft Ia in Codex?

Run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill draft-ia -a codex`. Or copy the skill folder (plugins/ai-agency/tonone/skills/draft-ia in jeremylongshore/tons-of-skills-marketplace) into .agents/skills/draft-ia in your project. Codex loads it when a task matches its description.

Can I use Draft Ia in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add jeremylongshore/tons-of-skills-marketplace --skill draft-ia -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/draft-ia, .gemini/skills/draft-ia, .github/skills/draft-ia and .opencode/skills/draft-ia in your project.

What does Draft Ia need to run?

SKILL.md names no scripts, command-line tools or credentials: Draft Ia is instructions for the agent only. Its frontmatter pre-approves these tools: Read, Write, Edit, Bash, Glob, Grep, WebFetch, WebSearch, Task, TodoWrite, AskUserQuestion.

Does Draft Ia access the network?

SKILL.md contains no URLs. Any network use would come from the scripts or tools the agent runs. This is read from the text; nothing was executed.

Is Draft Ia safe to install?

Our automated static check of SKILL.md found notes only (pre-approves every shell command (allowed-tools: bash)), nothing it rates as a warning. It is not a guarantee. Review the folder before installing.

What licence does Draft Ia use?

Draft Ia is published under the MIT licence (declared in SKILL.md). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Draft Ia use?

About 2.3k tokens (SKILL.md is roughly 9.1k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Draft Ia?

Skills that share tags, products or a category with Draft Ia: Impeccable (bestofjs/bestofjs, 3.1k stars), Interface Design for Dashboards and Apps (holaboss-ai/holaOS, 11k stars), Animate (growupanand/ConvoForm, 102 stars) and Migrate Content Ia (docker/docs, 4.7k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Draft Ia?

jeremylongshore (a GitHub user) maintains it in jeremylongshore/tons-of-skills-marketplace, which has 2,827 GitHub stars. The repository holds 3,342 skills in this directory. The repository was last updated on October 10, 2026.

Source: jeremylongshore/tons-of-skills-marketplace on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.