디자인 스킬

Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design systems, services, and architectures. Trigger with "design a system for", "how should we architect", "system design for", "what's the right architecture for", or when the user needs help with API design, data modeling, or service boundaries.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TRIGGER THIS when designing employee engagement surveys, analyzing employee feedback, creating action plans based on survey results, tracking engagement trends, planning pulse surveys, or improving employee experience. Designs comprehensive surveys that measure engagement, belonging, and satisfaction with actionable insights and accountability-driven improvement plans.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

ACTIVATE when developing long-term strategy, setting OKRs, creating vision statements, building SWOT analyses, designing strategic frameworks, defining company direction, planning multi-year initiatives, or aligning organizational strategy with business goals. Executive must think through market positioning, competitive advantage, and measurable strategic objectives.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create beautiful visual art in .png and .pdf documents using design philosophy. You should use this skill when the user asks to create a poster, piece of art, design, or other static piece. Create original visual designs, never copying existing artists' work to avoid copyright violations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

TRIGGER THIS when preparing for new hires, planning first-day/week/month activities, creating onboarding schedules, building 30-60-90 day plans, designing welcome programs, organizing training schedules, or setting up buddy/mentorship programs. Designs comprehensive, engaging onboarding experiences that accelerate time-to-productivity and build belonging.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when choosing, comparing, or implementing UX patterns across the UX Patterns for Developers corpus.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user's task involves Ant Design (antd) — writing antd components, debugging antd issues, querying antd APIs/props/tokens/demos, migrating between antd versions, or analyzing antd usage in a project. Triggers on antd-related code, imports from 'antd', or explicit antd questions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Define production-ready visual intent for Blender scenes and standalone assets, including focal hierarchy, depth layers, visual flow, scale and repetition rhythm, camera mobility, representation fidelity, and performance budgets. Use for original or reference-guided Blender work before construction choices are executed, especially environments, architecture, products, hero assets, or scenes whose modeling quality depends on coordinated spatial design rather than isolated objects.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Orchestrate production-grade Blender work by probing the installed Blender version, retrieving relevant official Blender documentation, assigning visual design intent, classifying shape grammar and geometry/deformation/procedural/physics/shading needs, comparing direct Blender components with node systems, creating staged artifacts, and routing to specialist skills. Use for every non-trivial Blender creation, reconstruction, simulation, animation, environment, or scene-modification request, especially when the user does not know whether to use topology, Boolean, Array, curves, snapping, Displace, simulation, Geometry Nodes, or shading.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Verify code correctness statically against specifications using type checking, contract verification, and formal methods. Use when: (1) Verifying type safety and null safety in Python, Java, or C/C++ code, (2) Checking design-by-contract specifications (preconditions, postconditions, invariants), (3) Validating code against formal specifications, (4) Ensuring code quality and correctness before runtime, (5) Finding potential bugs through static analysis. Supports Python (mypy, contracts), Java (javac, JML), and provides verification scripts and contract specification guidelines.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Generate formal specifications including preconditions, postconditions, invariants, and contracts from code or requirements. Use this skill when documenting APIs, creating formal verification annotations, defining function contracts, specifying class invariants, writing design-by-contract code, or preparing code for formal verification. Supports multiple specification languages including JML, ACSL, Dafny, Eiffel contracts, and documentation annotations.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Check behavioral consistency between high-level hardware specifications and RTL implementations. Use when asked to check RTL consistency, verify RTL against spec, check hardware specification compliance, validate RTL implementation, find spec violations in RTL, check behavioral consistency, or when working with hardware designs that need verification against protocol specifications, timing requirements, or functional specifications in Verilog, VHDL, or SystemVerilog.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Automatically infer formal correctness properties from Verilog/SystemVerilog RTL code and generate SystemVerilog Assertions (SVA). Identifies control-flow invariants (mutual exclusion, valid-ready handshakes, pipeline ordering, safety properties), liveness expectations, and temporal properties. Use when working with RTL designs that need formal property generation, when adding assertions to existing RTL, or when users ask to infer properties, generate assertions, or create formal specifications from hardware designs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Iteratively enhance user requirements into clear, complete, actionable specifications through analysis and clarification. Use when: (1) Users provide initial requirements that need refinement, (2) Requirements are vague, incomplete, or ambiguous, (3) Creating formal specifications from informal descriptions, (4) Identifying missing constraints, edge cases, or acceptance criteria, (5) Clarifying assumptions and implicit dependencies, or (6) Preparing requirements for design, implementation, or verification. Operates interactively: analyze → ask clarifying questions → refine based on responses.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Designer-turned-developer who crafts stunning UI/UX even without design mockups. Use for any frontend implementation requiring visual design decisions, aesthetic direction, or pixel-perfect UI work.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Identify design quality issues in code including high coupling, low cohesion, God classes, long methods, and other code smells. Use when: (1) Reviewing code architecture and design quality, (2) Identifying refactoring opportunities, (3) Detecting God classes or classes with too many responsibilities, (4) Finding high coupling or low cohesion issues, (5) Analyzing code maintainability and technical debt. Detects coupling smells, cohesion problems, complexity issues, size violations, and encapsulation problems with actionable refactoring suggestions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Recommends appropriate software design patterns based on problem descriptions, requirements, or code scenarios. Use when designing software architecture, refactoring code, solving common design problems, or choosing between design approaches. Analyzes the problem context and suggests suitable creational, structural, behavioral, architectural, or concurrency patterns with implementation guidance and trade-off analysis.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Design and review APIs with suggestions for endpoints, parameters, return types, and best practices. Use when designing new APIs from requirements, reviewing existing API designs, generating API documentation, or getting implementation guidance. Supports REST APIs with focus on endpoint structure, request/response schemas, authentication, pagination, filtering, versioning, and OpenAPI specifications. Triggers when users ask to design, review, document, or improve APIs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Plan game UX, UI, and HUD design specifications. Use when the user says "lets create game UX", "design the HUD", "create UI specifications", or "help me plan the game UX"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, update, validate, or analyze a game project's PRD. Use when the user wants help producing, editing, validating, or analyzing a PRD — often derived from a GDD or prepared for external-tool integration.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create, update, or validate a game's Game Design Document. Use when the user wants help producing, editing, or validating a GDD — the primary design artifact covering pillars, mechanics, progression, levels, art, audio, and development epics.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Create comprehensive narrative documentation with story structure and world-building. Use when the user says "narrative design" or "create narrative"

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.