CodeMachine0121

Convert an existing Figma changelog into structured JSON format. Use when the user mentions "convert changelog", "import changelog", "migrate changelog", or provides a Figma link to an existing changelog they want converted to the standard JSON format.

Generate a new changelog for a component or design system file. Creates the changelog template and populates it with the first entry. Use when the user mentions "create changelog", "new changelog", "start changelog", or wants to begin tracking changes for a component.

Add new entries directly to an existing changelog in Figma using MCP tools. No JSON copy-paste needed. Use when the user mentions "update changelog", "add to changelog", "changelog entry", "log this change", or wants to add a new entry to an existing changelog.

Generate a visual property annotation in Figma showing each configurable property axis with component instance previews. Use when the user mentions "property", "properties", "property annotation", "create property", or wants to document a component's configurable properties visually.

Generate component anatomy spec in Figma — numbered markers and attribute table for UI components. Use when user asks for anatomy, component anatomy, or create anatomy.

Generate API overview specification in Figma — component properties, values, defaults, and configuration examples. Use when user asks for api, props, properties, or component api.

Generate color annotation specification in Figma — design token mapping for every element and state. Use when user asks for color, color annotation, or tokens.

Generate motion specification in Figma from After Effects export data. Use when user asks for motion, motion spec, animation spec, or timeline.

Verify an implementation conforms to its contract — the feature's PRD.md (preferred; its Gherkin acceptance-criteria scenarios) or BRIEF.md — using the Acceptance Criteria as the oracle. For each clause, first derive the expected outcome from the spec alone, then judge independently whether the test asserts that outcome and whether the production code produces it. Emits a Traceability Matrix with a per-clause conformance verdict; flags gaps, mis-asserted/shallow tests, behavior violations, and orphans. Never edits source code. Triggered by: "contract", "trace contract", "verify contract", "/contract".

Two modes: (1) FEATURE — conduct a requirements interview and generate a business-language PRD under .sdd/, turning the brief's requirement examples into Gherkin acceptance criteria; (2) PROJECT — analyze UL-MAP.md and project architecture to produce or update .sdd/PROJECT.md (vision, tech stack, conventions). Triggered by: "prd", "write a PRD", "feature spec", "product requirement", "/prd", "/prd project", "project overview", "project map".

Turn a feature's BRIEF.md and/or PRD.md into a single self-contained HTML page that visualizes the plan — goal, scope, personas, user stories, business flow, acceptance criteria (as Gherkin scenarios), and risks — using diagrams and charts so developers can see what is being built at a glance. Never edits source code. Triggered by: "visionize", "visualize the plan", "/visionize".

Drive implementation via TDD against a feature's PRD.md (acceptance criteria) and ARCH.md (the technical design). Extracts test cases from the PRD scenarios, runs red-green-refactor per case, and commits every cycle. Tests verify behavior only. Triggered by: "tdd", "implement with tdd", "/tdd".

Phase between PRD and TDD. Reads a feature's PRD.md and designs the technical approach — the change scope and the new classes/modules with their responsibilities — from the perspective of the next engineer who has to extend it, so future requirements land with minimal load. Outputs ARCH.md. Never edits source code. Triggered by: "architecture", "arch", "design architecture", "/architecture", "/arch".

Reach 100% intent consensus with the user, pin the intent down with concrete examples that cover boundaries and exceptions, then compile a requirements brief written purely in business language for handoff to PRD. Never edits source code. Triggered by: "clarify", "/clarify".

Improve the design quality of an existing codebase by identifying fragmented logic and consolidating it into deep modules — simple interfaces hiding complex internals. Triggered by: "improve codebase", "deep module", "/improve-codebase".

Manage a Ubiquitous Language Map — bridges business terms, code names, and UI labels within a Bounded Context. Use when: initializing a new UL map, or updating/reconciling an existing one. Triggered by: "ubiquitous language", "UL map", "domain glossary", "/ul-init", "/ul-update".

Use when designing or reviewing .NET Core project architecture, layer responsibilities, dependency direction, type boundaries, error handling strategy, or placement of cross-cutting concerns such as middleware and action filters.

Use when implementing or reviewing EF Core usage in .NET Core projects. Covers DbContext setup, Repository implementation, Unit of Work pattern, query optimization, migration management, and common pitfalls.

Use when refactoring .NET Core code, reviewing architecture, or checking if code follows James's style in C# projects. Triggers on: private methods, God Class, DI lifetime issues, impure service layer, mutable variables, scattered model conversions, if/switch branch implementations.

Use when writing or reviewing unit tests in .NET Core C# projects. Applies to test structure, naming, mocking, assertions, and framework setup using TUnit, NSubstitute, and FluentAssertions.

