디자인 스킬

Generate one Content-Derived Design direction from an HTML source, or let Auto choose the strongest direction. Use when the user says /reimagine-it generate, "redesign this page", "make it a landing page", "turn this into an infographic", names a token (all 17: webpage, infographic, svg, 3js, simulation, artistic, cinematic, dashboard, photography, landing, editorial, gradient, showcase, motion, glass, lookbook, particles), or wants a content-aware redesign instead of a mood board. CLI: npx reimagine-it --auto -i page.html -o out.html. Part of the reimagine-it Content-Derived Design suite.

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

Emit the content signals reimagine-it reads from an HTML file — title, anchors, proper nouns, dates, numbers, emails, links, source hex colors, and the derived palette — as JSON without generating a redesign. Use when the user says /reimagine-it extract, "what does the engine see in this page", "extract the palette", "pull the facts from this page", or wants content analysis for research, migration, or design-system work. CLI: npx reimagine-it extract -i page.html -o signals.json. Part of the reimagine-it Content-Derived Design suite.

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

Clear stored Woz credentials and log out.

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

WOZCODE utilities. Subcommands — login, logout, status, settings, update, share, review (deep multi-persona code review), benchmark (WOZCODE vs vanilla comparison). Invoke as `/woz <subcommand>`, e.g. `/woz login` or `/woz review`.

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

Deprecated alias — use `/woz logout`.

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

SwiftUI frontend visual design skill. Creates beautiful, distinctive iOS/macOS interfaces that avoid generic AI slop patterns. Covers design direction, layout systems, typography, color, spacing, brand integration, and design review. Use when designing new SwiftUI views, reviewing UI quality, creating iOS prototypes, choosing visual styles, improving app aesthetics, or when the UI looks generic or AI-generated.

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

Vaccine pipeline analysis: immunogenicity and seroconversion studies, lot-consistency trials, healthy-population efficacy designs, and age-cohort bridging, with the ACIP gate built into the value path across the med universe.

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

Device pipeline analysis: feasibility and pivotal study stages, design-iteration cycles, RWE studies, and post-market obligations, with reimbursement-aware value framing and decision-track awareness across the med universe.

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

Produce, direct, integrate, and quality-control ElevenLabs text-to-speech for narration, character performance, multilingual media, long-form voiceover, and streamed or batch AI-content audio. Use when selecting ElevenLabs models or voices; preparing spoken text; controlling pronunciation, pacing, emotion, and code-switching; using TTS APIs; cloning or designing a voice with consent; repairing artifacts; mastering deliverables; or evaluating generated speech. Excludes music, sound-effect generation, conversational-agent design, and general speech recognition except transcription used to verify TTS.

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

Design and produce raster images, native SVG artwork, brand-controlled visuals, and documented image edits with Recraft's API. Use for Recraft model and route selection, exact request construction, image-to-image, inpainting, outpainting, background work, vectorization, remix/exploration, palette and typography control, API migration, safety and rights review, and production QA.

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

Production guidance for authoring, integrating, and reviewing GSAP animation in browser-rendered media. Use for deterministic kinetic typography, SVG drawing and morphing, motion paths, FLIP transitions, responsive motion systems, or frame-seekable GSAP timelines inside HTML video composition and React-based renderers; not for ordinary CSS transitions or generic frontend development.

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

Provider-independent title design and kinetic typography direction for video, animation, ads, explainers, social hooks, brand films, lyric/text videos, title cards, main titles, lower thirds, captions-as-design, and other motion-led text. Use when an agent must plan, prompt, implement, hand off, iterate, or QA typography hierarchy, readability, timing, reveal/hold/exit, motion semantics, line breaks, safe areas, localization, brand constraints, accessibility, flashing/motion safety, or production specs for animated text.

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

Provider-independent production design direction for AI-generated media. Use when translating narrative, brand, advertising, product, social, film, or worldbuilding intent into sets, locations, props, color and material palettes, era research, graphic and environmental design, continuity bibles, image/video prompt planning, reference strategy, production constraints, iteration notes, handoff specs, and QA.

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

Provider-independent character design and continuity direction for generated media. Use when an agent must create, preserve, revise, or QA a recurring character across AI-generated images, video clips, avatars, animation, comics, ads, product mascots, serialized social posts, or multi-shot campaigns; especially when building character bibles, reference packs, prompts, expression/pose ranges, costume/hair/makeup/prop continuity, identity and likeness safeguards, iteration plans, handoff notes, or continuity reviews.

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

