「implementation」の検索結果

Hot-reload a Python function implementation from the latest file content without restarting the process. Use this to apply code fixes live after identifying a bug with watch/trace.

日本語の概要は準備中です。原文の説明を表示しています。

Apply MCAF feature-spec guidance to create or update a feature spec under `docs/Features/` with business rules, user flows, system behaviour, verification, and Definition of Done. Use when the user asks for a feature spec, executable requirements, acceptance criteria, behaviour documentation, or a pre-implementation plan for non-trivial behaviour changes.

日本語の概要は準備中です。原文の説明を表示しています。

Designs implementation blueprints for features using exploration findings and architectural best practices (converted from agent)

日本語の概要は準備中です。原文の説明を表示しています。

Reviews code implementations for correctness, security, maintainability with confidence-scored findings (converted from agent)

日本語の概要は準備中です。原文の説明を表示しています。

Generate Claude Code native Tasks from an existing spec. Use when user says "create tasks", "generate tasks from spec", "spec to tasks", "task generation", or wants to decompose a spec into implementation tasks.

日本語の概要は準備中です。原文の説明を表示しています。

Convert Claude Code plugins into generic, platform-agnostic format. Supports full conversion (skills, agents, hooks), flatten mode (skills only — agents converted to skills, hooks absorbed), or nested mode (agents nested as pure markdown within parent skills, hooks absorbed). Full mode supports per-group or unified output layouts — unified merges all groups into a single directory organized by component type. Strips Claude Code-specific implementation details to produce clean markdown files preserving only the intent and instructions. Use when asked to "make this portable", "convert to generic format", "export plugin", "create universal skills", "strip platform dependencies", "make harness-agnostic", "decouple from Claude Code", "flatten to skills only", "nest agents in skills", or when the user wants their plugin content usable outside Claude Code. Also use when the user wants to share skills with teams using different agent frameworks.

日本語の概要は準備中です。原文の説明を表示しています。

Provides code quality principles including SOLID, DRY, testing strategies, and best practices for implementation review. Use when reviewing code or applying quality standards.

日本語の概要は準備中です。原文の説明を表示しています。

Conduct an adaptive interactive interview on any topic and produce a structured markdown report, summary, or implementation plan. Use when the user says "interview me", "interview me about", "run an interview on", "help me think through", or wants guided discovery on any subject. Also triggers on "talk me through", "explore X with me", "help me plan Y", or "walk me through my thinking on Z" when the user wants a guided conversation rather than a direct answer. Applies broadly — career decisions, project ideas, product direction, personal goals, research questions, team problems — not just technical topics.

日本語の概要は準備中です。原文の説明を表示しています。

Feature development workflow with exploration, architecture, implementation, and review phases. Use for implementing new features or significant changes.

日本語の概要は準備中です。原文の説明を表示しています。

Evaluates ML applications in investment with feature engineering, model selection, and implementation considerations for alpha generation. Use when evaluating ML for investing, designing ML pipelines, or assessing ML strategy feasibility.

日本語の概要は準備中です。原文の説明を表示しています。

Produce written specs and atomic PBIs that an implementation agent can execute independently. Authors specs and Linear issues.

日本語の概要は準備中です。原文の説明を表示しています。

Use when delegating a coding task to mimo (the mimo CLI / Xiaomi opencode fork) — offloading implementation to mimo, resuming a mimo session, or running work on a chosen provider/model. Triggers on "/mimo-code", "run mimo", "delegate to mimo", "resume the mimo session", "offload this to mimo".

日本語の概要は準備中です。原文の説明を表示しています。

Populate domain specs (glossary, entity definitions, use-cases) from SPEC.md content during implementation.

日本語の概要は準備中です。原文の説明を表示しています。

Templates and guidance for implementation plans with dynamic phase generation.

日本語の概要は準備中です。原文の説明を表示しています。

Create change specification and implementation plan with dynamic phase generation. Supports feature, bugfix, refactor, and epic types.

日本語の概要は準備中です。原文の説明を表示しています。

Use when developing or extending EZ_math_model itself from a written implementation plan, especially adding algorithms, tool skills, templates, or multi-step repo changes.

日本語の概要は準備中です。原文の説明を表示しています。

Post-implementation QA planning — independent of /review (the developer chooses whether to run them sequentially or in parallel), only when the change has a running surface worth driving. Interviews the developer to turn the specs and the diff into an executable QA specification (specs/qa/QA-<N>-<slug>.md) that /execute-qa runs. The agent drives browser and shell; the human steps in only at named handoff points. Use only when the user asks to plan manual QA — never trigger automatically.

日本語の概要は準備中です。原文の説明を表示しています。

Dispatch code-reviewer subagent to review implementation against plan or requirements before proceeding

日本語の概要は準備中です。原文の説明を表示しています。

Execute implementation plan by dispatching fresh subagent for each task, with code review between tasks

日本語の概要は準備中です。原文の説明を表示しています。

Receive and act on code review feedback with technical rigor, not performative agreement or blind implementation

日本語の概要は準備中です。原文の説明を表示しています。

Create detailed implementation plans with bite-sized tasks for engineers with zero codebase context

日本語の概要は準備中です。原文の説明を表示しています。

Create distinctive, production-grade frontend interfaces with strong hierarchy, thoughtful systems, and polished implementation that avoid generic AI aesthetics. Use when the user wants to build or redesign web pages, flows, components, or full app surfaces, or when another better-web-ui skill needs shared project design context before other better-web-ui skills.

日本語の概要は準備中です。原文の説明を表示しています。

Create standout, technically ambitious interfaces that feel extraordinary through cinematic transitions, advanced motion, heavy rendering, or other high-ambition implementation work. Use when the user wants to wow, impress, go all-out, or push a feature beyond conventional UI polish—not when simple visual confidence or routine cleanup is enough.

日本語の概要は準備中です。原文の説明を表示しています。

Gather and persist project design context such as audience, brand personality, UX goals, and implementation defaults for future better-web-ui work. Use when starting a project, defining UI direction, or establishing reusable design guidance before other better-web-ui skills.

日本語の概要は準備中です。原文の説明を表示しています。