@rafaelobitten: After spending way too many tokens with Codex @OpenAIDevs especially Astra over the past week, I ended up adding these …

X AI KOLs Timeline News

Summary

A developer shares coding guidelines added to AGENTS.md after using Codex to reduce overengineering, improve efficiency, and follow best practices like using open-source libraries and writing meaningful tests.

After spending way too many tokens with Codex @OpenAIDevs especially Astra over the past week, I ended up adding these guidelines to the AGENTS.md in my ~/.codex. They’ve helped a lot with cutting down on overengineering, unnecessary precautions, excessive testing, and rebuilding things that already have solid solutions out there: 1. Prefer reliable, secure open-source libraries over building from scratch; when customization is needed, prefer supported extensions or extension points, and build from scratch only when existing options cannot efficiently meet the project’s requirements. 2. Choose the simplest solution that meets the requirements; avoid overengineering and speculative abstractions. 3. Always check current official API and library documentation; use version-compatible guidance rather than blindly upgrading. 4. Write only tests that provide meaningful confidence and prevent regressions; avoid redundant tests and unjustified release gates.
Original Article
View Cached Full Text

Cached at: 09/16/26, 06:01 AM

After spending way too many tokens with Codex @OpenAIDevs especially Astra over the past week, I ended up adding these guidelines to the AGENTS.md in my ~/.codex.

They’ve helped a lot with cutting down on overengineering, unnecessary precautions, excessive testing, and rebuilding things that already have solid solutions out there:

  1. Prefer reliable, secure open-source libraries over building from scratch; when customization is needed, prefer supported extensions or extension points, and build from scratch only when existing options cannot efficiently meet the project’s requirements.

  2. Choose the simplest solution that meets the requirements; avoid overengineering and speculative abstractions.

  3. Always check current official API and library documentation; use version-compatible guidance rather than blindly upgrading.

  4. Write only tests that provide meaningful confidence and prevent regressions; avoid redundant tests and unjustified release gates.

Similar Articles

@jxnlco: https://x.com/jxnlco/status/2057153744630890620

X AI KOLs Following

This tweet thread discusses best practices for using the Codex coding agent, focusing on durable threads, voice input, steering, queuing, and its expanding capabilities beyond code generation to full computer workflow automation.