3,225 件 ・ 関連度順
概要と使いどころ
Search, read, create, edit, and maintain knowledge in a Memex KB via the `mx` CLI. Use when the user asks to search the KB, find documentation, check project or organizational docs, add or update knowledge-base entries, audit KB quality, or when reusable knowledge should be captured for future agents.
日本語の概要は準備中です。原文の説明を表示しています。
Makes the agent reconsider a task it just handed back to the human and find a way to do it itself, checking memory, CLI tools, skills, MCP servers, and documentation in turn. Use when the user invokes `/you` or `$you`, or replies that the agent should do something itself rather than asking them.
日本語の概要は準備中です。原文の説明を表示しています。
Structures git branches and worktrees: keeps unrelated changes on separate branches, isolates each in its own worktree created so the repository's setup runs, records dependencies with git-machete, and recombines them into a temporary mixdown branch for local testing. Use before creating any branch or worktree in a codebase that works on more than one branch, including branching off the default branch to start a change; when starting work in a fork, clone, or third-party checkout; when choosing what a new branch should be based on; when a branch is growing a second unrelated concern; when deciding whether to stack branches or keep them independent; when preparing a change for a pull request or patch submission; when handed an existing worktree or branch to implement and commit in a fork; or when a local build needs several in-progress branches combined. Not needed where the repository clearly commits everything to the trunk, or holds notes or personal data rather than code.
日本語の概要は準備中です。原文の説明を表示しています。
Triages an already-dirty Git working tree: breaks down every uncommitted change hunk by hunk, separates deliberate edits from tool-written churn, possibly accidental reversions, misplaced scope, and sensitive content, asks the user about the ambiguous cases, and proposes an ordered set of commits plus a list of hunks to hold back. Use when the user invokes `/pc` or `$pc`, asks what they should commit, wants their uncommitted changes broken down, or wants commits proposed for a dirty working tree or pile of accumulated local modifications. To plan commit boundaries for a change before or while implementing it, use `incremental-commits` instead.
日本語の概要は準備中です。原文の説明を表示しています。
Rebases every local branch of a fork onto a moved upstream, flags the ones upstream has superseded, and rebuilds the mixdown branch that combines them. Use after fetching a fork's upstream and finding it has advanced far, been force-pushed, or rewritten its history; when several stacked or sibling branches all need bringing forward at once; when a branch was cut from a mixdown and now carries merge commits it should not have; or when asked to rebase all branches, re-mix, or bring a whole worktree set up to date.
日本語の概要は準備中です。原文の説明を表示しています。
当AI智能体需要处理以下情形时触发本技能： 1. 当前案件/问题在现行法律中没有直接、明确的规定（法律漏洞）； 2. 需要参考已有判例、相似案件或相近法律规范来推导当前问题的处理方案； 3. 用户明确要求"参照""比照""类推适用"某一规范或案例； 4. 在法律论证中需要以"相似案件相似处理"（Like cases should be treated alike）原则支撑结论； 5. 需要评估两个或多个案件/规范之间的相似性与差异性，以判断能否进行类比； 6. 在合同解释、侵权责任认定、行政处罚裁量等场景中，需要借助类似情形的处理经验形成论证。 本技能的核心是：识别相似性基础（tertium comparationis），论证类比的正当性，并在此基础上得出合理的法律结论。
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
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".
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes ticket complexity and maps dependencies against an existing codebase before sprint planning. Triggers on 'how complex is this ticket', 'what should we work on first', 'can we fit this in the sprint', 'tech review before planning', 'plan the sprint'. NOT for writing implementation plans (see mk:plan-creator); NOT for scope/ambition review (see mk:plan-ceo-review).
日本語の概要は準備中です。原文の説明を表示しています。
Relentlessly interview the user about THEIR plan or design — one question at a time — resolving each branch of a decision tree until shared understanding. Claude is the interviewer; the user is the interviewee. Triggers on "grill me", "stress-test this plan", "get grilled on my design", "interrogate my plan". Checkpoints every answer to docs/knowledge/<slug>.md so progress survives a context-window reset. Flags knowledge the user cannot answer as a gap to chase. Do NOT use to PROPOSE solutions or compare approaches (→ mk:brainstorming). Do NOT use to validate "is this worth building?" (→ mk:office-hours). Do NOT use when Claude should ANSWER questions about the repo (→ mk:ask-me). Do NOT use for a one-shot review of an existing plan (→ mk:plan-ceo-review). Do NOT use to apply named reasoning lenses to findings (→ mk:elicit).
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Zod schema validation and React Hook Form integration for TypeScript frontends. This skill should be used when creating forms, defining API schemas, validating form data, implementing type-safe validation, using ZodResolver with React Hook Form, or migrating legacy forms to the Zod + React Hook Form pattern.
日本語の概要は準備中です。原文の説明を表示しています。
DraftForge test infrastructure for writing backend unit tests, Playwright E2E tests, and managing test data population. This skill should be used when writing new tests, adding test fixtures, creating populate functions for new features, adding Playwright E2E specs, using login/auth fixtures, creating test users/orgs/leagues/tournaments, or understanding the test data architecture. Covers backend Django tests via Docker, Playwright config (projects, workers, sharding), test auth endpoints that expose backend login to frontend, and feature-isolated test data patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Django Redis caching with django-cacheops. This skill should be used when implementing caching, adding cache invalidation, optimizing API performance, modifying models that affect cached data, or debugging cache-related issues in the Django backend.
日本語の概要は準備中です。原文の説明を表示しています。
Structured logging conventions for DraftForge backend (Django/Celery/Daphne) and frontend (React). This skill should be used when adding log statements, creating new modules, debugging with logs, or reviewing logging patterns. Covers structlog usage, system/subsystem taxonomy, required fields, log levels, and Grafana query patterns.
日本語の概要は準備中です。原文の説明を表示しています。
Replace with description of the skill and when Claude should use it.
日本語の概要は準備中です。原文の説明を表示しています。
Python Invoke task automation for DTX website. This skill should be used when running repo commands, backend tests via Docker, database migrations, updating invoke tasks, Docker operations, or workflow automation. Supports dev/test/prod environments with run, exec, up, down commands. References docs/development/invoke-tasks.md for complete command reference.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill for ANY of the following — do not skip it even if the query seems simple: strategic decisions, business analysis, thesis building, complex problem solving, geopolitical analysis (non-market), philosophical reasoning, academic research, system design, decision under uncertainty, long-form thinking, or any question that benefits from First Principle deconstruction and multi-agent reasoning. ALWAYS use this skill when the user asks about: why something works the way it does, whether a decision is correct, how to think about a complex problem, what could go wrong, analyzing a situation from multiple angles, or any "should I..." question involving real-world trade-offs. This is NOT a market/trading skill — for financial markets, BTC, gold, stocks, forex, macro economics, use money-atlas-intelligence-os instead.
日本語の概要は準備中です。原文の説明を表示しています。
Pick a visual direction before generating any creative. Produces 3-6 named, distinct visual directions (e.g. premium minimal, bold maximalist, lifestyle/editorial, retro, techno-brutalist) with rationale + sample prompts, then generates one reference image per direction so the user can choose. Use when the user says "explore visual direction", "what style should this be", "give me directions/looks", or before ads/scene/shot work when no style is locked. Part of the Creative Production set.
日本語の概要は準備中です。原文の説明を表示しています。
Connect business positioning to a concrete visual language. Maps strategic positioning (category, differentiator, who-it's-for, who-it's-against) onto visual decisions — palette, type, imagery, tone — so the look reinforces the strategy. Use when the user says "positioning into visuals", "what should the brand look like given our strategy", "align visuals with positioning", or is moving from strategy to brand expression. Part of the Creative Production set.
日本語の概要は準備中です。原文の説明を表示しています。