Real-world guides and resources for learning how software engineering and leadership works in a post-AI world.
🌐 Live site: path.kilo.ai
This is a comprehensive guide to agentic engineering—the practice of working effectively with AI coding agents. Whether you're an engineer learning to prompt effectively, a team lead integrating agents into workflows, or an executive building an adoption strategy, there's a path for you.
This is a community project. We're building this together because the field moves fast and no single perspective captures everything. Your experience matters—whether you've been using AI tools for years or just started last week.
- Introduction — What agentic engineering is, how agents work, and emerging trends
- For Engineers — Getting started, task decomposition, and best practices
- For Team Leads — Adopting tools, measuring impact, and quality assurance
- For Executives — Strategic vision, ROI frameworks, and security compliance
- Use Cases — Planning, implementation, deployment, and documentation
- Governance — Security review, accountability, and quality gates
- Appendices — Glossary, reading list, and prompt templates
Built with Astro and Starlight, styled with Catppuccin.
# Install dependencies
bun install
# Start dev server
bun dev
# Build for production
bun build
# Preview production build
bun previewWe'd love your help making this resource better. There are many ways to contribute:
- Found a typo or broken link? Open a PR directly—no issue needed
- Have a resource to share? Add it to the relevant page's Resources section
- Spotted outdated info? Let us know or fix it yourself
- New content — Have expertise in an area we haven't covered? We want it
- Real-world examples — Case studies, war stories, and lessons learned are gold
- Translations — Help make this accessible to more people
- Tooling improvements — Better search, navigation, or accessibility
- Check existing issues — Someone might already be working on it
- Open an issue first for larger changes—let's discuss before you invest time
- Fork and PR — Standard GitHub flow
- Keep it practical — We value real-world experience over theory
See CONTRIBUTING.md for detailed guidelines.
This isn't just documentation—it's a conversation. Join us:
- Discord — Ask questions, share wins, discuss what's working
- GitHub Discussions — Longer-form conversations and proposals
- GitHub Issues — Bug reports and feature requests
Be excellent to each other. We're all figuring this out together. Respectful disagreement is welcome; personal attacks are not.
Apache 2.0 — Use it, build on it, share it.