Use when code mixes units, fixed-point precisions, scaling factors, rates, prices, shares, or conversions. Not for type-level unit modeling: use type-driven.
中文简介正在准备中。当前显示原文说明。
@OutlineDriven
组织
Outline-Driven Development - methodology between vibes and specs. Plugins for Claude Code, Codex CLI, and Gemini CLI. AST tooling + context engineering.
300 个技能1 个仓库 37
Use when code mixes units, fixed-point precisions, scaling factors, rates, prices, shares, or conversions. Not for type-level unit modeling: use type-driven.
中文简介正在准备中。当前显示原文说明。
Use when reconciling an API endpoint's generated OpenAPI schema and declared response types with its actual runtime response. Not for general API documentation: use docs-and-adrs.
中文简介正在准备中。当前显示原文说明。
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.
中文简介正在准备中。当前显示原文说明。
Use when an implementation has more workarounds than structure and another patch will not pay. Not for in-place re-derivation: use breaking-driven. Not for one-artifact rewrites: use rewrite-clean-v0.
中文简介正在准备中。当前显示原文说明。
Use when an exact symbol, path, entrypoint, or line range can bound a focused code question or patch proposal under a fixed source budget. Not for source changes or broad repository exploration.
中文简介正在准备中。当前显示原文说明。
Use when a feature begins or specs are checked in: author or update behavioral specs and keep them current with what ships. Not for producing the initial approved spec and plan: use spec-driven.
中文简介正在准备中。当前显示原文说明。
Use when invoked to apply an invariant-first, fail-fast, special-case-eliminating baseline. Not for domain models in types: use type-driven. Not for design-by-contract: use contract-driven.
中文简介正在准备中。当前显示原文说明。
Use when a trusted bug or performance report needs reproduction and fix. Not for untrusted reports or scope beyond the named feature.
中文简介正在准备中。当前显示原文说明。
Use when a human says "overhaul", "rebuild this subsystem", or "rewrite it from scratch". Not for thin-slice features: use incremental-implementation. Not for root-cause repair: use strike-the-root.
中文简介正在准备中。当前显示原文说明。
Use when asked to explore the codebase to map structure, symbols, and dependencies. Not for a single file under 50 LOC: read it directly.
中文简介正在准备中。当前显示原文说明。
Use when the user asks to make the skills framework work in a new harness, IDE, or CLI. Not for remote, credential, publish, deploy, or irreversible changes.
中文简介正在准备中。当前显示原文说明。
Use when the user wants a clean Xcode rebuild by deleting DerivedData and build artifacts. Do not use for diagnosing a specific build error: use ios-build-fix.
中文简介正在准备中。当前显示原文说明。