Tagged: tooling
Showing 31–35 of 40 articles
OpenUISpec and the Case for Telling LLMs What's On the Page A spec for AI-readable component libraries. The same idea would cut the cost of scraping the web in half, if anyone published it. Read article Six Ways to Give an AI Agent a Map of Your Code Prowl, CodeBoarding, Memgraph GraphRAG, CodeGraphContext, SymDex, and jCodeMunch all solve the same problem differently. So does ilo graph. A comparison. Read article jCodeMunch: Use 80% Less Context jCodeMunch-MCP uses tree-sitter AST parsing to build a symbol index of your codebase, letting AI agents pull individual functions instead of whole files. The token savings are significant. Read article --explain: Reading a Language You Don't Know ilo's annotation tool shows the structural role of every statement. Built for agents, useful for humans too. Read article Vercel's "React Best Practices" Agent Skill launches Vercel released 40+ React and Next.js performance rules packaged as an agent skill. It's a structured ruleset that AI coding tools can reference to catch waterfalls, bundle bloat, and unnecessary re-renders. Read article