code▌

Evaluate code review feedback with technical rigor before implementing, avoiding performative agreement and blind implementation. \n \n Verify feedback against actual codebase behavior, test coverage, and architectural context before proceeding \n Ask for clarification on unclear items before implementing anything; partial understanding leads to wrong fixes \n Push back on suggestions that break functionality, lack context, violate YAGNI, or conflict with established decisions using technical re

Webflow custom code: register (store script) → apply (attach to site). Inline scripts only via MCP (max 10,000 chars).

Process: Explore → Plan → Code → Commit

Expert guidance for writing Python code in n8n Code nodes.

When reviewing Encore Go code, check for these common issues:

Optional Mermaid diagrams for complex code structures. Choose the diagram type based on the programming paradigm. Code diagrams show the internal structure of a single component.

Navigate large Rust codebases efficiently using Language Server Protocol.

Combined simplification and review pipeline. This skill orchestrates two sub-skills in sequence:

Clean code reads like well-written prose. Every name reveals intent. Every function tells a story. Every class has a single purpose. The goal isn't just working code—it's code that others can understand quickly, modify safely, and extend confidently.

Systematic code improvement through review, refactoring, and debugging with verification gates.