Nautilo engineering skill pack
Download the same review skills we use to keep Nautilo useful, coherent, and production-safe. They work in any coding agent that can read Markdown.
What they teach
Experience finds the hoops. Systems traces the code, state, deployment, and failure paths. Overengineering cuts what the evidence does not justify.
What is standing between this person and the change they came to make?
Remove hoops, exposed machinery, dead ends, false completion, bad tool contracts, and arbitrary limits—then write the shorter replacement journey.
Use when: Reviewing an idea, workflow, interface, agent tool, specification, plan, or working feature.
Read and downloadWhat runs now, who owns the truth, and what is the least we need to change?
Ground the design in current code, canonical state, existing mechanisms, ownership, sovereignty, failure, deployment, migration, and recovery.
Use when: Reviewing an idea, architecture, technical design, specification, plan, or implementation.
Read and downloadWhat can we delete, defer, or prove with one basic complete path first?
Cut premature machinery, turn horizontal component plans into usable vertical waves, and make every abstraction earn its place.
Use when: A plan is growing steps, infrastructure, abstractions, or deployment machinery faster than evidence warrants them.
Read and download