1,900 件 ・ 関連度順
概要と使いどころ
Optimizes agent context setup. Use when starting a new session, when agent output quality degrades, when switching between tasks, or when you need to configure rules files and context for a project.
日本語の概要は準備中です。原文の説明を表示しています。
Elite AI context engineering specialist mastering dynamic context management, vector databases, knowledge graphs, and intelligent memory systems.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user asks to run Codex CLI (codex exec, codex resume) or references OpenAI Codex for code analysis, refactoring, or automated editing. Uses GPT-5.2 by default for state-of-the-art software engineering.
日本語の概要は準備中です。原文の説明を表示しています。
AI Agent 成本工程 — 基於 Claude Code 的成本追蹤、prompt cache 最佳化、token 預算控制逆向分析。Use when: 優化 token 消耗、設計成本控制機制、分析 cache 效率、選擇模型配置。
日本語の概要は準備中です。原文の説明を表示しています。
Harness Engineering 設計模式 — 基於 Claude Code 原始碼逆向分析的 12 條可遷移原則。Use when: 設計 agent 系統架構、實作 tool orchestration、設計 context 管理策略、建構 agent loop。
日本語の概要は準備中です。原文の説明を表示しています。
Delegate implementation to Codex, grok, or cursor-agent, then review the diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants Codex, the grok 后端, or cursor-agent to write code, mentions handing off / delegating implementation to one of those backends, asks to work through a plan or spec unit-by-unit with an implementation backend doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer runs in the real environment behind backend-specific git and publication boundaries, must not be pointed at a full test suite by default, and its self-report is a claim rather than evidence. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the engineering-mode skill when it is installed.
日本語の概要は準備中です。原文の説明を表示しています。
Delegate implementation work to a dedicated implementer subagent, then review its diff, send it back to iterate, gate on the full test suite, and ship it as a PR. Use this whenever the user wants a separate model to write code, mentions handing off / delegating implementation, asks to work through a plan or spec unit-by-unit with a subagent doing the coding, or wants a review-and-merge loop wrapped around delegated output — and also when resuming such a loop ("keep going", "next unit", "继续下一个"). It encodes constraints that are expensive to rediscover: the implementer self-reports success, must not run the full test suite by default, must not touch git, and its report is a claim rather than evidence. Cursor port of implementation-loop. This loop expects an approved plan or an equivalently precise spec; settle an unsolved high-level goal into a plan first, using the cursor-engineering-mode skill (it ships in this same plugin).
日本語の概要は準備中です。原文の説明を表示しています。
基于「AI工程造价+法律知识库」（1394人订阅，3149个内容）的造价+法律交叉领域AI技能。当用户需要进行工程造价司法鉴定、合同风险审查、变更索赔分析、结算纠纷诊断时使用。触发词包括但不限于：造价+法律、工程司法鉴证、合同风控、变更索赔、结算纠纷、鉴定意见、证据链、工期索赔、费用索赔。也适用于用户需要基于知识库内容进行案件分析、模拟鉴定、风险预警的场景。
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of the project's agent-tree structural overhead vs the context window. NOT for cost tracking (budget skill); NOT for read/compact decisions (mk:context-engineering).
日本語の概要は準備中です。原文の説明を表示しています。
Runtime router for context decisions: read-more/stop/ask/assume/delegate, minimal read-set, compaction timing. Model: Write/Select/Compress/Isolate. NOT for agent-tree overhead audit (context-audit).
日本語の概要は準備中です。原文の説明を表示しています。
Weekly engineering retrospective from commit history, work patterns, and code-quality metrics, with trend tracking and per-person breakdown. NOT for per-session reflection (mk:memory / Phase 6).
日本語の概要は準備中です。原文の説明を表示しています。
Creates new skills with proper structure, compliance checks, and registration. Enforces mk: prefix, sub-agents.md structure, and context-engineering principles. Use to scaffold a new skill.
日本語の概要は準備中です。原文の説明を表示しています。
Post-build pass reducing complexity without changing behavior. Catches dead code, needless abstractions, over-engineering. NOT for style (mk:clean-code) or diff review (mk:review).
日本語の概要は準備中です。原文の説明を表示しています。
Runtime router for context decisions: read-more/stop/ask/assume/delegate, minimal read-set, compaction timing. Model: Write/Select/Compress/Isolate. NOT for .codex/ overhead audit (mk:context-audit).
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of .codex/ structural overhead: 'remove X save Y tokens' vs the context window. NOT for cost tracking (budget skill); NOT for runtime read/compact decisions (mk:context-engineering).
日本語の概要は準備中です。原文の説明を表示しています。
Post-implementation simplification pass. Reduces complexity without changing behavior. Use after Phase 3 (Build GREEN) and before Phase 4 (Review). Catches dead code, unnecessary abstractions, over-engineering, and redundant patterns. Triggers on "simplify", "clean up", "reduce complexity", "too complex". NOT for style/convention enforcement (see mk:clean-code); NOT for reviewing diffs or PRs (see mk:review).
日本語の概要は準備中です。原文の説明を表示しています。
Create new skills with proper structure, compliance checks, and registration. Use when asked to create a skill, build a new skill, or scaffold a skill template. Enforces mk: prefix, sub-agents.md structure, and context engineering principles.
日本語の概要は準備中です。原文の説明を表示しています。
JSON-canonical session memory. Use when capturing session learnings, extracting patterns, or tracking costs — persists to .meowkit/memory JSON stores; matching Markdown files are generated views. Activates during Phase 0 (Orient) to load context and Phase 6 (Reflect) to persist it. NOT for weekly-cadence engineering retrospectives (see mk:retro); NOT for arbitrary file storage.
日本語の概要は準備中です。原文の説明を表示しています。
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).
日本語の概要は準備中です。原文の説明を表示しています。
Read-only audit of `.claude/` structural overhead. Reports prioritized "remove X save Y tokens" recommendations against the model context window. NOT for monetary cost tracking — that's /mk:budget. NOT for transcript size monitoring — long-session continuity defers to Claude Code native compaction. NOT for runtime context decisions (what to read, when to compact) — see mk:context-engineering. Use when planning to add context capacity, diagnosing perceived slowdowns, or auditing health.
日本語の概要は準備中です。原文の説明を表示しています。
Routes data engineering tasks to the correct DE expert agent. Use when user requests data pipeline design, DAG authoring, SQL modeling, stream processing, or warehouse optimization.
日本語の概要は準備中です。原文の説明を表示しています。
dbt best practices for SQL modeling, testing, and analytics engineering workflows
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Inspect an explicit Fusion design, parameters, geometry, references, configuration and health without editing it. Use for model understanding or engineering audits.
日本語の概要は準備中です。原文の説明を表示しています。