This folder contains the Software 3.0 development reference set for AI builders.
The documents in this folder summarize and operationalize key ideas from Andrej Karpathy's Software 3.0 framing, then provide multiple consumption formats for different use cases:
- Full deep-dive reading
- Concise implementation reference
- Abstract overview
- Retrieval-friendly knowledge base
- Visual interactive cheatsheet
-
software-30-developer-guide.md- Full guide with context, principles, practical methods, and phased framework.
- Best for first-time deep reading and strategic planning.
-
software-30-developer-guide-concise.md- Condensed version focused on actionable steps and quick decision loops.
- Best for day-to-day implementation and team syncs.
-
software-30-developer-guide-abstract.md- High-level abstract of the guide.
- Best for quick orientation or sharing the core thesis.
-
software-30-knowledge-base.md- Structured, retrieval-oriented knowledge base format.
- Best for AI assistant grounding, semantic retrieval, and internal RAG workflows.
-
software-30-cheatsheet.html- Visual interactive cheatsheet.
- Best for quick browsing and workshop presentation.
- Live link: https://sw3dev.github.io/aiDevelopersGuide/software-30-cheatsheet.html
- Start with
software-30-developer-guide-abstract.md - Read
software-30-developer-guide.md - Keep
software-30-developer-guide-concise.mdas your operational reference - Use
software-30-knowledge-base.mdfor AI-tool ingestion and retrieval - Use
software-30-cheatsheet.htmlfor visual review and training sessions
-
Individual developer
- Use the full guide to align your mental model, then run projects through the concise checklist and go/no-go tests.
-
Engineering team lead
- Use the concise guide in planning/review meetings and turn the framework into team standards.
-
AI tooling / RAG pipeline
- Ingest the knowledge base file as canonical context for assistants and internal copilots.
- Treat this folder as a living knowledge set.
- Revisit and update content at major model-release milestones.
- Keep terms and examples consistent across all five files when editing.