backprop-guard
Skill4 starsChanged 31 days agoMITView on GitHub
Backpropagate downstream code failures, test rejections, and slop findings into upstream rules, invariants, and AGENTS.md rather than merely patching downstream symptoms.
In this repository47 other files it gives its agents.
- AGENTS.mdAGENTS.md
- anti-slop-engineeringSkill
- anti-slop-engineeringSkill
- api-ergonomics-and-contract-governorSkill
- apple-craft-and-frame-budgetSkill
- apple-craft-and-interaction-physicsSkill
- asset-provenance-guardSkill
- chaos-and-degradation-choreographerSkill
- chromatic-drift-guardSkill
- cognitive-load-and-attention-governorSkill
- comment-budget-guardSkill
- context-window-and-token-economics-architectSkill
- cryptographic-agility-and-secret-lifecycle-gateSkill
- decision-guardSkill
- demock-guardSkill
- design-system-drift-guardSkill
- deterministic-simulation-and-property-testingSkill
- distributed-consensus-and-concurrency-gateSkill
- finops-and-unit-economics-governorSkill
- future-scale-gateSkill
- grumpy-senior-staff-engineerSkill
- honeypot-trap-guardSkill
- house-tell-guardSkill
- install-anti-slopSkill
- llm-eval-and-prompt-injection-fortressSkill
- mandela-guardSkill
- mechanical-sympathy-and-perf-gateSkill
- mechanical-sympathy-profilerSkill
- motion-runtime-guardSkill
- observability-and-slo-architectSkill
- observability-and-slo-gateSkill
- paranoid-principal-architectSkill
- pr-boundary-guardSkill
- privacy-and-data-lineage-gateSkill
- re0-handoff-guardSkill
- reduction-guardSkill
- repo-memory-and-invariant-stewardSkill
- root-fix-gateSkill
- safe-evolution-and-rollout-choreographerSkill
- scientific-fault-isolationSkill
- styleseed-guardSkill
- supply-chain-and-sbom-sentinelSkill
- tagore-guardSkill
- type-level-and-ast-slop-gateSkill
- ui-and-copy-disciplineSkill
- verification-oracle-architectSkill
- zero-downtime-migration-gateSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 3 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈3
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 16
When an AI coding assistant introduces a bug or writes slop, standard workflows only fix the local file.
- Distinctive: line 22
Atomically Apply: Update the invariant ledger so all future agent turns ingest the new constraint at Gate 0.
- Distinctive: line 27
One Canonical Owner: Every backpropagated lesson belongs in exactly one Single Source of Truth (SSOT).
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Upstream Invariant & Rule Backpropagation Guard
Feed errors from output back through the generative layers that produced them, updating upstream invariants so the failure can never recur.
Why This Skill Is Needed & Target State
When an AI coding assistant introduces a bug or writes slop, standard workflows only fix the local file. The prompt, rules, constitution, or missing invariant that permitted the mistake remain untouched. Consequently, subsequent sessions repeat the exact same failure.
The target state is an error backpropagation pipeline:
- Identify the Symptom: Map the failure to its error class (
DEMOCK,MANDELA,REDUCTION,AST_SLOP,SRE_KISS). - Question Upstream Requirements (Elon Step 1): Challenge why the rule or gap existed.
- Pin the SSOT Owner: Direct the invariant into
AGENTS.md,.anti-slop/invariant-ledger.json, or a specific skill file. - Atomically Apply: Update the invariant ledger so all future agent turns ingest the new constraint at Gate 0.
Invariant Rules
- Backprop Before Local Merge: Significant downstream failures must emit an upstream invariant candidate before PR completion.
- One Canonical Owner: Every backpropagated lesson belongs in exactly one Single Source of Truth (SSOT).
- Preserve Generalization: Formulate rules as general behavioral constraints, not hyper-narrow one-off exceptions.
CLI Usage
# Generate backprop record for an observed finding
bunx anti-slop-engineering backprop \
--finding DEMOCK_SILENT_FALLBACK \
--file "src/db/client.ts" \
--line 42 \
--excerpt "catch { return []; }" \
--json
# Atomically commit invariant to .anti-slop/invariant-ledger.json
bunx anti-slop-engineering backprop \
--finding DEMOCK_SILENT_FALLBACK \
--file "src/db/client.ts" \
--line 42 \
--excerpt "catch { return []; }" \
--applyDoes it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

