Designs, reviews, and implements app UX architecture for mobile, tablet, desktop, native, hybrid, cross-platform, and web/PWA apps. Use when shaping information architecture, navigation models, route contracts, URLs, deep links, state restoration, adaptive layouts, windows, sidebars, inspectors, toolbars, menus, command palettes, task flows, permission flows, accessibility, widgets, shortcuts, App Intents, App Actions, or system entry points. Trigger when the user asks for app UX, mobile UX, desktop app UX, app navigation, tabs vs sidebars, back behavior, deep links, route design, PWA navigation, app review, or a framework-agnostic plan before choosing SwiftUI, UIKit, AppKit, Jetpack Compose, React Native, Flutter, Kotlin Multiplatform, Electron, Tauri, Capacitor, native web views, or a PWA stack.
Writes, refines, splits, and scores the issue artifact itself: compact implementer-ready body, acceptance criteria, scope boundary, routing metadata, and complexity. Use when the user asks to create an issue, write ticket-ready issue text, refine issue scope, add acceptance criteria, add issue metadata, estimate issue points, split oversized work, or make one issue clear enough for an implementer. Do not use for picking work, tidying Linear projects, implementation, pull requests, or project planning.
Keeps an existing Linear project tidy after planning and during execution. Use when the user asks to "tidy Linear", "clean up the project", "audit issues", "find duplicates", "check stale blockers", "fix project drift", or run periodic Linear housekeeping on a project, initiative, or milestone set. Use when planning is underway or execution has started and relationships, labels, priorities, documents, and issue states need coherence without changing product scope.
Create, audit, document, and evolve digital design systems from the bundled universal design-system guide. Use when the user says "create a design system", "write a system brief", "audit our design system", "define tokens", "make a component spec", "plan adoption", "write release notes", "create governance", "build a design-system roadmap", or asks about foundations, color, typography, spacing, motion, media, data visualization, content voice, accessibility, component APIs, component libraries, patterns, templates, themes, modes, multi-brand architecture, platform support, engineering architecture, design tooling, source-of-truth rules, documentation, contribution, deprecation, migration, testing, quality gates, metrics, maturity, templates, or readiness checklists.
Use when the user asks to create, update, review, or refactor an agent skill, including requests like "turn this workflow into a skill", "make a skill for this", "fix this SKILL.md", "add references to this skill", "make this skill work in Codex and Claude", or "split this bloated skill". Creates skill directories, writes portable SKILL.md frontmatter and workflows, adds references, validates structure and token budgets. For adding executable helpers, use the tooling skill.
Mines recent Codex or Claude agent conversations and git history for struggles, repeated corrections, rework patterns, and taste signals — then turns findings into new skills or updates to existing ones. Use when retrospecting on recent coding sessions, extracting learnings, identifying skill gaps, improving skills from real usage patterns, codifying recurring preferences, or when the user says "retro this repo", "mine recent conversations", "what should become a skill", or "find repeated agent mistakes".
Cross-platform Apple Human Interface Guidelines: color, typography, layout, materials, motion, accessibility, SF Symbols, branding, plus shared UI elements (activity views, rating indicators, web views, …) and meta sections (components, patterns, technologies). Use when the design topic is platform-agnostic. User says: "iOS color tokens", "SF Symbols", "Apple typography", "dark mode guidance".
Apple Human Interface Guidelines by platform: iOS and iPadOS, macOS, watchOS, tvOS, and visionOS UI components, controls, navigation, and platform conventions. Use when designing, building, or auditing UI for a specific Apple platform. Pair with `foundations` for shared Apple design principles and `services` for framework integrations. User says: "design iPhone UI", "macOS component", "watchOS audit", "tvOS navigation", "visionOS layout".