「contract」の検索結果

5-layer agent output validation, I/O contract specification, vertical slice development, and test doubles policy with per-layer examples

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

Use before planning a frontend phase, or when a UI contract must be locked before implementation. Orchestrates gsd-ui-researcher and gsd-ui-checker to validate, research, and verify UI-SPEC.md for the phase.

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

The HyperFrames composition contract — build one renderable project. Use for composition structure, the `data-*` timing attributes, `class="clip"`, tracks, sub-compositions, variables, framework-owned media playback, deterministic-render rules, and validation. Also covers Tailwind projects and the STORYBOARD.md / SCRIPT.md plan formats. Read before writing composition HTML.

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

Design bounded bot specifications with clear purpose, examples, output contracts and error handling. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.

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

Translate a sanitized cURL request into an explicit API contract draft and integration requirements. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.

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

Identify negotiable contract terms and draft options with commercial tradeoffs and legal review questions. Use for this Bot Generator Bot template; creates drafts or simulations within its declared scope.

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

Implements safe error boundaries, cancellation and user recovery contracts; not telemetry pipelines or durable retry machinery.

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

Reviews skill instructions, trigger boundaries and distribution contracts; not product code.

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

Implements one scoped product feature or fix using existing contracts; not upgrades, performance tuning or establishing cross-cutting technical foundations.

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

Designs target system boundaries, contracts and tradeoffs from requirements; does not plan tasks or implement.

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

Implement Domain-Driven Design with typed DTOs, repository interfaces, and single-responsibility Action classes in Laravel. Use when creating domain folders, binding repository contracts in providers, or passing DTOs between layers.

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

Define the delivery metrics contract for agent-assisted SDLC — DORA four plus per-stage indicators derived from artifact and git history, and the control bands that turn metric drift into a routed intake. Use when reporting cycle time, plan adherence, or defining response thresholds.

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

Designs modular high-level architectures from functional requirements and produces design documents for each module. Use when designing a new system, creating architecture documentation, or producing module-level design specs with integration contracts and test specifications.

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

Internal Ralph Specum contract for Codex phase interviews, skill manifests, approval, and delegation gates. Phase coordinators load this skill directly; users do not invoke it as a workflow phase.

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

Captures executable contracts and coding conventions into .trellis/spec/ documents. Use when learning something valuable from debugging, implementing, or discussion that should be preserved for future sessions.

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

Professional DOCX document creation, editing, and formatting using OpenXML SDK (.NET). Three pipelines: (A) create new documents from scratch, (B) fill/edit content in existing documents, (C) apply template formatting with XSD validation gate-check. MUST use this skill whenever the user wants to produce, modify, or format a Word document — including when they say "write a report", "draft a proposal", "make a contract", "fill in this form", "reformat to match this template", or any task whose final output is a .docx file. Even if the user doesn't mention "docx" explicitly, if the task implies a printable/formal document, use this skill.

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

API design, versioning, testing, schema validation, and contract testing patterns for REST and GraphQL APIs.

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

Strategic guidance for choosing and implementing testing approaches across the test pyramid. Use when building comprehensive test suites that balance unit, integration, E2E, and contract testing for optimal speed and confidence. Covers multi-language patterns (TypeScript, Python, Go, Rust) and modern best practices including property-based testing, test data management, and CI/CD integration.

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

Use when a `source-tutorial` workspace has ingested sources and needs a grounded tutorial contract before structure planning.

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

Use when an agent needs to drive a real Chrome window via opencli — inspect a page, fill forms, click through logged-in flows, or extract data ad-hoc. Covers the selector-first target contract, compound form fields, stale-ref handling, network capture, and the agent-native envelopes the CLI returns. Not for writing adapters — see opencli-adapter-author for that.

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

Own MSBuild import and hook discovery. USE FOR: CustomBefore/CustomAfter hooks, ordered wildcard and NuGet auto-imports, control properties, build/buildTransitive packed layout, package ID and file-name matching, per-TFM forwarders, and tracing why assets or hooks are missing, broken, or replaced. An import guard remains in scope when it is one defect in a broader hook/import flow. DO NOT USE for a focused safety verdict on whether one specific Import needs Exists or is an intentionally unguarded package contract; use msbuild-antipatterns. NEVER INVOKE when imports and hook placement already work and the request is only target Inputs/Outputs, incremental skipping, or FileWrites clean tracking; use incremental-build or target-authoring. Exclude props-versus-targets placement and non-MSBuild systems.

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

Apply minimal MCAF repository governance when the user explicitly asks to adopt MCAF or change MCAF-specific rules. USE FOR: creating or tightening root and local AGENTS.md policy; placing durable engineering context; defining the repository's own verification contract. DO NOT USE FOR: ordinary .NET implementation, documentation edits, UI/UX, testing, CI, Git, NFR, developer-experience, or ML work unless the request is specifically about MCAF governance. INVOKES: inspect repository policy and documentation, make the smallest durable governance change, then validate the affected repository surfaces.

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

Use only for MSBuild failure investigation, build-performance analysis, or review of existing build XML/extension contracts. A plan to convert a working legacy/non-SDK project to SDK style or migrate packages.config is a project-system migration, NOT a build-file review: do not activate, even to check scope. Framework/API upgrades are also excluded. Activate for advisory Import/Exists hook and NuGet packed-import questions even without a checkout or failed build; .csproj/.fsproj/.vbproj/.props/.targets conditions; custom-target inputs/outputs; .binlog capture/replay; failing dotnet build/restore/pack/publish or MSBuild-based test builds; slow evaluation, compilation, copying, or no-change builds; and controlled timing comparisons. Exclude SDK installation alone, C# refactoring, runtime profiling, assertions after successful builds, and non-MSBuild builds.

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

Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.

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