UI/UX, 로고, 슬라이드, 이미지 생성 (7.4천건)
Orchestrate the UI team through the full UX pipeline: from UX spec authoring through visual design, implementation, review, and polish. Integrates with /ux-design, /ux-review, and studio UX templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided, section-by-section UX spec authoring for a screen, flow, or HUD. Reads game concept, player journey, and relevant GDDs to provide context-aware design guidance. Produces ux-spec.md (per screen/flow) or hud-design.md using the studio templates.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generates a new sprint plan or updates an existing one based on the current milestone, completed work, and available capacity. Pulls context from production documents and design backlogs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Holistic cross-GDD consistency and game design review. Reads all system GDDs simultaneously and checks for contradictions between them, stale references, ownership conflicts, formula incompatibilities, and game design theory violations (dominant strategies, economic imbalance, cognitive overload, pillar drift). Run after all MVP GDDs are written, before architecture begins.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fast-lane prototype skill for the hybrid workflow. Builds a playable prototype in 2-3 days with minimal process overhead. Designed for discovery phase.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guided, section-by-section GDD authoring for a single game system. Gathers context from existing docs, walks through each required section collaboratively, cross-references dependencies, and writes incrementally to file.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews a game design document for completeness, internal consistency, implementability, and adherence to project design standards. Run this before handing a design document to programmers.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Lightweight design spec for small changes — tuning adjustments, minor mechanics, balance tweaks. Skips full GDD authoring when a system GDD already exists or the change is too small to warrant one. Produces a Quick Design Spec that embeds directly into story files.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Generate design or architecture documents from existing implementation. Works backwards from code/prototypes to create missing planning docs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Decompose a game concept into individual systems, map dependencies, prioritize design order, and create the systems index.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
When a GDD is revised, scans all ADRs and the traceability index to identify which architectural decisions are now potentially stale. Produces a change impact report and guides the user through resolution.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guides writing, reviewing, and reasoning about modern Android UI code using Jetpack Compose. Covers best practices for state management, side effects, recomposition, navigation, Material 3 design, accessibility, and performance. Use when reading, writing, or reviewing any Jetpack Compose project.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before generating, editing, or reviewing any user interface — a dashboard panel, a landing page, an email, a slide, an app screen. Sets three deliberate design dials (variance, motion, density) BEFORE generation so the output has a point of view instead of defaulting to the timid, uniform look that reads as "AI made this". Applies to Genesis's OWN dashboard UI, not only things built for others.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Audits an existing rendered interface or frontend diff for hierarchy, content clarity, interaction states, accessibility, responsive behavior, visual consistency, performance-sensitive UI patterns, and anti-generic design defects. Use for a UI/UX review, redesign audit, screenshot review, pre-release visual check, or design-system consistency pass. Not for building a new interface from scratch or for backend-only review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs or reviews relational, document, key-value, graph, or search data models with ownership, invariants, access paths, migrations, consistency, retention, privacy, and recovery behavior. Use for schema changes, new data stores, indexes, migrations, persistence boundaries, or query-driven design. Not for a query-only bug without a model change or for API contract design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs, builds, or refactors user-facing web or application interfaces with deliberate visual direction, typography, color and spacing tokens, content hierarchy, responsive behavior, accessible interaction states, and real rendered-surface verification. Use for pages, components, dashboards, landing pages, design systems, and frontend polish. Not for backend logic, API-only work, or visual claims that cannot be rendered or inspected.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Designs or reviews HTTP, REST, GraphQL, RPC, CLI, webhook, event, and service interfaces with explicit inputs, outputs, errors, compatibility, idempotency, pagination, authentication, versioning, and observability. Use when introducing or changing an API or cross-component contract. Not for internal implementation details with no boundary or for debugging one API failure; use root-cause-debugging there.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Explores ambiguous product or engineering intent before implementation, clarifies users, constraints, alternatives, risks, and acceptance criteria, and turns the result into an approved design direction. Use for a new feature, subsystem, creative UI, architecture change, or unclear request. Not for an already-scoped bug fix, an existing implementation plan, or a narrow code review.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Web design reference for building production-grade interfaces. Covers layout, typography, color, spacing, shadows, animation, accessibility, responsive design, components, performance, and UX psychology. Use when building UI, reviewing design quality, choosing design tokens, or making any visual design decision.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create, redesign, repair, validate, preview, and package lightweight standalone HTML deliverables. Use for marketing experiences, product prototypes, infographics, motion narratives, documents, browser tools, dashboards, guided workflows, knowledge interfaces, mini-games, presentations, reusable style and brand systems, and local-model text, vision, image, or code tools that must run without a build chain or hosted service.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Figma from the shell via Flue - a plugin bridge to the Figma Plugin API without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Review design specification documents for Go programs before implementation begins. Use this skill when a user has a Go spec, design doc, RFC, or PRD to review, wants feedback on a planned feature in a Go codebase, is about to start implementing from a spec, or asks "is this spec ready?" or "review this before I build it". Applies Go philosophy — simplicity, composition, explicit errors, context propagation — plus Cobra/Viper CLI conventions where applicable.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Control Adobe InDesign from the shell via Flue - ExtendScript bridges without an MCP server.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.