jimmytoan/ai-coding-survival-guide — explained in plain English
Analysis updated 2026-05-18
Read the context discipline doc to learn when to start a fresh AI chat instead of letting context grow stale.
Use the model selection guide to decide when a cheaper model is enough versus when a stronger model is worth the cost.
Copy the good-vs-bad prompt examples and implementation-plan template to scope AI coding tasks before requesting code.
| jimmytoan/ai-coding-survival-guide | 0xjbb/modulestomped | abhisumatk/epstein_files_rag | |
|---|---|---|---|
| Stars | 34 | 34 | 34 |
| Language | — | C++ | Python |
| Setup difficulty | easy | moderate | moderate |
| Complexity | 1/5 | 4/5 | 3/5 |
| Audience | developer | developer | researcher |
Figures from each repo's GitHub metadata at analysis time.
No installation needed, it is a documentation-only repository read directly on GitHub.
This repository is a practical guide for using AI coding assistants more thoughtfully, particularly in the context of usage-based billing where every AI model call carries a cost. The guide opens with the "Max Power" metaphor, a reference to a cartoon character who insists on doing things the hard way. The point is that many developers use AI tools in ways that produce fast output but also generate fast waste: giant context windows, expensive models for simple tasks, and long iterative loops that undo what was just generated. The core argument is that the most effective use of AI coding tools is not about generating the most code, but about controlling context, selecting the right model for the task, scoping work before handing it to an agent, and reviewing output carefully. The guide describes this as the beginning of "FinOps for AI coding agents," borrowing a cost-management discipline from cloud infrastructure and applying it to AI model usage. The repository includes a set of documents covering specific topics: context discipline (when to start a fresh chat and how to write a useful compacted summary), model selection (using cheaper models for simpler tasks and stronger models for architecture decisions and security-sensitive code), agent mode usage (when delegation makes sense and when it does not), team guidelines, cost observability, and prompt pattern examples showing good and poor formulations side by side. The guide does not promote any specific tool and is described as anti-waste rather than anti-AI. There is no runnable code in the repository. Readers consume it by browsing the docs directory, with a table in the main README pointing to each document by topic.
A practical guide of docs and prompt patterns for using AI coding assistants without wasting tokens, credits, or code review time.
No license file mentioned in the README, so usage terms are unclear.
Setup difficulty is rated easy, with roughly 5min to a first successful run.
Mainly developer.
This repo across BitVibe Labs
Verify against the repo before relying on details.