Rules written into the prompts
- Cite file and line for every finding.
- Separate must-fix defects from optional suggestions.
- Do not rewrite the change. Show the smallest fix.
← Home / Sectors / Engineering
Sector 09 of 14 — ♐︎ Sagittarius — θ 205.7°–231.4°
Review, documentation and delivery prompts that are specific to the line and honest about severity. A pack of sixty prompts that trains your AI to work as a staff software engineer carrying out code review, written separately for whichever AI you run.
Fig. 01 — The pack map
Every area of engineering work is covered at every tier: four Point prompts for quick tasks, three Line, two Plane and one Solid workflow. Six areas of ten makes sixty.
| Area of work | IPoint | IILine | IIIPlane | IVSolid | Total |
|---|---|---|---|---|---|
| 01Code review and refactoring | 4 | 3 | 2 | 1 | 10 |
| 02Technical documentation | 4 | 3 | 2 | 1 | 10 |
| 03Incident post-mortems | 4 | 3 | 2 | 1 | 10 |
| 04Release notes and changelogs | 4 | 3 | 2 | 1 | 10 |
| 05Architecture decision records | 4 | 3 | 2 | 1 | 10 |
| 06Test planning | 4 | 3 | 2 | 1 | 10 |
| Whole pack | 24 | 18 | 12 | 6 | 60 |
Fig. 02 — Specimen
The same task, re-cut live for your AI and for each tier. Watch what each tier adds.
Fig. 03 — The standard
Review is the last check before this code runs in production. A defect missed now costs far more to fix later.
Rules written into the prompts
What “done” means
When a person steps in
Fig. 04 — UK rules
Every prompt in this pack tells your AI which UK rules apply to the work, and to apply them only where they are relevant. It never lets the AI claim that work complies with a law: points for a qualified person are marked [REQUIRES VERIFICATION].
UK rules built into the prompts
Specialist viewpoints in every Solid prompt
Checks before anything is released
These prompts help your team work to UK rules. They are not legal, tax or financial advice, and a qualified person must review the output before it is relied on.