What is ux-information-architecture?

Information architecture is the practice of organizing and labeling content so people can find it. This guidance covers categories, screen names, sorting, filtering, settings, and levels of hierarchy.

Use it to plan a sitemap, group content, name screens, organize settings, choose sort and filter controls, show timestamps, and reduce unnecessary scrolling.

It removes the need to search through confusing menus or guess where information belongs. Clear structure lowers the mental effort required to use an app.

ux-information-architecture — Skill by parhamb/design-skills

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 parhamb/design-skills --skill ux-information-architecture

Clone the repo

git clone --depth 1 https://github.com/parhamb/design-skills

Made for: Claude Code, Codex.

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/parhamb/design-skills/ux-information-architecture/github.svg)](https://agentmods.dev/skills/parhamb/design-skills/ux-information-architecture)

Your own site

<a href="https://agentmods.dev/skills/parhamb/design-skills/ux-information-architecture"><img src="https://agentmods.dev/badge/skills/parhamb/design-skills/ux-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/parhamb/design-skills/ux-information-architecture"><img src="https://agentmods.dev/badge/skills/parhamb/design-skills/ux-information-architecture.svg" alt="Reviewed on agentmods" width="80" height="20"></a>

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

When invoked 713 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.

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.00057	$0.00713
Opus 5.5	$0.00023	$0.00285
Sonnet 5.5	$0.00011	$0.00143
Haiku 4.5	$0.00006	$0.00071

Measured 2mo ago against content hash 9db93ff1791d, method: parsed. Prices are Anthropic first-party input rates as of 2026-10-07, from the pricing page.

Security

Grade A, and why

ux-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 2mo 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.

ux-information-architecture/SKILL.md · 77 lines

How it starts

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

Information Architecture (IA)

IA is the practice of organizing, structuring, and labeling content so users can find what they need. Poor IA is the invisible reason users say "I just couldn't find it."

Checklist

Item	Guidance
Content categorization	Group by user mental models, not the internal org chart or database structure.
Well-structured content	Maximum 2 levels of hierarchy in any list. Never nest deeper than that.
Screen titles	Every screen has a clear, descriptive title that matches the nav item that opened it.
Sort options	Default sort is the most useful (date, relevance). User can change it.
Filter options	Active filter count shown ("3 filters active"). All filters can be cleared in one tap.
Minimal scrolling	Critical information is visible without scrolling. Details load progressively.
Timestamp visibility	Relative time near the event ("2 hours ago"), full timestamp accessible on tap.
Settings organization	Settings are grouped by theme: Account, Notifications, Privacy, Appearance, About.
F-pattern layout	Most important content is at the top and left of each screen.
Quick checkout	Purchase flow is 5 steps or fewer. Guest checkout is available.

IA Research Methods

Card sorting: Run an open card sort with 10 to 15 representative users before finalizing category labels. Use the results to name categories with the words users actually choose, not internal terminology.

Tree testing: Validate your structure by asking users to find items in a text-only tree with no visual design. If users fail to find items in the tree, the IA is the problem — not the visual design.

First-click testing: Research shows that 85% of users who click correctly on their first attempt go on to complete the task. Test key flows with first-click tests before investing in full prototypes.

Labeling Principles

Use words your users use, not what your engineers or product managers call things internally. Avoid jargon and acronyms for first-time users. Keep navigation labels to 1 or 2 words. Be consistent — if one section is called "Saved," do not call the same concept "Bookmarks" elsewhere in the app.

Read the full file on GitHub · 77 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.

2mo ago First seen · 77 lines · 57 tokens per session scan A 9db93ff1791d

Subscribe to this mod's changes

ux-information-architecture is a skill published in the GitHub repository parhamb/design-skills (25 stars, last pushed 4mo ago), licensed MIT. It adds 57 tokens to every session and 713 once invoked, about $0.0002 per session on Opus 5.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

ux-information-architecture next to 6 skills from other repositories
Mod	Type	Stars	Last push	Licence	Scan	Tokens	Works with
ux-information-architectureparhamb/design-skills	Skill	25	4mo ago	MIT	A	57	Claude Code, Codex
webgl-holographic-foilnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	41	Claude Code, Codex
html-ppt-hermes-cyber-terminalnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	53	Claude Code, Codex
html-ppt-taste-brutalistnexu-io/open-design	Skill	106k	yesterday	Apache-2.0	A	78	Claude Code, Codex
visual-ralphYeachan-Heo/oh-my-codex	Skill	34k	4d ago	MIT	A	52	Codex
glance-canonical-layoutsandroid/skills	Skill	10k	yesterday	Apache-2.0	A	56	Claude Code
accessibilitymicrosoft/hve-core	Skill	1.6k	yesterday	MIT	A	47	Claude Code