Multi-layer validation to catch bugs before they escape
中文简介正在准备中。当前显示原文说明。
查看安装方法安装前可以查看交给 AI 代理的指令内容。
MULTIPLE INDEPENDENT VALIDATION LAYERS
Each layer catches what others miss
One check can fail silently. Four layers rarely do.
What: Static analysis, types, linting
Catches: Typos, syntax errors, type mismatches
Run: First, before anything else
What: Individual function/module tests
Catches: Logic errors, edge cases, regressions
Run: After each code change
What: Component interaction tests
Catches: Interface mismatches, data flow errors
Run: After unit tests pass
What: Full system tests, user scenarios
Catches: Missing requirements, workflow bugs
Run: Before claiming complete
Code Change
↓
[Layer 1: Lint/Type Check]
↓ PASS?
[Layer 2: Unit Tests]
↓ PASS?
[Layer 3: Integration Tests]
↓ PASS?
[Layer 4: E2E / Manual Check]
↓ PASS?
Done
Fail at any layer → FIX before proceeding
| Without This Layer | What Escapes |
|---|---|
| No type checks | Undefined calls crash at runtime |
| No unit tests | Logic bugs slip through |
| No integration | Components don't work together |
| No E2E | User workflows broken |
1. Make change
2. Run linter immediately
3. Run affected unit tests
4. Run integration suite
5. Test the actual feature
1. Write failing test first
2. Fix the bug
3. Run all tests (regression check)
4. Verify original symptom gone
1. Write unit tests for new logic
2. Implement feature
3. Add integration tests
4. Verify against requirements
Configure per project:
layer_1:
command: "npm run lint && npm run typecheck"
when: "On save, before commit"
layer_2:
command: "npm run test:unit"
when: "After code changes"
layer_3:
command: "npm run test:integration"
when: "After unit tests pass"
layer_4:
command: "npm run test:e2e"
when: "Before claiming done"
→ Syntax/type error in your code
→ Fix immediately, don't proceed
→ Never commit with lint errors
→ Logic error or regression
→ Check: Did you break something?
→ Check: Is your new test wrong?
→ Fix root cause, not symptoms
→ Interface/contract broken
→ Check: API changes?
→ Check: State management issues?
→ May need to update multiple files
→ User-visible problem
→ Trace back through layers
→ Ask: Which layer SHOULD have caught this?
→ Add test to that layer
pre-action-verifier → Runs before each layerassumption-checker → Validates test assumptionsscope-boundary-checker → Ensures tests cover scoperollback-planner → Ready if pipeline fails还没有评价。欢迎分享你的使用感受。
无需登录即可发表。欢迎分享使用感受、提问，或说明在哪些环境下无法运行。
还没有评论。来写第一条吧。
Complete methodology for preventing AI hallucinations. Use when accuracy is critical and you need Claude to verify before claiming, cite before asserting, and admit uncertainty instead of guessing.
中文简介正在准备中。当前显示原文说明。
Transform rough ideas into solid designs through structured questioning
中文简介正在准备中。当前显示原文说明。
Canvas API Connection Skill
中文简介正在准备中。当前显示原文说明。
Forces every code-related claim to include file:line citations. No citation means the claim must be verified or removed. Use when building documentation, writing code reviews, or any output that others will rely on.
中文简介正在准备中。当前显示原文说明。
Assign confidence scores (0-100) to every claim in a response. Helps users understand which parts are verified facts and which are educated guesses. Use when the user needs to know how much to trust each part of the answer.
中文简介正在准备中。当前显示原文说明。
Forces Claude to extract exact quotes from files before making claims about them. Prevents hallucinations by grounding every statement in actual text from the codebase. Use when working with large files or unfamiliar code.
中文简介正在准备中。当前显示原文说明。