デザインのスキル

Enter explore mode for technical work — a thinking partner for {{engine_name}} code, architecture, and implementation decisions before you write any code. Use it to investigate a technical solution, design the architecture of a feature, choose between frameworks or libraries, compare implementation approaches, analyze how existing code or a system works, or deeply root-cause a complex bug without fixing it yet. The ultra mode adds adaptive artifacts (a C4 view, ADRs, a dependency graph) to the research folder — run it on "ultra research", "ultra explore" or "ultraresearch"; otherwise run the default. Trigger on "let's explore this technical solution", "how should we architect this feature", "which framework should we use", "run an ultra research on the save system", "investigate this error deeply". Research and analysis only — it never writes code. This is the CODE / engineering explorer — for GAME-DESIGN, GDD, mechanics, or balance research (no code) use /unikit-gd-explore.

日本語の概要は準備中です。原文の説明を表示しています。

Ideate a brand-new game concept with the user, from a blank page or a one-line hint to a finished CONCEPT card. Use it whenever the user wants to come up with a new game — whether the project has no design document yet, or already has one and they're exploring a fresh idea. Through a structured divergence/convergence dialogue it explores ideas, frames the hook, generates and scores concepts (market validation delegated to /unikit-gd-explore), and settles pillars, loops, motivation, and a pre-mortem. Trigger whenever the user wants to make or invent a game, doesn't know where to start, or gives a genre/theme hint, e.g. "let's come up with a game", "I don't know what game to make", "I want to make a roguelike", "a game about zombies", "a farming game", "help me come up with a concept". For researching or dissecting existing games use /unikit-gd-explore; to write an already-chosen concept as the master GDD use /unikit-gd-spec.

日本語の概要は準備中です。原文の説明を表示しています。

Dispatch an explicit, user-dictated set of edits that spans TWO OR MORE zones of the GDD — the master spec, systems, content types, and flows — in one ordered pass. Writes nothing itself: it resolves each delta to its (target, zone), orders them so a system change lands before the content or flow that depends on it, delegates each to the owning skill (/unikit-gd-spec, /unikit-gd-system, /unikit-gd-content, /unikit-gd-flow), and closes with one /unikit-gd-verify pass. Use when you already know the changes and they touch more than one part of the design, e.g. "apply these GDD changes", "update the combat system and its loot and the boss flow". It also takes a /unikit-gd-review report file (applies its apply-ready bucket), and a bare /unikit-gd-apply reads the last /unikit-gd-verify output in the session. For a single-zone change call its owner directly; to research an open question use /unikit-gd-explore first.

日本語の概要は準備中です。原文の説明を表示しています。

Create and own the master game design document (GAME.md — the authored one-pager plus the generated [gen] system/flow maps) and the GD-IDS.yaml facts registry — the top-level, big-picture layer of the GDD and the machine interface the code side reads. Use it to write the master spec from a concept or dialogue, import an existing GDD (a file path or URL), edit GAME.md content ("change a pillar", "rework the monetization stance", "tweak the loop stack"), pitch the game ("pitch" → PITCH.md), re-decompose the systems ("remap"), and — importantly — to add a new system to the design map ("let's add a new system", "add a crafting system to the game design", "add this to the GDD"). This is the structural, map-level layer plus GAME.md content edits. To write or fill in the detailed parameters of one existing system, use /unikit-gd-system; to apply one edit spanning several zones at once use /unikit-gd-apply; to invent a brand-new game concept use /unikit-gd-brainstorm.

日本語の概要は準備中です。原文の説明を表示しています。

Render the GAME-DESIGN document (the GDD) into a human-readable form — read-only Markdown chapters under docs/design/ (index, systems, flows, content, economy, glossary), with facts resolved inline from GD-IDS.yaml and drafts flagged 🚧. Optional --web also renders an HTML site from the unikit-docs template (falls back to Markdown-only if the template is absent). Use to export or publish the design for people to read, e.g. "render the GDD", "export the game design to docs", "generate readable design docs", "publish the GDD", "make a design doc site". Read-only — it never edits the GDD or registry, only renders it. This renders the game DESIGN — for the project's CODE documentation (README, docs/*, modules, architecture) use /unikit-docs.

日本語の概要は準備中です。原文の説明を表示しています。

Author and own one flow's design document (the FLOW.md objective flow) at .unikit/gamedesign/flows/FLOW-<slug>.md — the dynamics layer of the GDD (what the player does over time). Create the skeleton and walk the collaborative section-cycle to write its objectives, pacing, dependencies, and funnel events ("design the first-session flow", "map the onboarding sequence", "write the FLOW for the boss encounter"), AND revise it after approval under the delta discipline ("retune the pacing", "add a branch", "change a GOAL", "rework the onboarding") — a cue/number change is Tuning, a small step change a Tweak, restructuring a Rework; each bumps the version and logs the delta. Selects the wiring mode (linear | conditional | emergent) and re-renders the ## Flow Map [gen] / ## Funnel [gen] blocks in GAME.md. To add or detail a system use /unikit-gd-system; to edit GAME.md content use /unikit-gd-spec; to apply a multi-zone edit use /unikit-gd-apply; for a new game concept use /unikit-gd-brainstorm.

