ux-architecture

스타0

포크0

업데이트2026년 7월 17일 17:28

Specifies journeys, information architecture, responsive behavior, content hierarchy, and accessible interaction states.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

출처

lebobo88

lebobo88/orchestrator

GitHub 저장소 열기 Creator 저장소 보기

다운로드

UX architecture

Return one self-contained UX_SPEC packet from UX_SPEC through END_UX_SPEC. Use the top-level fields journeys:, information_architecture:, responsive_behavior:, accessibility:, states:, evidence:, assumptions:, and unresolved_decisions:. Populate them with:

primary and secondary users, jobs, entry points, exit states, and success signals;
information architecture and ordered journeys, including recovery paths;
content hierarchy and content requirements, with fabricated content prohibited;
desktop, tablet, and mobile behavior expressed as layout decisions rather than device labels alone;
keyboard order, focus movement, status announcements, validation, destructive-action confirmation, and reduced-motion implications;
applicable loading, empty, partial, error, success, offline, permission, disabled, selected, hover, focus, and active states;
unresolved product-policy decisions separated from safe design assumptions.

Prefer the smallest coherent flow. Do not add screens, settings, onboarding, or future-proof abstractions that the requested outcome does not need.

이 저장소의 다른 Skills

같은 저장소

browser-validator-core

lebobo88/orchestrator

Screenshot-first visual end-to-end validation policy for browser-rendered UI and webview jobs after verifier approval.

2026-07-180

build

lebobo88/orchestrator

Default engineering workflow. Classify a technical request, route it through the native T1/T2/T3 engineering fleet, and return only independently verified completion to the orchestrator.

2026-07-180

claude-operations

lebobo88/orchestrator

Safely operate Claude Code's opt-in advanced capabilities—sessions, worktrees, agent teams, Skills, MCP, plugins, hooks, Channels, schedules, goals, and Agent SDK integrations—when the user explicitly asks for one. Do not use for an ordinary build request.

2026-07-170

cross-vendor-judging

lebobo88/orchestrator

Routes selective local Codex plan, code, verification, and visual judgment with evidence-backed blocking and strict cost caps.

2026-07-170

design-core

lebobo88/orchestrator

Shared evidence, accessibility, context, and handoff rules for the local design-agent fleet.

2026-07-170

design-direction

lebobo88/orchestrator

Produces contextual creative theses and bounded visual directions without generic model defaults.

2026-07-170

name	ux-architecture
description	Specifies journeys, information architecture, responsive behavior, content hierarchy, and accessible interaction states.

UX architecture

primary and secondary users, jobs, entry points, exit states, and success signals;
information architecture and ordered journeys, including recovery paths;
content hierarchy and content requirements, with fabricated content prohibited;
desktop, tablet, and mobile behavior expressed as layout decisions rather than device labels alone;
keyboard order, focus movement, status announcements, validation, destructive-action confirmation, and reduced-motion implications;
applicable loading, empty, partial, error, success, offline, permission, disabled, selected, hover, focus, and active states;
unresolved product-policy decisions separated from safe design assumptions.

Prefer the smallest coherent flow. Do not add screens, settings, onboarding, or future-proof abstractions that the requested outcome does not need.