开放方法 · 有界任务 · 可追溯证据
让 AI 的生产能力
成为共同的工具
这里不是模型榜单，也不是不透明的 AI 平台。这个仓库把原则、方法、执行单元和验证证据放在一起，让普通人和小团队能够检查、修复、替换并继续改进自己的工作系统。
共同工作台 / COMMON WORKBENCH
- 01Principles判断从何而来
- 02Methods判断如何行动
- 03Practice行动如何受检验
- 04Evidence经验如何被继承
从具体问题开始
先从一个真实问题开始
这个仓库中的活动技能可以分别安装。先选择一个与当前问题相符的方法，在真实任务中观察它是否改变行动；任何模型、供应商和运行时依赖都应当保持可见、有限并可替换。
查看使用入口当前方法
每个技能只负责一种可辨认的判断
19 个活动技能由同一原则序列表达，但不共享一个万能工作流。
- 01
principle-cultivation
Steward a project's fallible principle lineage: preserve source-bound research, turn only gate-passing inquiries into candidates, convene selective P-ID reviews, clarify interpretations, trial human-nominated alternates, and prepare human-only Sequence decisions. Use for reusable-principle research, candidate proposals, principle reviews, interpretation drift, alternate trials, or maintaining a principle-centered skill collection.
- 02
context-engineering
Design, audit, and verify how decision-relevant project information reaches an agent through the actual runtime. Use when an agent misses a governing boundary, receives irrelevant context, cannot discover an instruction or skill, or when deciding what should be always available, activated for a task, or retrieved on demand. Do not use to author domain knowledge, organize its source artifacts, write a one-off prompt, configure vendor hooks, or build an agent runtime.
- 03
improve-agent-workflow
Diagnose and improve how coding agents work in an existing project: project skills, AGENTS instructions, prompt and context delivery, tools or CLI surfaces, hooks, verification, handoffs, and agent-facing workflow. Use when an agent repeatedly misses scope or instructions, the owning agent-facing surface is unclear, several surfaces interact, agent experience is costly or confusing, or a user asks Codex to improve how agents work in a company repository. Start from observed project evidence, change the smallest owning surface, and verify behavior through the ordinary agent entry path. If the issue is already localized to a skill's trigger, prompt, context layering, or behavior evaluation and a dedicated skill-engineering method is available, use that method directly. Do not use for ordinary product features, generic CI or business workflows, one-off prompt wording, or a process redesign with no observed agent-action gap.
- 04
skill-engineering
Design, rewrite, review, and test agent skills that improve a repeated agent action or judgment. Use when creating a skill, rewriting a SKILL.md, improving a known skill trigger or action layer, reducing skill-context bloat, or checking whether a skill instruction actually changes behavior. Triggers include "create a skill", "rewrite this skill", "review this SKILL.md", "improve this project skill", "skill design", and "test this skill prompt". If an agent-work failure has not yet been localized to a skill, let an agent-workflow diagnostic method identify the owning surface first.
- 05
disciplined-development
Lightweight behavioral discipline for any development task — ground decisions in evidence, choose the smallest valid change, test before claiming done, and analyze the specific situation before applying a pattern. Triggers on "be more disciplined", "professional habits", "stop overengineering", "check your work", "don't guess", "bad habits", "test strategy", "meaningful tests", or "avoid test bloat"; also when an agent shows overconfidence, untested claims, or repetitive overengineering across tasks.
唯一语义根
原则不是墙上的口号。
它要在行动中留下差异。
当前证明义务
先在有界生产任务上，证明更经济的开放组合能够交付可检查的结果。
这是一项需要持续证据的长期工作，不是已经兑现的模型优越性声明。人保留目的、数据和验收权；运行时保留成本、失败和修复路径。