Provider-independent sound design and Foley direction for generated media. Use when an agent must plan, prompt, source, generate, edit, mix, hand off, repair, or QA sound effects, Foley, ambience, impacts, transitions, UI/product audio, emotional sound design, or accessibility-safe captions for videos, ads, trailers, animation, avatar clips, explainers, games/trailers, product films, and social edits.

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

Validate any Lattice SKILL.md against all tier conventions — atoms, molecules, and refiners. Catches structural errors, broken cross-references, and convention violations before they reach the repo. If you just wrote or modified a Lattice skill file and haven't run this yet, run it now — manual review consistently misses the same categories of errors this skill is specifically designed to catch. Use when the user says 'validate this skill', 'check this skill', 'does this follow conventions', 'review this skill file', 'check my SKILL.md', or 'skill validate'. Reports PASS/FAIL with specific file-and-section findings and actionable fixes. Standalone — does not call other skills.

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

Apply requirement quality principles when generating or validating feature specifications. Enforces feature completeness, scenario structure, AC verifiability, feature independence, and implementation slice quality. Use when writing feature specs, validating existing requirements, or when the user mentions 'validate this spec', 'check this feature', 'requirement quality', 'is this spec complete', or 'requirement-quality'. This skill governs the craft of writing individual feature specifications — not technical design (see design-blueprint), not implementation (see code-forge).

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

Generate structured feature specifications through a collaborative product interview. Acts as a senior PM and business analyst pair — arrives with a point of view, challenges scope, proposes options at every decision. Composes the requirement-quality atom for spec quality enforcement and collaborative-judgment for surfacing genuine decisions. Produces an epic/feature hierarchy in .lattice/requirements/ that serves as direct input to design-blueprint. Use when the user says 'forge requirements', 'write requirements', 'spec this feature', 'create a feature spec', 'define this epic', 'write a PRD', 'spec out what we are building', or 'requirement forge'.

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

Apply DDD tactical patterns when working with domain code, and validate proposed domain models before approval (design mode). Enforces aggregate design, value objects over primitives, entity identity rules, and bounded context boundaries. Use when creating or modifying domain models, designing aggregates, working in the domain layer, or when the user mentions 'domain', 'aggregate', 'value object', 'entity', 'bounded context', or 'DDD'.

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

Guide structured design thinking through 5 progressive levels before any code is written. Levels: Capabilities, Components, Interactions, Contracts, Implementation. Use when building new features, refactoring significant code, designing modules, or when the user says 'design this', 'architect this', 'let's think before coding', 'walk me through the design', or 'whiteboard this'. For simple utilities enter at Level 4 (Contracts), for single-component tasks at Level 2 — see Complexity Calibration. Do not use for quick bug patches.

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

Run a complete design workflow -- from establishing context through four progressive design levels (Capabilities, Components, Interactions, Contracts) to an approved blueprint. Composes knowledge-priming, context-anchoring, learning-harvest, collaborative-judgment, design-first, architecture, and domain-driven-design into one process. Handles both new features (create context doc) and resuming existing work (load context doc). Level 5 (Implementation) is delegated to code-forge. Use when starting a design, planning architecture, or when the user says 'design a feature', 'blueprint', 'start designing', 'plan the architecture', or 'let's design before coding'.

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

Facilitate a structured conversation to define DDD guardrails for domain design within a repository. Produces a formal ddd-principles.md document that the domain-driven-design atom will use as its override. Use when setting up domain design principles, defining aggregate rules, or when the user says 'setup DDD', 'define domain rules', 'DDD principles', or 'help me define my domain patterns'.

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

Manage per-feature living documents that capture decisions, constraints, and reasoning across AI sessions during active development. Scoped to feature-level work — design, implementation, bugfix, refactor — not for codebase-wide assessments or product-wide specifications (those define their own document lifecycles). Handles creating new context documents, loading existing ones, and enriching them with new decisions. Use when starting a new feature, resuming work, making technical decisions, resolving questions, or when context needs to persist across sessions. Use this skill whenever the user mentions 'load context', 'update context', 'context doc', 'decisions', 'continue where we left off', 'what did we decide', or 'capture this decision'.

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

Protocol for handling ambiguous decisions and missing/conflicting knowledge during code generation, design, and review. Ensures AI surfaces genuine judgment calls with structured options and stops on hallucination risk instead of silently assuming. Use when a decision has multiple valid approaches, when facts are missing or contradictory, when the user asks 'what should we do here?', 'is this a judgment call?', 'should I ask about this?', 'am I guessing here?', 'what are the tradeoffs?', or when deciding between two reasonable architectural or design options. Also composed by molecules to define how judgment calls and clarification requests are surfaced and resolved.

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