What is information-architecture?

A planning guide for the structure of a website or software product before visual design and coding begin. It covers navigation, content grouping, page layouts, web addresses, and the paths users take.

Use it to plan site navigation, organize documentation or other content, map onboarding and other user flows, and define page and URL structures.

It helps prevent confusing menus, scattered content, and page structures that are difficult to change later. It also connects the design brief to concrete build tasks.

information-architecture — Skill for Claude Code by julianoczkowski

Install

Getting it into your agent

One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.

Any agent

npx skills add julianoczkowski/designer-skills --skill information-architecture

Clone the repo

git clone --depth 1 https://github.com/julianoczkowski/designer-skills

Made for: Claude Code.

Or install designer-skills, the plugin that ships this one along with the rest of its 8 skills.

Wrote this? Show the measurements

A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.

README.md

[![agentmods](https://agentmods.dev/badge/skills/julianoczkowski/designer-skills/information-architecture/github.svg)](https://agentmods.dev/skills/julianoczkowski/designer-skills/information-architecture)

Your own site

<a href="https://agentmods.dev/skills/julianoczkowski/designer-skills/information-architecture"><img src="https://agentmods.dev/badge/skills/julianoczkowski/designer-skills/information-architecture/github.svg" alt="Measured on agentmods" height="20"></a>

Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.

Your own site · 80×15

<a href="https://agentmods.dev/skills/julianoczkowski/designer-skills/information-architecture"><img src="https://agentmods.dev/badge/skills/julianoczkowski/designer-skills/information-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

Per session 63 Skills are progressive disclosure: only the name and description are preloaded; the body loads when the skill is used.

When invoked 1,065 The whole file, excluding the scripts and references it only reads on demand.

Security scan A 0 findings. A grade says what 26 rules found in the file — not that it is safe. Third-party audits

Socket pass 30 Mar 2026
Snyk pass 30 Mar 2026
NVIDIA SkillSpector pass 7 Sept 2026

How audits are shown

Origin original No closer match found in the catalogue.

Token cost

What it costs to keep this loaded

Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.

Model	Per session	Once invoked
Fable 5.1	$0.00063	$0.01065
Opus 5	$0.00032	$0.00532
Sonnet 5	$0.00013	$0.00213
Haiku 4.5	$0.00006	$0.00106

Measured 12d ago against content hash 7aad60e5568d, method: parsed. Prices are Anthropic first-party input rates as of 2026-09-11, from the pricing page.

Security

Grade A, and why

information-architecture scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 12d ago.

A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.

Nothing flagged

None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.

information-architecture/SKILL.md · 112 lines

How it starts

The opening of the file, as written. The whole thing — 112 lines — stays where its author put it; the contents beside it link to each section on GitHub.

This skill defines the structural skeleton of a product or site. It sits between the design brief and the build. Run this after the brief is written and before tasks are created.

Example prompts

"Plan the IA for this app before I start building"
"Map out the navigation and page structure"
"I need to organize the content for a documentation site"
"Define user flows for the onboarding experience"

Process

Look for an existing design brief at .design/*/DESIGN_BRIEF.md. If multiple subfolders exist, use the most recently modified one, or ask the user which feature they are working on. If no brief exists, ask the user what they are building and for whom.
Explore the existing codebase to understand what structure already exists:
- Routing: Next.js app/ or pages/ directory, React Router config, Vue Router, SvelteKit routes, or static HTML page files
- Navigation components: header, sidebar, navbar, breadcrumb, footer components
- Layout components: root layouts, nested layouts, page wrappers, container components
- Page directories: how pages are currently organized in the file system
- URL patterns: existing slugs, dynamic segments, query parameter conventions
- CMS or data layer: content models, API routes, data fetching patterns, MDX/content directories
- If structure exists, this skill extends and improves it. Do not propose a new architecture that ignores what is already built.
Interview the user about structural decisions. For each question, provide your recommended answer.

Cover at minimum:
- What are the primary things a user needs to find or do? Rank by frequency.
- How many levels of navigation depth are acceptable?
- What content will grow over time vs. what is fixed?
- Are there distinct user types who need different entry points?
- What is the one page/view where the user spends 80% of their time?
Once you have a shared understanding, produce the IA document using the template below and save it as INFORMATION_ARCHITECTURE.md in the same .design/<feature-slug>/ subfolder as the design brief.

Read the full file on GitHub · 112 lines

Changes

What this file has done since we first saw it

Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.

12d ago First seen · 112 lines · 63 tokens per session scan A 7aad60e5568d

Subscribe to this mod's changes

information-architecture is a skill published in the GitHub repository julianoczkowski/designer-skills (547 stars, last pushed 2mo ago), licensed Apache-2.0. It adds 63 tokens to every session and 1,065 once invoked, about $0.0003 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.

Design and UX Planning

webgl-holographic-foil

A self-contained WebGL2 hero: thin-film interference over a crushed-foil surface whose palette shifts with the viewing angle; move the cursor to tilt the film.

nexu-io/open-design · 41 tokens

html-ppt-hermes-cyber-terminal

OpenDesign + BYOK: choosing and wiring your own model, hands-on — cost, quality, and the routing decision. Built as a decision-grade AI literacy deck for engineers, IT, applied-AI teams.

nexu-io/open-design · 53 tokens

html-ppt-taste-brutalist

16:9 HTML deck in tactical-telemetry / CRT-terminal taste. Deactivated-CRT charcoal slides, white-phosphor monospace, hazard-red accent, scanline overlay, ASCII syntax, density over decoration. Distilled from Leonxlnx/taste-skill brutalist-skill (Tactical Telemetry mode).

nexu-io/open-design · 78 tokens

information-architecture