fking ai
This commit is contained in:
@@ -127,3 +127,9 @@ When your current role requires capabilities from another tier, use `activate_sk
|
||||
- When managing complex, multi-file Track implementations.
|
||||
- When creating or refining conductor tracks (MUST follow Surgical Spec Protocol).
|
||||
</triggers>
|
||||
|
||||
## Anti-Patterns (Avoid)
|
||||
|
||||
- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
|
||||
- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
|
||||
|
||||
@@ -162,6 +162,6 @@ Focus: {One-sentence scope}
|
||||
- Do NOT batch commits - commit per-task
|
||||
- Do NOT skip phase verification
|
||||
- Do NOT use native `edit` tool - use MCP tools
|
||||
- DO NOT SKIP a TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
|
||||
- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
|
||||
|
||||
@@ -193,6 +193,6 @@ When all tasks in a phase are complete:
|
||||
- Do NOT batch commits - commit per-task
|
||||
- Do NOT skip phase verification
|
||||
- Do NOT use native `edit` tool - use MCP tools
|
||||
- DO NOT SKIP a TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
|
||||
- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
|
||||
@@ -107,3 +107,14 @@ If you cannot complete the task:
|
||||
2. Explain exactly why you cannot proceed
|
||||
3. List what information or changes would unblock you
|
||||
4. Do NOT attempt partial implementations that break the build
|
||||
|
||||
## Anti-Patterns (Avoid)
|
||||
|
||||
- Do NOT implement code directly - delegate to Tier 3 Workers
|
||||
- Do NOT skip TDD phases
|
||||
- Do NOT batch commits - commit per-task
|
||||
- Do NOT skip phase verification
|
||||
- Do NOT use native `edit` tool - use MCP tools
|
||||
- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
|
||||
- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
|
||||
|
||||
@@ -101,3 +101,13 @@ If you cannot analyze the error:
|
||||
1. Start your response with `CANNOT ANALYZE:`
|
||||
2. Explain what information is missing
|
||||
3. List what would be needed to complete the analysis
|
||||
|
||||
## Anti-Patterns (Avoid)
|
||||
|
||||
- Do NOT implement code directly - delegate to Tier 3 Workers
|
||||
- Do NOT skip TDD phases
|
||||
- Do NOT batch commits - commit per-task
|
||||
- Do NOT skip phase verification
|
||||
- DO NOT SKIP A TEST IN PYTEST JUSTS BECAUSE ITS BROKEN AND HAS NO TRIVIAL SOLUTION OR FIX.
|
||||
- DO NOT SIMPLIFY A TEST JUST BECAUSE IT HAS NO TRIVAL SOLUTION TO FIX.
|
||||
- DO NOT CREATE MOCK PATCHES TO PSUEDO API CALLS OR HOOKS BECAUSE THE APP SOURCE WAS CHANGED. ADAPT TESTS PROPERLY.
|
||||
|
||||
Reference in New Issue
Block a user