React/Next.js authoring, review, and optimization: components, routes, bundle size, re-renders, performance. Auto-activates on .tsx/.jsx files alongside mk:typescript in React projects.
日本語の概要は準備中です。原文の説明を表示しています。
1.5万 件 ・ 関連度順
概要と使いどころ
React/Next.js authoring, review, and optimization: components, routes, bundle size, re-renders, performance. Auto-activates on .tsx/.jsx files alongside mk:typescript in React projects.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-agent collaboration bringing 2-4 perspectives into one discussion for architecture decisions and trade-off analysis. Use for 'should we X or Y', design review, or debate before deciding.
日本語の概要は準備中です。原文の説明を表示しています。
Deep Vue 3 best-practices review and authoring workflow: built-in components (Teleport, Suspense, KeepAlive, Transition), animations, slots, directives, render fns, perf pass. Complements mk:vue.
日本語の概要は準備中です。原文の説明を表示しています。
Render a plan directory (plan.md + phase-*.md) as a visual: generates/validates visual-plan/plan.json, opens a studio to view/edit, exports plan.html. Pass --static for a legacy single-file render.
日本語の概要は準備中です。原文の説明を表示しています。
Vue 3 testing best-practices review: Vitest + Vue Test Utils for components, composables, Pinia, Router, async/Suspense, forms, a11y, plus Playwright E2E strategy. Advisory only.
日本語の概要は準備中です。原文の説明を表示しています。
Loads, lists, composes, or validates graded evaluation rubrics: PASS/WARN/FAIL grading with weighted criteria and balanced anchor examples for evaluator-style review.
日本語の概要は準備中です。原文の説明を表示しています。
Design UI components/design systems, review visual design, check accessibility. Triggers: design system, color palette, font pairing, WCAG check. Data-driven: palettes, fonts, UX guidelines.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow navigator: scans project state (plans, reviews, tests, git) and recommends the next pipeline step. Use for 'what next?' or 'where am I?'. NOT for complexity routing (mk:scale-routing).
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan, one question at a time, until shared understanding. Checkpoints answers so progress survives a reset. Do NOT use to propose solutions.
日本語の概要は準備中です。原文の説明を表示しています。
Single-task pipeline: plan → test → build → review (ship separately). Use for a feature or scoped fix. NOT for green-field builds (mk:autobuild) or auto-orchestration (mk:workflow-orchestrator).
日本語の概要は準備中です。原文の説明を表示しています。
JSON-canonical session memory in .meowkit/memory (Markdown is a generated view). Capture learnings, patterns, costs; loads at Orient, persists at Reflect. NOT for retrospectives (mk:retro).
日本語の概要は準備中です。原文の説明を表示しています。
Design and review durable REST, GraphQL, RPC, or event API contracts: shape, compatibility, pagination, error semantics. Discovers existing consumers first. Not implementation, schema, or release.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a raw idea into ONE honest recommendation: interview one question at a time until confirmed, then give a verdict with trade-offs and a checklist. Not for options or debate.
日本語の概要は準備中です。原文の説明を表示しています。
Advanced vulnerability analysis principles. OWASP Top 10 baseline + current threat landscape awareness, Supply Chain Security, attack surface mapping, risk prioritization. Use when performing security audits, threat modeling, or OWASP reviews. NOT for STRIDE/CSO-mode infrastructure audits (see mk:cso).
日本語の概要は準備中です。原文の説明を表示しています。
Use when refining a draft user prompt before sending it to a coding agent. Decomposes goal/context/constraints/acceptance/output-format, detects ambiguity and model-coupled framing, then emits a model-agnostic rewrite. Supports --analyze, --score, and --deep. NOT for prompts from scratch (mk:brainstorming), plans/reviews (mk:elicit), implementation plans (mk:plan-creator), or general codebase scouting (mk:scout).
日本語の概要は準備中です。原文の説明を表示しています。
Use when loading, listing, composing, or validating graded evaluation rubrics — PASS/WARN/FAIL grading with weighted criteria and balanced PASS/FAIL anchor examples. Triggers on /mk:rubric, "load rubric", "compose rubric preset", "validate rubric", or evaluator-style code review that needs anchor-grounded judgments.
日本語の概要は準備中です。原文の説明を表示しています。
Serve any markdown file or directory as a calm, book-like reader via a local HTTP server (127.0.0.1 only). Best for long-form documents — RFCs, runbooks, design docs, plan files — where comfortable in-browser reading matters. Supports Mermaid diagrams, dark/light mode, plan navigation sidebar, and keyboard shortcuts. Requires explicit start and stop lifecycle.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, or optimizing React/Next.js code. Triggers on .tsx/.jsx files, React component work, Next.js routes, bundle optimization, re-render issues, or performance improvements. Auto-activates alongside mk:typescript when React project detected.
日本語の概要は準備中です。原文の説明を表示しています。
Coordinates staged or parallel jobs across live-verified coding-agent runtimes (Claude Code, Codex, Cursor, and other installed CLIs) and in-session toolkit subagents. Routes each job by capability and risk tier, isolates parallel writers in git worktrees, captures redacted output, resumes interrupted runs, and blocks completion until an independent arbiter verifies the results. Use when work should be split across multiple runtimes or subagents, run as staged or parallel jobs, and reviewed before handoff. NOT for a single-agent task or the in-session 7-phase flow (use mk:cook / mk:workflow-orchestrator).
日本語の概要は準備中です。原文の説明を表示しています。
JIRA issue CRUD via the jira-as wrapper. Triggers: 'create bug/task/story', 'show me PROJ-123', 'get/view/look up issue', 'update PROJ-123', 'delete PROJ-123'. NOT for transitions (mk:jira-lifecycle); NOT for comments/attachments (mk:jira-collaborate); NOT for bulk ops (mk:jira-bulk); NOT for issue links (mk:jira-relationships); NOT for time logging (mk:jira-time); NOT for sprint/epic (mk:jira-agile).
日本語の概要は準備中です。原文の説明を表示しています。
Deep spec analysis on a Confluence page. Reads page (+ children) via the confluence-as wrapper, produces a structured Spec Research Report with requirements, acceptance criteria, gaps, ambiguities, and suggested user stories for human review. Read-only — does NOT create Jira tickets. Triggers: 'analyze spec for PAGE-ID', 'extract requirements from confluence page', 'spec research on URL'. NOT for raw page CRUD (mk:confluence-page); NOT for ticket complexity scoring (mk:planning-engine).
日本語の概要は準備中です。原文の説明を表示しています。
Design and review durable REST, GraphQL, RPC, or event-facing API contracts. Use for public or shared API contracts, endpoint/schema consistency, compatibility, pagination, error semantics, and API documentation. Discovers existing consumers and conventions before recommending a style.
日本語の概要は準備中です。原文の説明を表示しています。
Design and implement backend service changes: API contracts, service boundaries, auth integration, reliability and delivery checks. Use for backend/API handlers, services, webhooks, jobs, or backend architecture changes. Routes schema/migrations to mk:database; security review to the existing security workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Workflow navigation assistant. Scans project state (plans, reviews, tests, git) and recommends the next step in the 7-phase pipeline. Use when asked "what should I do next?", "where am I?", "help", or at session start. NOT for domain complexity routing (see mk:scale-routing); NOT for skill discovery (descriptions handle that automatically).
日本語の概要は準備中です。原文の説明を表示しています。