「before」の検索結果

Relentlessly stress-test a plan or design through a one-question-at-a-time interview that researches available context first and includes a recommended answer with every question. Use when the user asks to "grill me", wants a plan/design challenged, or needs decisions resolved before implementation.

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

Set up Claude Code git safety guardrails that block dangerous git commands before execution. Use when the user asks to prevent git push, hard reset, git clean, destructive checkout/restore, or branch deletion from Claude Code hooks.

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

Phase 1 of the Forge pipeline. Gather real context from the codebase, answer everything the code can answer through exploration, then grill the user one question at a time (with a recommended answer) for only what code cannot answer, and write a research document. Use when starting /forge-research or the research step of /forgemaster, or when the user wants a research-first investigation before planning a feature.

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

Generate multiple radically different interface designs before implementation. Use when designing an API, module boundary, command surface, data contract, or when the user says "design it twice".

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

Fact-check an implementation plan against the real codebase and first-party documentation, flagging inaccuracies with what / why / evidence and a severity tier. Use when the user wants a plan reviewed or validated for accuracy, runs /review-plan, or wants a plan checked against real code before implementing. Accepts a Beads issue, a filesystem path, or a plan pasted into chat.

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

Professional, ethical HR partner for hiring, onboarding/offboarding, PTO and leave, performance, compliant policies, and employee relations. Ask for jurisdiction and company context before advising; produce structured, bias-mitigated, lawful templates.

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

Validates Conductor project artifacts for completeness, consistency, and correctness. Use after setup, when diagnosing issues, or before implementation to verify project context.

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

Complete guide for TUnit new-generation testing framework. Use when creating test projects with TUnit or migrating from xUnit to TUnit. Covers Source Generator driven test discovery, AOT compilation support, fluent async assertions. Includes project creation, [Test] attribute, lifecycle management, parallel control, and xUnit syntax comparison. Keywords: TUnit, tunit testing, source generator testing, AOT testing, new generation testing framework, [Test], [Arguments], TUnit.Assertions, Assert.That, Before(Test), After(Test), NotInParallel, TUnit.Templates, Microsoft.Testing.Platform, TUnit vs xUnit, parallel execution

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

Mandatory final risk-focused review for any repository change. Checks security, architecture boundaries, test coverage, and release readiness before closeout.

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

Build a minimal context pack and recommend the correct specialist path for token-efficient execution. Use when the task is non-trivial, spans multiple domains, or should reduce token usage before implementation.

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

Use for non-trivial, design-bearing, or architecture-affecting work before execution planning. Creates or updates a versioned spec under planning/specs/active/ with design intent, alternatives, risks, and acceptance criteria.

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

Use as the single visible starter and controller for workspace work that may change files, runtime assets, planning state, docs, settings, or governance. Normalize the request into the Super Agent lifecycle: intake, spec registration for non-trivial work, planning registration, specialist routing, execution, testing, review, closeout, and planning-state updates before implementation begins.

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

Audit and remediate dependency/package vulnerabilities across .NET backend, frontend (npm/pnpm/yarn), and Rust projects with severity-based quality gates. Use when the user asks for SCA checks, dependency hardening, or release security gates before build/package.

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

Use for non-trivial feature, behavior, workflow, or architecture work before execution planning. Create or update a versioned spec under planning/specs/active with design intent, alternatives, risks, acceptance criteria, and planning readiness.

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

Route tasks using the repository's static routing catalog and load only the minimal context pack. Use before execution when the task spans multiple domains or the correct instruction set is unclear.

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

Documentation and narrative content for create-vue-dsfr. Use for markdown files, Storybook stories, VitePress guides, component documentation, and API documentation. Read the shared project skill before acting.

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

Git commit, branch, and pull request conventions for create-vue-dsfr. Use before creating commits, branches, issues, or PRs. This skill has priority over other project skills for commit and PR work.

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

Unit and integration testing strategy for create-vue-dsfr. Use for writing, updating, or refactoring Vitest specs and test coverage. Read the shared project skill before acting.

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

Code implementation, refactoring, and bugfixes for create-vue-dsfr. Use for implementing features, refactoring code, or fixing bugs. Read the shared project skill before acting.

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

Use FIRST when someone asks for a new feature or a change to an existing one — before any schema, code or test. Works out what is actually being asked for, whether to build it or integrate a third party (Trustpilot, Stripe, Calendly and the like), where the data lives, who may do what, and what happens when the vendor is down. Produces a decision, then hands to feature-schema.

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

Audit a page or the whole yoursite site (or a new site) for indexing readiness — cache headers, sitemap, robots, canonical, JSON-LD, internal links — and check the publish pipeline (Cloudflare purge/warm, IndexNow, GSC, Bing). Use before/after publishing content or launching a site.

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

Gather phase context through adaptive questioning before planning. Use --auto to skip interactive questions (the agent picks recommended defaults). Use --chain for interactive discuss followed by automatic plan+execute. Use --power for bulk question generation into a file-based UI (answer at your own pace).

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

Ingest external plans with conflict detection against project decisions before writing anything.

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

Surface the agent's assumptions about a phase approach before planning

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