UI Architecture Review

Systematic critique of UI information architecture and interaction design. Challenges whether elements should exist, what belongs together, and whether the logical structure of a component is right. Use when reviewing input surfaces, toolbars, action bars, compose flows, menus, or any component where the STRUCTURE (not style) needs questioning. Triggers: "review this UI", "does this make sense", "challenge this design", "IA audit", "interaction critique", "what's wrong with this component", or when a design review focuses on pixels before questioning architecture.

Install

skills CLI (Claude Code, Cursor, Codex and more)
npx skills add catch-the-wave/fullstack-ios-claude-skills --skill ui-architecture-review
Manual install
git clone --depth 1 https://github.com/catch-the-wave/fullstack-ios-claude-skills.git /tmp/fullstack-ios-claude-skills
mkdir -p ~/.claude/skills
cp -r /tmp/fullstack-ios-claude-skills/research/ui-architecture-review ~/.claude/skills/ui-architecture-review

Personal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.

From the SKILL.md

<essential_principles>

**Structure precedes style.** If the information architecture is wrong, no amount of typography, haptics, or spring animations will fix it. This skill challenges logical structure before anyone touches pixels.

**Every element must justify its existence.** "Who needs this, how often, and what breaks if I remove it?" Elements that can't answer all three get killed or moved.

**Concerns don't mix.** Content creation, organization, media attachment, and mode switching are different concerns. Putting them in one flat menu creates a junk drawer, not a toolbar.

**Reference apps are evidence, not inspiration.** When Apple Notes, Things, Bear, Linear, and Notion all separate a concern the same way, that's a discovered pattern, not a style choice.
</essential_principles>

<objective>
Provide systematic interaction architecture critique grounded in Cognitive Dimensions of Notations (CDN), Bastien-Scapin Ergonomic Criteria, action-object analysis, and UICrit evaluation patterns.

This is the design equivalent of code review — challenge architecture, not aesthetics.
</objective>

<quick_start>
Given a component (code, screenshot, or description), run in this order:

1. **Element justification** — For each interactive element: who uses it, how often, what if removed? → KEEP / MOVE / MERGE / KILL
2. **Concern separation** — Are different concerns (creation, organization, attachment, destruction) mixed in one surface?
Read the full skill on GitHub

Details

Skill name
ui-architecture-review
Path
research/ui-architecture-review/SKILL.md
License
MIT
Repo updated
17 September 2026

FAQ

What does the UI Architecture Review skill do?

Systematic critique of UI information architecture and interaction design. Challenges whether elements should exist, what belongs together, and whether the logical structure of a component is right. Use when reviewing input surfaces, toolbars, action bars, compose flows, menus, or any component where the STRUCTURE (not style) needs questioning. Triggers: "review this UI", "does this make sense", "challenge this design", "IA audit", "interaction critique", "what's wrong with this component", or when a design review focuses on pixels before questioning architecture.

How do I install the UI Architecture Review skill?

skills CLI (Claude Code, Cursor, Codex and more): npx skills add catch-the-wave/fullstack-ios-claude-skills --skill ui-architecture-review. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.

Is UI Architecture Review popular?

It lives in catch-the-wave/fullstack-ios-claude-skills, which has 5 GitHub stars and 0 forks.

Related skills

Image to Code

5

catch-the-wave/fullstack-ios-claude-skills

Elite website image-to-code skill for Codex. For visually important web tasks, it must first generate the design image(s) itself, deeply analyze them, then implement the website to match them as closely as possible. In Codex, it must prefer large, readable, section-specific images instead of tiny compressed boards, generate fresh standalone images for sections or detail views instead of cropping old ones, avoid lazy under-generation, avoid cards-inside-cards-inside-cards UI, and keep the hero clean, spacious, readable, and visible on a small laptop.

Images, Video & AudioIn 2 lists

Full Output Enforcement

5

catch-the-wave/fullstack-ios-claude-skills

Overrides default LLM truncation behavior. Enforces complete code generation, bans placeholder patterns, and handles token-limit splits cleanly. Apply to any task requiring exhaustive, unabridged output.

Productivity & NotesIn 2 lists

Gpt Taste

5

catch-the-wave/fullstack-ios-claude-skills

Elite UX/UI & Advanced GSAP Motion Engineer. Enforces Python-driven true randomization for layout variance, strict AIDA page structure, wide editorial typography (bans 6-line wraps), gapless bento grids, strict GSAP ScrollTriggers (pinning, stacking, scrubbing), inline micro-images, and massive section spacing.

AI, LLMs & AgentsIn 2 lists

UI UX Designer

5

catch-the-wave/fullstack-ios-claude-skills

Use when designing interfaces, improving user experiences, creating design systems, or addressing accessibility issues

Frontend & Design

Swiftui Animation

5

catch-the-wave/fullstack-ios-claude-skills

Implement, review, or improve SwiftUI animations and transitions. Use when adding explicit animations with withAnimation, configuring implicit animations with .animation(_:body:) or .animation(_:value:), configuring spring animations (.smooth, .snappy, .bouncy), building phase or keyframe animations with PhaseAnimator/KeyframeAnimator, creating hero transitions with matchedGeometryEffect or matchedTransitionSource, adding SF Symbol effects (bounce, pulse, variableColor, breathe, rotate, wiggle), implementing custom Transition or CustomAnimation types, or ensuring animations respect accessibili

Frontend & Design

Vue Composables

8

Freddy-CHEN-ux/00_claude_skills

Use when creating reusable composables, managing reactive state, or implementing the Composition API. Load for useX patterns, Pinia store patterns, withLoadingState helper, lifecycle management, and type-safe state patterns. Covers composable structure, error handling, and testing composables.

Frontend & Design

Browse the most popular Claude skills, all frontend & design skills, or write your own with the skills generator.