Skip to content
Skills Library
Programming · Review & audit

zero-defect

/zero-defect

Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.

Repository
maestro ↗
Licence
MIT
Last repository change
29.04.2026

Assessment and security

90/ 100Class: good
Format25 / 25
Frontmatter with name and description, valid name, description up to 1,024 characters, name matching the folder.
Discoverability25 / 25
Description explains when to use the skill, has a reasonable length and uses third person.
Content25 / 35
At least 150 words and at most 500 lines, headings, step lists, examples or code.
Hygiene15 / 15
No placeholders such as TODO, no Windows paths, with a licence.
Riskno signals detected in the scan
Files in this package
1
Scripts
0
HTML comments
0
URLs in SKILL.md
0
Deprecation

No signals detected. Repository changed on 29.04.2026, without references to retired models or APIs.

Licence

MIT, open: use and modify while retaining author attribution.

What it does and when to use it

Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.

Arguments

/zero-defect [task or area]
Original author description

Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable.

How it works

  1. MANDATORY PREPARATION
Original SKILL.md headings · 76 lines, 658 words
SKILL.md preview
---
name: zero-defect
description: "Use when you need maximum precision on a critical task — production deployments, security-sensitive code, financial calculations, or any work where mistakes are unacceptable."
argument-hint: "[task or area]"
category: fix
version: 2.0.0
user-invocable: true
---

## MANDATORY PREPARATION

Invoke /agent-workflow — it contains workflow principles, anti-patterns, and the **Context Gathering Protocol**. Follow the protocol before proceeding — if no workflow context exists yet, you MUST run /teach-maestro first.

---

Activate maximum precision mode for the current session. This command establishes execution-time discipline — not for the workflow design, but for **how the agent itself operates**. Every response, every code change, every claim must pass the zero-defect gate.

This is model-agnostic. It works with Claude, Gemini, GPT, Codex, or any AI agent.

### The 8 Precision Rules

Follow these for the **entire session** after this command is invoked:

| # | Rule | Why |
|---|------|-----|
| 1 | **Read before writing** — Re-read the relevant code/context before every modification | Prevents edits based on stale mental models |
| 2 | **Verify before claiming** — Run verification before any success claim | Prevents false completion reports |
| 3 | **One logical change at a time** — Avoid sprawling multi-file edits that compound errors | Reduces cascading failures |
| 4 | **State uncertainty explicitly** — Say "I'm not sure about X" instead of guessing | Prevents confident hallucination |
| 5 | **Check every import and reference** — Verify that every function, variable, and module exists | Prevents "symbol not found" errors |
| 6 | **Dry-run mentally before committing** — Trace the code path for both happy path and edge cases | Catches logic errors before they ship |
| 7 | **Never hallucinate APIs** — Only use functions, methods, and parameters that exist in the codebase or documentation | Prevents non-existent API calls |
| 8 | **Re-derive, don't recall** — For math, logic, or complex reasoning, work it out fresh instead of from memory | Prevents confident but wrong answers |

### The Pre-Commit Gate

Before claiming ANY work is complete, pass every item:

- [ ] Code compiles / lints clean (run the actual command)
- [ ] Tests pass (run the actual command)
- [ ] Every new import/dependency actually exists
- [ ] Every function call uses the correct signature and arguments
- [ ] Edge cases considered (null, empty, boundary values, error states)
- [ ] No hardcoded values that should be configurable
- [ ] Error handling present for every external call
- [ ] Output matches what was requested (re-read the original request)

### Anti-Pattern Table

| Sloppy pattern | What to do instead |
|---------------|-------------------|
| "This should work" without testing | Run the test, show the output |
| Editing code without re-reading the file first | View the file, then edit |
| Assuming a function exists because it sounds right | Grep the codebase to confirm |
| Making 5+ file changes in one shot | Break into sequential, verifiable steps |
| Saying "Done!" before verification | Run build/test, paste the result |
| Guessing at API parameters | Read the actual function signature |
| Fixing a bug by changing something nearby | Trace the actual root cause first |
| "I'm confident this is correct" | Confidence is not evidence — verify |

### Session Directive

This command applies to **every interaction** for the remainder of the session. There are no exceptions. The rules apply to:

- Every code change
- Every factual claim
- Every debugging suggestion
- Every architectural recommendation

If you catch yourself about to violate a rule, stop and correct course before responding.

### Recommended Next Step

After the critical work is done, run `/evaluate` to review the output quality, or `/refine` for a final polish pass.

**NEVER**:

- Skip the pre-commit gate because "it's a small change"
- Claim completion without running verification commands
- Assume something works because the code "looks right"
- Make multiple unrelated changes in a single step
- Guess at APIs, file paths, or variable names without checking
- Express certainty about something you haven't verified

Versions

The database has no other skills named zero-defect.

Database snapshot: 13.11.2026 · package version 3dfba8e85e54 (SHA-256 digest of the entire package)

Downloads in the last 30 days: 0 · ranking

Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.

Similar skills

  • 100hotfix
    Apply a hotfix for critical production issues. Use for security vulnerabilities or bugs that prevent core functionality. Triggers on "hotfix", "emergency fix", "critical fix", "production bug".
  • 90game-code-review
    Use when reviewing game code or architecture, especially Unity C#, Firebase rules/functions, JavaScript/TypeScript tooling, gameplay systems, UI code, async code, dependency injection, tests, performance hot paths, and security-sensitive backend code.

Feedback and reports

Your message goes to Bartosz Sokoliński. An email address is needed only for a reply. See the privacy policy.