fable-design-options

仓库创建 2026年7月5日最近提交 22 天前SkillHot 收录 22 天前

▸ 精选理由

面向实际实现的证据驱动设计，适合需要有据可依的架构决策场景。

这个 Skill 做什么

基于代码库证据生成多种技术设计方案与权衡分析。

读取真实代码库证据后，给出多套可选的技术方案并把每种做法的利弊、迁移成本和风险讲清楚。适合在现有系统上做架构调整、API 改动、数据模型迁移或需要写决策备忘时使用。特别之处是建议会指向具体代码文件/证据，避免抽象建议，必要时还能启用子代理做更深入的评估。

▸ 展开 SKILL.md 英文原文

Evidence-grounded design option generation for technical architecture, migrations, APIs, data models, safety controls, operational changes, and implementation plans. Use when the user asks for options, tradeoffs, design review, migration strategy, or a decision memo grounded in the current codebase.

开发编程架构设计方案生成迁移权衡分析Codex

Stars

Forks

仓库内 Skill

7 日增星

安装 / 使用

给你的 Agent 一句话（通用）

帮我安装这个 skill：https://raw.githubusercontent.com/rhein1/fable5-codex/main/plugins/fable5-codex/skills/fable-design-options/SKILL.md

或 curl 直取 SKILL.md

curl -fsSL "https://raw.githubusercontent.com/rhein1/fable5-codex/main/plugins/fable5-codex/skills/fable-design-options/SKILL.md"

SKILL.MD 节选查看完整文件 ↗

# Fable Design Options

Generate options after reading the actual system. Avoid abstract architecture advice when source evidence is available.

For ECF-style governed runs, use `../../references/ecf-run-contract.md`. For large or high-risk design-option tasks, use real Codex subagents when the runtime exposes a subagent tool and the user has not opted out; treat architecture, migration, API, data model, security/privacy/money/data/API, operational, release, or cross-module decisions as large by default. Otherwise run `single-agent multi-lens` and say why no subagents were used when workflow trace is requested.

## Workflow

1. Clarify the decision, constraints, authority boundaries, and suc

via SKILL·HOT · 数据来自 GitHub 公开信息 · 原文版权归作者所有