「implementation」の検索結果

Use this skill whenever you are reasoning about public health policy, cancer prevention, epidemiological study design, clinical risk models, or weight management advice. This skill channels the thinking of Graham A. Colditz, epidemiologist at Washington University in St. Louis. Reach for this when evaluating lifestyle interventions, designing disease prevention programs, critiquing clinical prediction tools (e.g., AUC vs. clinical utility), or analyzing life-course risk accumulation. Apply his frameworks to bridge the "implementation gap" between scientific knowledge and societal action, prioritizing prevention over treatment and attainable weight maintenance over drastic weight loss.

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

Set performance budgets before implementation.

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

Check premium specs before implementation.

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

Turn a feature request into a minimal, file-level implementation plan before any code.

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

Suede-affiliated ethical application of behavioral science to marketing decisions, including framing, anchoring, social proof, loss aversion, choice architecture, and friction. Use when the user needs a named psychological model, an evidence-aware application, and a testable hypothesis. NOT FOR: clinical or mental-health advice, deceptive dark patterns, page implementation (use suede-site-alchemy), or pricing design (use suede-pricing).

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

Suede-affiliated engineering-as-marketing strategy for selecting, scoring, and scoping calculators, graders, generators, and other free interactive tools. Use when the user wants a lead, link, education, or product-adoption asset with a measurable path to the paid product. NOT FOR: downloadable lead assets (use suede-lead-magnets), implementation of a full website (use suede-site-alchemy), or search diagnostics (use suede-seo-audit).

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

Suede AI eval design and coverage audit: AI-SPEC, failure-mode rubric with severity scoring, concrete pass/fail eval cases, coverage and infrastructure scores, and mechanical acceptance gates. Use when a change ships LLM, RAG, agent, classifier, prompt, or generated-media behavior, or when asked to write evals for an AI feature, design test cases for a model surface, audit existing eval coverage, or judge whether AI behavior is safe to ship. No AI-SPEC means no eval plan, and no eval plan holds the recommended ship verdict. NOT FOR: reviewing or grading the implementation code behind the AI surface (use suede-code); wiring a passing suite into CI as a required check (use suede-ci-gate); UAT of the built feature beyond the eval suite (a private Suede Labs companion, not in this pack).

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

Suede Thought Graph shipping search for a multi-file repo change. Use when competing implementation plans need one evidence-gated selection before any build. Halts on hazards, collisions, budget exhaustion, or no safe winner. Reads production; never deploys. NOT FOR: bulk independent work (use a separate private worker-fleet pass); findings-only diff review (use suede-code-review); CI or branch-protection wiring (use suede-ci-gate); copy-only shipping (use suede-ship-copy).

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

Structured planning mode for AI agents working on coding and development tasks. Produces a comprehensive plan BEFORE any code is written or changed, including task decomposition, architecture decisions, risk assessment, and approval gates. Use this skill whenever the user says "/plan", "plan mode", "plan first", "think before coding", "make a plan", or asks the agent to plan before executing. Also trigger when the user describes a complex multi-step development task and would clearly benefit from structured planning before implementation — especially for tasks involving new features, refactors, migrations, infrastructure changes, or multi-file edits. When in doubt, plan. A few minutes of planning prevents hours of rework.

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

Answer questions about code, architecture, and technical decisions — no implementation. Trigger on questions asking 'why', 'what does this do', 'what is the purpose of', 'explain', 'what's the difference', 'compare', or 'what are the tradeoffs' — even when referencing specific files, code snippets, or inline code. The key signal is the user wants to UNDERSTAND something, not change it. Do NOT trigger for requests to build, fix, plan, review, research, or add/modify code.

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

Use when the user wants a written, reviewable plan or spec produced before coding starts. Triggers on: mapping out changes without implementing, thinking through risks of upgrades or migrations, evaluating approaches before committing to one, writing specs for team review, phasing work into stages, or any request that explicitly defers coding ('don't implement yet', 'before we build'). The distinguishing signal is that the user wants a plan artifact — not implementation, not a conversational answer. MUST activates inside Claude's native plan mode to have a better planning behavior.

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

Review code for quality, correctness, and fit. Use when the user wants judgment on code that already exists — their own changes, a teammate's patch, a PR, branch, commit, diff, staged changes, or one or more files to look over. Activate on requests like review, look over, sanity check, critique, code review, or 'is this good?' The key signal is that the user wants evaluation of existing code and its tradeoffs, not implementation, debugging, or explanation. This skill works independently, but when plans, specs, task artifacts, or prior discussion exist, use them to understand why the code exists before judging it.

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

ALWAYS activate when the user's query involves Docker in any way — even if it also matches other skills. If the words docker, Dockerfile, docker-compose, compose.yml, container, or image appear in the query, this skill MUST be used. Covers: writing or editing Dockerfiles and compose files, adding services (postgres, redis, etc.) to compose, volume mounts and data persistence, docker build failures (layer caching, npm install issues), healthchecks and service startup ordering (depends_on), environment variables in containers, port mapping, container crashes and exit codes (OOM/137), non-root users, multi-stage builds, image optimization, .dockerignore, and deploying to container runtimes. Takes priority over general implementation or debugging skills when Docker infrastructure is the subject.

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

Generate phased implementation roadmaps with Epic/Story/Task breakdown, effort estimates, and validation checkpoints. Use when cto-architect needs to create actionable technical roadmaps from architecture designs.

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

Convert an approved PRD or clear requirements into an implementation-ready technical spec with scope, interfaces, and acceptance criteria.

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

Design backend architecture for implementation with API contracts, data model changes, service boundaries, security, and observability.

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

Create comprehensive implementation plans with bite-sized tasks. Use when you have requirements before touching code.

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

Write a structured PRD for high-risk, cross-team, or multi-sprint initiatives before implementation.

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

Design implementation-ready frontend solutions with UX intent, component structure, responsive behavior, accessibility, and handoff criteria.

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

Use when you finish an analiz report - the human must approve the analysis before any implementation task is created, via the analiz_review column

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

Use when you write the `plan` section of an analiz report - steps that pin files, signatures, tests and verify commands, nothing more

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

Use when an analiz task arrives in done (approved) - turn the approved split into implementation tasks with repository, AC, derived_from and ordering arguments

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

Use when the stakeholder asks about an analysis outcome or its implementation tasks - understand the human approval gate and review the tasks the architect created once the human approved

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

Master workflow for an implementation task. Use when you pick up any task or bug that changes product code, including a need_revision bounce.

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