日本語の概要は準備中です。原文の説明を表示しています。

Research and ideation partner for GAME DESIGN — think through design ideas before writing them into the GDD; produces a brief, never edits the GDD itself. Use to assess a genre or market for viability, dissect a reference game (mechanics → dynamics → aesthetics), explore how to improve or extend an existing system, flow, or content type, research new mechanics the design lacks, investigate a part of the GDD in code, or develop the research bucket of a /unikit-gd-review report into decided edits. Trigger on "explore how to improve the flow", "ways to improve the combat system", "is this genre saturated", "break down the combat of Hades", "work out the review's open questions". GAME-DESIGN research only — for CODE or technical research use /unikit-explore; to reconstruct a design from code use /unikit-gd-recon; to write a change into the GDD use /unikit-gd-system or /unikit-gd-spec; to apply edits you know use /unikit-gd-apply; to invent a new game use /unikit-gd-brainstorm.

日本語の概要は準備中です。原文の説明を表示しています。

Generate and maintain the project's TECHNICAL documentation from its codebase — scans the project structure, tech stack, and module boundaries, then writes a lean README landing page plus detailed topic pages (architecture, modules, setup, build, APIs), only the docs that are relevant. Use whenever the user wants to create, update, or validate documentation of the CODE or the project itself, e.g. "generate documentation", "create docs", "write the README", "update the project docs", "document the codebase", "document this project's architecture", "validate the project documentation". This is CODE / project documentation only — it never documents the game design. To render the GAME DESIGN (the GDD: systems, flows, content, economy) for people to read use /unikit-gd-docs.

日本語の概要は準備中です。原文の説明を表示しています。

Mechanical consistency check for game design — answers "is the design consistent with itself?" — plus changed-scope impact analysis across all three GDD axes: systems, flows, and content types. Offline and deterministic: greps the facts registry against the documents (numbers, terms, IDs, duplicate & dangling references, roster↔disk, map freshness, Depends 3-way, status/version, AC presence, placeholder leaks, flow & content schema), and from a git diff computes which dependent systems, flows, and content a change affects. Scope is inferred: a named document checks that document; an unverified diff triggers a changed-scope pass; otherwise everything. Use when the user wants a consistency or impact check, e.g. "verify the design", "what did this change affect", "find broken references in the design". Conflicts triage into four tracks; the entailed fixes hand off to /unikit-gd-apply in one pass. This is the mechanical pass — for a subjective "is this design good" quality critique use /unikit-gd-review.

日本語の概要は準備中です。原文の説明を表示しています。

ฟลอริสต์มืออาชีพ — flower arrangement, design brief, occasion-based (wedding, funeral, birthday), color theory, flower meaning

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบ slide ระดับมืออาชีพ — pitch deck (Guy Kawasaki 10-slide), exec summary, visual hierarchy

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบภายใน — functional layout, furniture spec, lighting plan, material palette, mood board พร้อม render prompt

日本語の概要は準備中です。原文の説明を表示しています。

Logo Designer — brand identity, logo system (mark + wordmark), usage guide, rebrand, color mode (CMYK/RGB/Pantone), file format spec

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง storyboard + edit plan + sound cue + color grading plan สำหรับงานตัดวิดีโอ

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง Midjourney/DALL-E prompt คุณภาพสูง + design brief สำหรับโลโก้ โปสเตอร์ อินโฟกราฟิก โซเชียลมีเดีย

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง concept design + mood board + Midjourney render prompt + material spec สำหรับงานสถาปัตยกรรม

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบ UX ตั้งแต่ discovery, IA, user flow, wireframe, prototype จนถึง usability test สำหรับเว็บและแอป

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง collection plan + mood board + pattern brief + fabric spec สำหรับแบรนด์แฟชั่น

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง product brief + packaging design + mockup prompt + spec สำหรับสินค้าและบรรจุภัณฑ์

日本語の概要は準備中です。原文の説明を表示しています。

Packaging Designer — บรรจุภัณฑ์ box/bottle/label, dieline, material selection, print spec, shelf impact, CMYK/RGB color management

日本語の概要は準備中です。原文の説明を表示しています。

สร้าง shot list + mood board + retouching plan + Lightroom preset recipe สำหรับงานถ่ายภาพ

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบเครื่องประดับ — ring, necklace, earring + gem (cut/clarity/color), metal selection พร้อม render prompt

日本語の概要は準備中です。原文の説明を表示しています。

ออกแบบ animation, motion brief, AfterEffects spec, Lottie export สำหรับ UI, logo reveal, explainer video

日本語の概要は準備中です。原文の説明を表示しています。

นักเขียนอักษรประดิษฐ์ — Thai + Latin calligraphy, hand lettering, signage, wedding invitation, lettering artwork

日本語の概要は準備中です。原文の説明を表示しています。