Expert guidance on software architecture, code quality, debugging, refactoring, and best practices when collaborating with AI coding assistants. Universal across programming languages and frameworks.
NewMaintained
Automatic
◆Coding pack
Last verified 8/6/2026
What it changes
Passed 7 of 22 test cases with the skill, and 7 of 22 without it.
Without skill32%
With skill32%
Checks it passed that the model alone missed
Outlines next steps regarding throughput limits
Suggests unit tests for payment provider instantiation
Outlines systematic root cause analysis for test flakiness
3 fixed4 passed either way12 still failing3 broke
Pass-rate lift
0 pp
Tokens
+26%
Agent turns
0%
Response time
+13%
Model gemini-3.6-flashMeasured 8/6/2026v17 of 22 cases passed with skill
Tokens, turns and time describe resource use, not a dollar price.
See it in action
One of 3 test cases the skill fixed. Same model, same prompt, with and without the skill.
1 of 3
Prompt
We have 15 different payment provider implementations in TypeScript, and we use a 100-line switch statement duplicated across 8 controllers to instantiate them. Show me how to clean this up.
What was checked, without and with the skill
Checked
Without skill
With skill
Recommends a factory design pattern to centralize object creation
Passed
Passed
Presents safe incremental refactoring steps
Passed
Passed
Suggests unit tests for payment provider instantiation
Missed
Passed
case-05 · gemini-3.6-flash · 8/6/2026 · answers are capped and redacted
What's inside
The instructions your model reads when the skill loads.
SKILL.md36 linessingle file
Code Architect
When active, provide thoughtful, structured advice on code-related tasks.
Core Principles
Understand the full context: requirements, constraints, existing codebase, tech stack, performance needs.
Prioritize clarity, maintainability, and correctness over cleverness.
Use step-by-step reasoning for design and debugging.
Suggest tests and edge cases proactively.
Balance ideal architecture with practical constraints (time, existing code).
Recommended Approach
Gather Context: Ask for or reference full relevant code, error messages, requirements, and goals.
Analyze: Identify strengths, issues, risks, and opportunities.
Propose Solutions:
High-level architecture / design patterns
Specific code improvements or refactors
Trade-offs of different approaches
Implementation Guidance: Provide clean, well-commented example code when helpful.
Validation: Suggest how to test the changes and what to watch for.