Confluence page CRUD via confluence-as: create/show/update/delete, hierarchy, copy. NOT bulk (mk:confluence-bulk), spec analysis (mk:confluence-spec-analyst), or comments (mk:confluence-collaborate).
The English summary is being prepared. Showing the original description.
Generate publish-grade SVG+PNG technical diagrams — architecture, data flow, flowchart, sequence, agent-memory, class, ER, state-machine, comparison, timeline, and more — across 8 visual styles. Writes output to tasks/visuals/ or an active plan's visuals/ directory. Requires rsvg-convert (librsvg) for PNG export; degrades gracefully to SVG-only when absent.
The English summary is being prepared. Showing the original description.
Use when writing tests, running validation scripts, or (in TDD mode) enforcing red-green-refactor cycle. Activates during Phase 2 (Test) and Phase 3 (Build). NOT for coverage gap mapping (see mk:nyquist); NOT for sprint contract negotiation (see mk:sprint-contract).
The English summary is being prepared. Showing the original description.
Use when analyzing harness trace logs to surface recurring failure patterns and suggest harness improvements. Scatter-gather pattern across last N runs with mandatory HITL gate before any change is applied. Triggers on /mk:trace-analyze, "analyze traces", "find patterns in harness runs", or after a model upgrade flagged dead-weight-audit-needed.
The English summary is being prepared. Showing the original description.
Use when writing, reviewing, or refactoring Vue 3 code — components, composables, reactivity, Pinia state, Pinia Colada data-fetching, file-based routing, and forms. Targets Composition API + <script setup> + TypeScript. Auto-activates on .vue files. For deep best-practices review/recommendations or the full ordered workflow (built-in components, animations, performance pass), use mk:vue-best-practices.
The English summary is being prepared. Showing the original description.
Use for Vue 3 testing best-practices review and recommendations — designing and auditing Vitest + Vue Test Utils tests for components, composables, Pinia stores, Vue Router, async/Suspense, Teleport, forms, and accessibility, plus Playwright E2E test-design strategy. Advisory/review only — recommends patterns and flags test smells; does not run tests. Complements mk:vue-best-practices (feature code). Invoke for "review my Vue tests", "how should I test this component/composable/store", or "Vue test best practices".
The English summary is being prepared. Showing the original description.
Answer factual project questions (codebase, architecture) with cited evidence. NOT for brainstorming, trade-offs (mk:party), debugging (mk:investigate), review (mk:review), or plans (mk:plan-creator).
The English summary is being prepared. Showing the original description.
Use for deep Vue 3 best-practices review, recommendations, and the full ordered authoring workflow — built-in components (Teleport, Suspense, KeepAlive, Transition, TransitionGroup), animation techniques, slots, fallthrough attrs, custom directives, async components, render functions, plugins, and the post-functionality performance pass. Complements mk:vue (the everyday Composition API quick-reference). Invoke for "review my Vue", "Vue best practices", "recommend improvements", or non-trivial feature work needing the ordered workflow.
The English summary is being prepared. Showing the original description.
Use when designing UI components, creating design systems, reviewing visual design, or checking accessibility compliance. Triggers on "design system", "UI review", "color palette", "font pairing", "accessibility audit", "responsive design", "WCAG check". Auto-activates when ui-ux-designer agent is working. Data-driven: 160 palettes, 73 font pairings, 161 product types, 98 UX guidelines, 25 chart types.
The English summary is being prepared. Showing the original description.
Ship workflow with explicit scopes: prepare stages and commits locally; release pushes and creates a PR; publish manages issues and versioning. Use when asked to "ship", "deploy", "push to main", "create a PR", or "merge and push". Proactively suggest when the user says code is ready or asks about deploying. Supports official (→ main) and beta (→ dev/develop) ship modes with auto-detection.
The English summary is being prepared. Showing the original description.
Create a self-contained, visually polished HTML showcase page for a topic or set of artifacts. Supply a mission (topic summary) and optional artifact paths explicitly — the skill never auto-scans the repo. Writes output to assets/showcase/<mission>/. Screenshots are optional (requires Puppeteer). Publishing is local-only by default; publish requests without a configured path fail clearly.
The English summary is being prepared. Showing the original description.
Session-scoped guardrails warning before rm -rf, DROP TABLE, force-push, git reset --hard, kubectl delete, etc; user can override. NOT for scoping edits to a directory (mk:freeze).
The English summary is being prepared. Showing the original description.
Generate or compare multiple technical approaches for one validated decision. NOT for product discovery or refining an existing plan.
The English summary is being prepared. Showing the original description.
Bootstraps a new project end to end: research, design, plan, scaffold, implement, docs. Explicit invocation only. NOT for autonomous builds (mk:autobuild); NOT for existing-repo work (mk:cook).
The English summary is being prepared. Showing the original description.
Experimental/manual harness canary procedure. It records benchmark manifests and scores but does not provide a fully automated runner.
The English summary is being prepared. Showing the original description.
Runs autonomous multi-hour green-field builds: planner, contract, generator/evaluator loop, scaffolding density per model tier. NOT for scoped tasks (mk:cook); NOT for scaffolding only (mk:bootstrap).
The English summary is being prepared. Showing the original description.
Use when creating files and need the correct path, organizing project layout, or enforcing naming conventions. Two modes: advisory (return path) and organize (restructure).
The English summary is being prepared. Showing the original description.
Multi-agent collaboration session. Brings 2-4 agent perspectives into one discussion for architecture decisions and trade-off analysis. Use when asked "should we X or Y?", "let's discuss", or "design review".
The English summary is being prepared. Showing the original description.
Manage JIRA collaboration surface via the jira-as wrapper: comments, attachments, watchers, notify. Triggers: 'comment on KEY', 'add attachment to KEY', 'watch KEY', 'notify KEY watchers'. Internal-vs-public comment safety enforced. NOT for issue CRUD (mk:jira-issue); NOT for issue links (mk:jira-relationships).
The English summary is being prepared. Showing the original description.
Create inline Mermaid v11 diagram blocks — flowcharts, sequence, class, ER, Gantt, state, timeline, user-journey, and 20+ other types — rendered in markdown files and browser environments. Zero external dependencies; mmdc is optional for CLI export.
The English summary is being prepared. Showing the original description.
YC Office Hours — product validation for a new product, feature, or side-project concept. Startup mode tests demand; Builder mode develops an unvalidated product idea. Use when the user asks whether something is worth building or has an idea whose problem/value is not yet validated. Proactively suggest when the user describes a new product idea or is exploring whether something is worth building — before any code is written. Use BEFORE a plan exists. For reviewing an existing plan, use /mk:plan-ceo-review.
The English summary is being prepared. Showing the original description.
Use when stuck on approach (not debugging). Strategic unsticking via 7 non-default techniques: simplification cascades, collision-zone thinking, meta-pattern recognition, inversion, scale game, first principles, via negativa. Triggers on complexity spiraling, innovation block, recurring patterns across domains, forced-assumption solutions, scale uncertainty, told-it's-impossible, or bloated systems needing subtraction. For evidence-based root-cause debugging, use mk:sequential-thinking instead.
The English summary is being prepared. Showing the original description.
JIRA-side cache + project-context discovery via the jira-as wrapper. Triggers: 'jira cache status', 'clear jira cache', 'discover project context for PROJ'. Diagnostic-only — no Atlassian state changes. NOT for issue CRUD; NOT for project admin (mk:jira-admin).
The English summary is being prepared. Showing the original description.
Bulk JIRA operations on 10+ issues via the jira-as wrapper: bulk transition / assign / set-priority / clone / delete. Dry-run is MANDATORY first. Triggers: 'bulk update N issues', 'mass transition', 'transition 50+ issues to Done', 'bulk-clone', 'bulk-delete'. NOT for single-issue ops (mk:jira-issue / mk:jira-lifecycle).
The English summary is being prepared. Showing the original description.
Is this your account? Link GitHub to bring it onto your creator page (Japanese)