chore: remove conflicting artifact instruction

This commit is contained in:
Muhammad Ubaid Raza
2026-02-25 01:50:33 +05:00
parent 4dea294547
commit 59d26c54fa
8 changed files with 8 additions and 8 deletions

View File

@@ -39,7 +39,7 @@ Browser automation, UI/UX and Accessibility (WCAG) auditing, Performance profili
- Never navigate to production without approval.
- Retry Transient Failures: For click, type, navigate actions - retry 2-3 times with 1s delay on transient errors (timeout, element not found, network issues). Escalate after max retries.
- Errors: transient→handle, persistent→escalate
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -32,7 +32,7 @@ Containerization (Docker) and Orchestration (K8s), CI/CD pipeline design and aut
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
- Always run health checks after operations; verify against expected state
- Errors: transient→handle, persistent→escalate
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -35,7 +35,7 @@ Technical communication and documentation architecture, API specification (OpenA
- Verify parity: on delta for updates; against source code for new features
- Never use TBD/TODO as final documentation
- Handle errors: transient→handle, persistent→escalate
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -47,7 +47,7 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
- Security issues → fix immediately or escalate
- Test failures → fix all or escalate
- Vulnerabilities → fix before handoff
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -121,7 +121,7 @@ delegation_validation:
* ask_questions: Only as fallback and when critical information is missing
- Stay as orchestrator, no mode switching, no self execution of tasks
- Memory: Use memory create/update when discovering architectural decisions, integration patterns, or code conventions.
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Direct answers in ≤3 sentences. Status updates and summaries only. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -58,7 +58,7 @@ gem-implementer, gem-browser-tester, gem-devops, gem-reviewer, gem-documentation
- Stay architectural: requirements/design, not line numbers
- Halt on circular deps, syntax errors
- Handle errors: missing research→reject, circular deps→halt, security→halt
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -90,7 +90,7 @@ Codebase navigation and discovery, Pattern recognition (conventions, architectur
- Include code snippets for key patterns
- Distinguish between what exists vs assumptions
- Handle errors: research failure→retry once, tool errors→handle/escalate
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>

View File

@@ -39,7 +39,7 @@ Security auditing (OWASP, Secrets, PII), Specification compliance and architectu
- Use tavily_search ONLY for HIGH risk/production tasks
- Review Depth: See review_criteria section below
- Handle errors: security issues→must fail, missing context→blocked, invalid handoff→blocked
- Artifacts: Generate all artifacts under docs/plan/{plan_id}/
- Communication: Output ONLY the requested deliverable. For code requests: code ONLY, zero explanation, zero preamble, zero commentary. For questions: direct answer in ≤3 sentences. Never explain your process unless explicitly asked "explain how".
</operating_rules>