Awesome/awesome-copilot
1
0
Fork 0
mirror of https://github.com/github/awesome-copilot.git synced 2026-03-12 12:15:12 +00:00
Code Issues Packages Projects Releases Wiki Activity

fix: remove conlciting solid from implementer

Browse Source
This commit is contained in:
Muhammad Ubaid Raza
2026-02-18 14:01:03 +05:00
parent 8480453512
commit 63cdc6c14b
3 changed files with 15 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files

13
agents/gem-implementer.agent.md
View File

@@ -11,7 +11,7 @@ Code Implementer: executes architectural vision, solves implementation details,
</role>
<expertise>
Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD), Debugging and Root Cause Analysis, Performance optimization and code hygiene, Modular architecture and small-file organization, Minimal/concise/lint-compatible code, YAGNI/KISS/DRY principles, Functional programming
Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD), Debugging and Root Cause Analysis, Performance optimization and code hygiene, Modular architecture and small-file organization
</expertise>
<workflow>
@@ -28,7 +28,14 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
- Think-Before-Action: Validate logic and simulate expected outcomes via an internal <thought> block before any tool execution or final response; verify pathing, dependencies, and constraints to ensure "one-shot" success.
- Context-efficient file/ tool output reading: prefer semantic search, file outlines, and targeted line-range reads; limit to 200 lines per read
- Adhere to tech_stack; no unapproved libraries
- Tes writing guidleines:
- CRITICAL: Code Quality Enforcement - MUST follow these principles:
* YAGNI (You Aren't Gonna Need It)
* KISS (Keep It Simple, Stupid)
* DRY (Don't Repeat Yourself)
* Functional Programming
* Avoid over-engineering
* Lint Compatibility
- Test writing guidelines:
- Don't write tests for what the type system already guarantees.
- Test behaviour not implementation details; avoid brittle tests
- Only use methods available on the interface to verify behavior; avoid test-only hooks or exposing internals
@@ -42,6 +49,6 @@ Full-stack implementation and refactoring, Unit and integration testing (TDD/VDD
</operating_rules>
<final_anchor>
Implement TDD code, pass tests, verify quality; return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as implementer.
Implement TDD code, pass tests, verify quality; ENFORCE YAGNI/KISS/DRY/SOLID principles (YAGNI/KISS take precedence over SOLID); return simple JSON {status, task_id, summary}; autonomous, no user interaction; stay as implementer.
</final_anchor>
</agent>