Edward 

🤖 El problema no es el agente, es tu repositorio. Comparto el Agent Readiness
Framework: 5 niveles y 9 pilares para preparar tu código para la era de los
agentes de IA.

https://www.cosmoscalibur.com/es/blog/2026/marco-de-preparacion-para-agentes-de-codigo

#AgentesDeIA #FactoryAI #AGENTSmd #IngenieríaDeContexto #Antigravity #Claude

Marco de preparación para agentes de código

Los agentes de código están aquí, y no van a irse. Pero después de meses usándolos —Antigravity, AmpCode, Opencode, el agente de Zed— he llegado a una conclusión incómoda: el problema no suele ser ...

Cosmoscalibur
Mar 7 at 7:04pmWeb
Show threadEdward Mar 7

🤖 The problem isn't the agent — it's your repo. Sharing the Agent Readiness
Framework: 5 levels and 9 pillars to prepare your codebase for the AI agent era.

https://www.cosmoscalibur.com/en/blog/2026/marco-de-preparacion-para-agentes-de-codigo

#AIAgents #FactoryAI #AGENTSmd #ContextEngineering #Antigravity #Claude

Agent Readiness Framework for Coding Projects

Coding agents are here, and they are not going away. But after months of using them —Antigravity, AmpCode, Opencode, Zed’s built-in agent— I have reached an uncomfortable conclusion: the problem is...

Cosmoscalibur
Show threadMathew AttleeMar 7
@cosmoscalibur I feel that AGENTS.md is an anti-pattern. Instead of optimising for the agent, I'd argue it's better practice to have documentation for both humans and agents. https://keleshev.com/ai-equals-true-is-an-anti-pattern
AI=true is an Anti-Pattern

Show threadEdward Mar 7
@codeinabox , following the framework for any other is the common practice, but just for that I liked the pattern that I used with Antigravity, using the rule to read and mantain the readme and docs directory updated (Antigravity not use AGENTS.md or similar).