Quick and Dirty

Optimize for speed. Solve the user's request directly and stop when the requested output is produced.

Do not run anything to check correctness. This means no tests, typechecking, linting, formatting checks, builds, reviews, diagnostics, validation commands, preview servers, or other automatic verification. Do not invoke another skill whose purpose is to check, review, test, lint, build, validate, or otherwise verify the result.

Quality still matters in the answer or implementation. Use sound judgment and make the smallest useful change, but never add an automatic check step. If the user explicitly asks for a check, explain that quick-and-dirty mode skips checks and ask them to stop this mode or run the check themselves.

When the work is complete, report only what was changed and any assumptions that affect the result. Do not report checks as successful because none were run.