可直接放进 Codex 的简化指令:优先满足当前已验证需求的最简单设计,不为假设的未来需求增加抽象、依赖和基础设施;评论补充了简单性与模块边界的平衡。
本站仅展示 Tabbit 编辑摘要和必要节选;完整内容、上下文与最新版本请查看原始来源。
Prefer the simplest design and implementation that fully satisfies the current, demonstrated requirements.
Do not add abstractions, layers, configuration, extension points, dependencies, or infrastructure for hypothetical future needs. Introduce them only when concrete requirements or repeated patterns justify their cost.
Before adding code, consider whether the goal can be met by deleting, consolidating, or reusing existing code.
When multiple approaches are correct, choose the one with fewer concepts, moving parts, and maintenance obligations, unless evidence shows that a more complex approach is necessary.
Treat patterns and principles as tools, not goals. Do not apply SOLID, design patterns, or architectural boundaries in ways that make a small solution more complicated than the problem requires. 共享 排序方式: 评论区域 mindstuff8 • 18天前
I think you've missed something here that is super important and that is dealing with context.
I’ve seen vibe-coded projects become giant single-file apps because “keep it simple” was interpreted as “don’t create boundaries.” Then AI struggles because every change pulls too much unrelated code into context.
Modularity isn’t over-engineering.
The goal should be to create the simplest design that still preserves clear responsibilities and boundaries.
回复 共享 -AJacobs- • 18天前
Any reason to believe that this is better than ponytail?
回复 共享 Dolo12345 • 18天前 前 1% 最受欢迎的评论者
sol max is amazing don’t touch a thing tibo
回复 共享 abazabaaaa • 17天前
I probably wouldn’t write the word “delete” especially not the way you have it written
回复 共享 JD3Lasers • 15天前
Rm -rf / The simplest method was no method.
NaturallyFarOut • 14天前
always has been
EmilPlaysGames • 18天前
can someone tell me is this actually good
nicky_factz • 18天前
There’s nothing technically wrong with any of these rules as an agents.md set, but all this is simply guidance if you already inject similar rules elsewhere or have a lot of compaction it’s going to lose this like it would any nuance over time.
A lot of these prompts work fine in isolation because it’s good advice, doesn’t mean the agent won’t wander or get context poisoning from other parts of your harness
SlimyResearcher • 18天前
You have to tell it speciifcally to use Occam's razor. Otherwise, it may still over-engineer even if the instructions are in the AGENTS.md file.
2053_Traveler • 17天前
Isn’t Occam’s razor most popularly used to refer to simple explanations being best? In principle, and in truth maybe it works. But I wonder if something much shorter like “Ruthlessly practice YAGNI” would be better
nicky_factz • 18天前
I hear ya, I think a lot of people have more of a self inflicted harness problem than just the model itself however. They installed 300 skills and 15 plugins that all repeat the same guidance in different flavors, or worse, they conflict, all from the 5.4 days and need to loosen up the guardrails first then look for this kind of tweak, because sol has not been an issue for me with over engineering like at all, I had some problems on launch with ultra mode but general sol seems very capable at medium/high OOTB and mostly on a clean setup too.
These are solid rules and Occam’s razor is definitely a good well known concept for an LLM to pick up on so I may throw those words into my plugin cuz I like it.
adolf_twitchcock • 17天前
It's not.
It could have been a simple sentence. Mentioning occams razor doesn't do anything.
BlacksmithLittle7005 • 15天前
Just put karpathy rules in your AGENTS md, was enough for me
TorgoNUDH0 • 17天前
I use a multi dimensional epistemic analysis dual adversarial super review/verifier stage. I put all the eponymous laws in there with a bit of hydratation crawl on arxiv. This cause my workflow to loop forever. I once caught it authenticate into a system jusg to prove a point to the planning agent. So add a fail fast clause
Historical-Donut-918 • 17天前
What?
TalosStalioux • 16天前
Isn't using DRY principles enough?
[已删除] • 18天前
版主已移除评论
EmilPlaysGames • 18天前
not profitable for open ai if you’re on plan, it’s just a deficit and they would actually save by making it under-engineered
SlimyResearcher • 18天前
I found that simply adding it to AGENTS.md doesn't work, but when you tell it specifically to use Occam's razor and give it the instructions above, it does produce simpler designs.
[已删除] • 18天前
版主已移除评论
Fit-Palpitation-7427 • 18天前
So whats your alternative ? Terra? Luna? Sol medium?
ComSenseisnotCommon • 18天前
You are correct people who build these agents in that way don’t understand they using the wrong model. Idk if it’s fomo or some syndrome that because it’s considered the highest marketed of something it’s just always the best and efficient that people force everything down it.
创建于 2011年10月31日 公共 38万1.8万 R/CODEX 规则 1 Respect 2 Be relevant to the Codex technology 3 High information posts get highest priority 4 More r/Codex comment karma = higher posting priority 5 The moderation of r/Codex is partly automated 6 For problem reports with low detail, use Megathreads. For high detail, post to the feed. 7 Check previous posts before posting 8 Use the right flair 9 Don't use bots. Read up on BotBouncer 10 Attack OpenAI's practices. not its people. COMMUNITY RESOURCES
These are some tools and links and ideas supplied by the community that might help you.
Low noise r/Codex Low noise r/Codex Codex Reset Predictor Codex Reset Predictor Complaint Feed Filter Complaint Feed Filter OTHER CODEX COMMUNITIES r/OpenaiCodex 19,229 位成员 版主 向版主发送消息 u/pollystochastic
Moderator u/bot-bouncer u/AutoModerator u/floodassistant u/comment-nuke u/dexterthebot u/dexythebot u/codex-dequeuer u/codex-megathread 查看所有版主 已安装的应用 dexythebot Comment Mop codex-dequeuer codex-megathread Flooding Assistant Bot Bouncer dexterthebot Reddit 规则 隐私政策 用户协议 你的隐私选择 辅助功能 Reddit, Inc. © 2026。保留所有权利。 折叠“导航” 创建社区 REDDIT 上的游戏 定制信息流 创建自定义信息流 最近访问 r/opencodeCLI r/chrome r/Notion r/todoist 社区 管理社区 资源 关于 Reddit 广告 开发者平台 Reddit Pro 测试版 帮助 博客 职业 新闻 Reddit 最佳 Reddit 规则 隐私政策 用户协议 你的隐私选择 辅助功能 Reddit, Inc. © 2026。保留所有权利。
GPT-5.6 Sol