Show Menu
Cheatography
  1. Home >
  2. Programming >

AI Engineering Usage Cheat Sheet (DRAFT) by

Match the task, protect your credit reserve, and stop when two approaches make no progress. A quick reference tested against common engineering scenarios.

This is a draft cheat sheet. It is a work in progress and is not finished yet.

1. Start with the task

Known command or obvious quick fix
Editor, terminal or script.
Build or test fails
Rerun the failing check; read the first error. Unclear? Gemini CLI.
Write, plan or compare options
Gemini Web, with approved context.
Explain code or make a bounded change
Gemini CLI, even across several files.
Complex problem remains unresolved
Consider Kiro. Check the middle column first.
CLI = comman­d-line app. Use tools approved for your data.

No match? Use this order

Standard tool can do it in 10 minutes?
Use it. Otherwise:
No local files or commands needed?
Gemini Web. Otherwise:
Gemini CLI has the access and quota?
Try it. Kiro is a deliberate escala­tion.
Quota = usage allowance. For an incident, follow the runbook and involve on-call first.
  

2. Before starting Kiro

Use it for a result worth the cost.
Other tools cannot finish the task; expect 30+ minutes saved or signif­icantly lower risk.
Write three lines:
Finish: [specific result]
Done: [obser­vable check]
Stop: [time/­spe­nding limit]
Check remaining allowance and permis­sions.
Watch actual usage; a prompt is not a spending cap.
10 / 30 minutes are guidel­ines. Urgency alone does not justify Kiro.

Set today's Kiro allowance

At the start of the day:
1. Set aside 2,000 for urgent work.
2. Divide the rest by workdays left.
3. Cap at 300.
Before each task: deduct today's spend.
Allowance used? Gemini or standard tools.
Balance 2,000 or less? No routine Kiro.
Reserve spending is your decision; agents must ask.
Personal example: 10,000­/month, 20 workdays. 500/day spends all; 400/day keeps the reserve. Past burn: 10k in 3-5 days. Credits measure Kiro usage.
  

3. Stuck? Check progress

Same failure, no new evidence?
Try a different approach.
Two approaches without progress?
Stop. Report what you tried, evidence, blocker and one next step.
Progress means:
A useful new fact, a smaller reprod­uction of the failure, or a passing check.
Also stop at the limit, missing permis­sion, or work beyond the agreed task. No automatic Kiro escala­tion.

Copy this brief | Any task

Deliver [specific result].
Use [relevant eviden­ce/­con­text].
Stay within [files­/topic; exclus­ions].
Done when [obser­vable check].
Stop at [time; credits if visible].

Use approved tools. Make changes only as needed and verify the result. Stop at the limit or after two approaches without progress.

Ask before adding work, switching to Kiro or spending the reserve. Report result, checks and blockers.
Fill every bracket. Works for analysis, writing or code.

Before you move on

Review the result. Is it safe to use?
Record the cost. Was it worth it?
Recheck the balance. What is left?
Personal operating guide | v3.1