团队AI编码规范开源：告别Vibe Coding
推荐指数 55.0 NO. 015 · 2026.08.05
发布2026/08/04Score72Comments39
为什么值得看
ADLC Team Skills 开源了一套团队级AI编码规范层，让Claude Code和Codex等Agent共享团队的架构标准、产品策略和评测基准。解决多人用AI编程时代码风格混乱、技术债务累积的痛点，把"个人提示词技巧"升级为可版本控制的团队协作基础设施。
编辑判断
目前大多数团队用AI编码还处于"各凭本事"阶段，Cursor Rules、.claude.md这些个人配置文件无法跨成员同步，导致Code Review时人类和AI的标准打架。这个项目把团队规范做成了可版本控制的层，相当于给Agent发了"员工手册"。
跟Cursor的Project Rules相比，ADLC更强调评测基准和合规验证，不只是"告诉AI怎么写"而是"能检查AI写得对不对"。如果你的团队已经有3人以上用Claude Code或Codex，且PR质量在下降，值得先fork Team AI Directives那套模板试试，比从头写团队规范快得多。
潜在风险是维护成本：规范层本身需要专人更新，否则会变成新的技术债务源头。
社区反馈
负面 38 条评论
核心争论：AI编码规范是必要基础设施还是过度设计的token浪费
I work with an engineering team using Claude Code, Codex, and OpenCode daily. Early on, we created a custom fork of spec-kit to set up our team directives repository and distribute custom agent workflows. While that fork got us started, maintaining a custom fork of a CLI just to ship prompt workflow
I thought the HN guidelines forbid AI-generated comments?
I see what this is going for but can’t help but feel like it’s overwrought. It feels a bit like the most likely outcomes are increased token burn, review surface, and time per task vs not using this. Who knows, maybe that’s a good thing.