بنقرة واحدة
tdd-strict
Use when high-assurance reliability is required (Bug fixes, Critical Features, Quality Hardening).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
القائمة
Use when high-assurance reliability is required (Bug fixes, Critical Features, Quality Hardening).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when decomposing tasks into parallel sub-tasks or spawning sub-agents. Vendor-agnostic core; load a per-vendor reference for concrete tool names, directory conventions, and invocation syntax.
Use when performing Verification-Driven Development with adversarial approach. Actively challenge assumptions and find weak spots.
Use when performing VDD adversarial review with an opt-in sarcastic, provocative delivery style — a stylistic skin over vdd-adversarial mechanics (exhaustive reporting + objective bar).
Performance critic in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing OWASP security critique in adversarial style (optional sarcastic skin). Part of VDD Multi-Adversarial pipeline.
Use when performing security vulnerability assessment (OWASP, secrets, dependencies, IaC, LLM, API, MCP/agentic) or when "thinking like a hacker" to find exploits.
| name | tdd-strict |
| description | Use when high-assurance reliability is required (Bug fixes, Critical Features, Quality Hardening). |
| tier | 3 |
| version | 1 |
This skill enforces a rigorous, evidence-based TDD cycle designed to eliminate "lucky passes" and "code hallucinations". It is stricter than the standard tdd-stub-first.
[!IMPORTANT] ACTIVATION: This skill replaces the standard TDD cycle. When active, you MUST follow the Strict Cycle below.
You must strictly follow this 4-step loop for EVERY test case.
EXPECTED_FAIL_REASONWrite the test case (or stub) and explicitly comment what exact error it should raise.
# EXPECTED_FAIL_REASON: AssertionError: Expected 200 OK, got 404 because endpoint is not registered.
def test_create_user(client):
resp = client.post("/users", json={"name": "Alice"})
assert resp.status_code == 200
Run the test. It MUST FAIL.
EXPECTED_FAIL_REASON?SyntaxError or ImportError -> Fix the test, do not touch code.Implement ONLY the code required to make the test pass.
try: ... except: pass just to silence errors.[!CRITICAL] Dead Code Rule: If you write a line of code, ask: "If I delete this line, will the current test fail?" If the answer is No, DELETE IT.
EXPLAIN_PASS_REASONRun the test. It MUST PASS.