원클릭으로 Manus에서 모든 스킬 실행

ui-ux-pro-max

스타1

포크0

업데이트2026년 6월 1일 21:32

Design intelligence for producing professional UI/UX documentation across platforms (web, mobile, desktop). Use during the design phase of user-facing features to generate a persistent design system — tokens, component specs, layout, states, accessibility — and per-page design docs. Invoked by sdlc-design. Produces design-system/MASTER.md as the single source of truth for visual and interaction design.

설치

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

Manus에서 실행

출처

AZANIR

AZANIR/sdlc-kit

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

다운로드

Manus에서 실행

UI/UX Pro Max (design documentation)

Adapted from nextlevelbuilder/ui-ux-pro-max-skill. Generates design intelligence, not code.

Modes

--design-system — produce the master system (run this first).
--persist — write outputs to disk instead of only chatting them (always use in SDLC).
per-page — generate a screen/flow spec that overrides the master where needed.

design-system/MASTER.md must contain

Design tokens — color (with semantic roles), typography scale, spacing, radius, shadows.
Component specs — for each component: anatomy, variants, sizes, states (default/hover/focus/active/disabled/loading/error), do/don't.
Layout — grid, breakpoints, responsive rules.
Accessibility — contrast targets, focus order, keyboard, ARIA expectations, motion/reduced-motion.
Content/voice — tone, capitalization, error-message style (Ukrainian, per policy).

Per-page docs (design-system/pages/.md)

Purpose, entry/exit, states (empty/loading/error/success), responsive notes, and which acceptance criteria from spec.md the page satisfies.

Rules

Be platform-aware: don't apply mobile gestures to a desktop-only tool, etc.
Every screen must trace to a spec acceptance criterion. Flag any orphan screens.
Hand the page list back to sdlc-design so it can append build tasks to tasks.md.

Примітка (UK)

Скіл генерує дизайн-документацію (не код). Головний артефакт — design-system/MASTER.md: токени, специфікації компонентів зі станами, лейаут, доступність і тон комунікації українською. Кожен екран має відповідати критерію приймання зі специфікації.

이 저장소의 다른 Skills

같은 저장소

code-graph

AZANIR/sdlc-kit

Optional code-navigation aid for large or unfamiliar codebases. Use during the plan or implement phases to map module dependencies, find where a symbol is defined and used, and orient before making changes. This is a navigation helper only — it is NOT the memory layer. Skip for small projects.

2026-06-011

memory-manager

AZANIR/sdlc-kit

Persistent memory layer across sessions. Use to recall prior context at the start of work, to store checkpoints at phase boundaries, and to answer "what did we decide / do before" questions. Backed by the agentmemory server (local SQLite + vector embeddings) on port 3111, with an MCP-only fallback. Every phase skill calls this to survive /clear and compaction boundaries.

2026-06-011

sdlc-design

AZANIR/sdlc-kit

Phase 4 of the SDLC, used ONLY for user-facing features. Use this to produce UI/UX design documentation and a persistent design system before implementation. Triggers when tasks.md exists and the spec marked a UI surface. Coordinates with the ui-ux-pro-max skill to generate design-system/MASTER.md and per-page specs. Skip entirely for CLI tools, libraries, or backend-only work.

2026-06-011

sdlc-implement

AZANIR/sdlc-kit

Phase 5 of the SDLC. Use this to write code that satisfies the tasks, strictly test-first (TDD). Triggers when tasks.md exists and design is done or not needed. Implements one task at a time, writing a failing test before code, then making it pass, then refactoring. Persists progress to memory after each task so work survives session boundaries.

2026-06-011

sdlc-orchestrator

AZANIR/sdlc-kit

Master coordinator for the full software development lifecycle. Use this when starting a new feature or project, when the user is unsure which phase to run, when resuming work after a break, or to establish/edit the project constitution. Routes to specify, plan, tasks, design, implement, review, and ship phases in the correct order and enforces that no phase is skipped. ALWAYS consider this skill first at the start of any development work.

2026-06-011

sdlc-plan

AZANIR/sdlc-kit

Phase 2 of the SDLC. Use this to decide HOW a specified feature will be built — architecture, tech choices, data model, API contracts, and trade-offs. Triggers after a spec exists and the user wants a technical plan or design decisions. Produces specs/<feature>/plan.md plus Architecture Decision Records (ADRs). Must read spec.md and memory/constitution.md and respect their constraints.

2026-06-011

name

ui-ux-pro-max

description

UI/UX Pro Max (design documentation)

Adapted from nextlevelbuilder/ui-ux-pro-max-skill. Generates design intelligence, not code.

Modes

--design-system — produce the master system (run this first).
--persist — write outputs to disk instead of only chatting them (always use in SDLC).
per-page — generate a screen/flow spec that overrides the master where needed.

design-system/MASTER.md must contain

Design tokens — color (with semantic roles), typography scale, spacing, radius, shadows.
Component specs — for each component: anatomy, variants, sizes, states (default/hover/focus/active/disabled/loading/error), do/don't.
Layout — grid, breakpoints, responsive rules.
Accessibility — contrast targets, focus order, keyboard, ARIA expectations, motion/reduced-motion.
Content/voice — tone, capitalization, error-message style (Ukrainian, per policy).

Per-page docs (design-system/pages/.md)

Purpose, entry/exit, states (empty/loading/error/success), responsive notes, and which acceptance criteria from spec.md the page satisfies.

Rules

Be platform-aware: don't apply mobile gestures to a desktop-only tool, etc.
Every screen must trace to a spec acceptance criterion. Flag any orphan screens.
Hand the page list back to sdlc-design so it can append build tasks to tasks.md.