Skill UI

This skill guides developers on best practices for structuring commits and Pull Requests (PRs). It teaches how to break down large, complex features into small, independent, and reviewable work units. By adhering to these principles, developers keep the reviewer's cognitive load low, improve code quality, and manage version control history effectively.

Apply Robert C. Martin-inspired clean code rules to improve code readability, naming conventions, function design, and responsibilities. This skill ensures everyday implementation quality, readable control flow, and testable code by following established best practices for software development.

This skill applies Steve McConnell's construction rules to software development tasks. It covers routine design, variable usage, class design, control flow, defensive programming, coding standards, and testing. Use it for disciplined software construction to ensure high-quality code implementation.

This skill extracts a checklist from planned work, builds the implementation, and verifies every check with an independent verifier. It is used when the user requests to extract a checklist, build a ticket, or implement a spec. It ensures rigorous testing and proof-based assertions, preventing self-reporting of completion. It involves extracting checks, building the code, and proving each one independently to guarantee quality.