Apply Kent Beck's "Tidy First?" methodology before implementing features or fixes. Use when: (1) about to change code and the structure feels messy, (2) asked to refactor or clean up code, (3) a PR mixes structural and behavioral changes, (4) code is hard to read or understand. Guides developer through separating structural tidyings from behavioral changes, and sequencing them correctly.

Turn a confirmed Design Brief + UI Spec into an actual design. Implementation stage: reads the feature's UI-SPEC.md (the UI design and whatever visual values it committed to, resolved from the design guideline) and DESIGN-BRIEF.md (the acceptance-criteria scenarios), plus UL-MAP.md / DESIGN-FOUNDATIONS.md, then builds real screens and interactions via one of two targets: Figma (through the connected Figma MCP) or self-contained HTML+CSS files. Honors every value the spec fixed; for visual details the spec deliberately left open, commits sensible choices at build time (consistent with the guideline / foundations) and lists them — without re-asking for a design guideline. Verifies every acceptance-criteria scenario in the brief is realized. Triggered by: "design-build", "build the design", "生成設計", "實作設計", "/design-build".

Manage a Ubiquitous Language Map for design — the single shared vocabulary that bridges the user's/domain term, the component or pattern name, the user-facing UI label, and the design token, within one product area. Optional and best run *after* ui-spec has settled the screens, components, labels, and visual values — to capture the vocabulary the design actually landed on — then kept in sync as later features and design-build introduce new components, labels, and states. Recommended when the vocabulary will be reused across features; skippable for a one-off. Use when: initializing a new map, or updating/reconciling an existing one. Triggered by: "ubiquitous language", "UL map", "設計語言", "共用語言", "design glossary", "/ul-init", "/ul-update".

Two modes: (1) FEATURE — take a confirmed Design Brief and work out the full UI design with the user: for each screen, which elements exist (buttons, inputs, lists, content blocks), their positions and hierarchy, the states (default/empty/loading/error/success), the interactions, and the visual/UI details that matter for the feature — resolved against the user's design guideline where one exists. This is where the UI is actually decided, so it is free to commit to concrete visual values (color usage, sizing, spacing, radius, type, borders) whenever they are what the discussion is about; it asks the UI questions the feature calls for rather than a fixed checklist. Generates a UI-SPEC.md focused purely on UI concerns. It contains NO scenarios and NO Given/When/Then — acceptance criteria live solely in the Design Brief; ui-spec only references them for coverage. (2) FOUNDATIONS — analyze UL-MAP.md and existing design to produce or update .sdd/DESIGN-FOUNDATIONS.md (layout system, component inventory, interaction

Reach 100% intent consensus with the user on a design problem — the user's intent, the underlying need, the target UX experience, and the end-to-end user flow — then pin it down with concrete flow scenarios that cover the happy path, boundaries, and exceptions. These scenarios double as the feature's acceptance criteria — this brief is the single home for all requirement examples and AC; downstream skills consume them, never restate them. Compile a Design Brief written purely in user/experience language for handoff to ui-spec. Produces no design artifacts and edits no files other than the brief. Triggered by: "ux-spec", "探討需求", "設計探索", "UX 探索", "/ux-spec".

Event Storming 引導專家，透過互動式問答帶領使用者完成 Event Storming 工作坊，識別 Domain Events、Commands、Actors、Aggregates、Policies、External Systems、Read Models 等 DDD 元素，最終生成結構化 Markdown 文件到 ddd-docs/ 目錄。當用戶提到 Event Storming、事件風暴、業務流程探索、領域事件分析，或想了解系統中會發生哪些事件時使用。通常作為 strategic-design 的前置步驟。

DDD 戰略設計專家，引導使用者完成 Bounded Context 識別、Aggregate 切分、Entity/Value Object 設計與通用語言建立，最終生成結構化 Markdown 設計文件到 ddd-docs/ 目錄。當用戶提到 DDD 設計、Bounded Context、領域建模、Aggregate 設計、子領域劃分，或想從業務分析轉為系統設計時使用。通常在 event-storming 工作坊之後使用，或作為獨立的 DDD 設計流程。

在 AI 時代誠實地自評「我這個 sprint 的交付成效」。不是產出量打分，而是用對 AI 免疫的流動/品質指標當溫度計、用判斷日誌當北極星。Use when the user says "sprint 自評", "我這 sprint 做得如何", "我的交付成效", "sprint self review", "個人交付量", or invokes /sprint-self-review.

Generate a professional software engineer resume/CV. Produces a polished, ATS-optimized resume with professional summary, technical skills, quantifiable achievements, and professional attributes. Use when user asks to "generate resume", "write CV", "build resume", "create resume", "產出履歷", or "寫履歷".