code▌

Simple, pragmatic, opinionated. Only what matters for writing production-grade python code.

Expert code review of git changes with focus on SOLID violations, security risks, and actionable improvements. \n \n Analyzes current git diff for SOLID principle violations, architecture smells, and removal candidates using structured checklists \n Scans for security risks including injection, authentication gaps, race conditions, and unsafe deserialization with exploitability assessment \n Flags code quality issues: error handling gaps, N+1 queries, boundary condition bugs, and performance hot

When explaining code, always include: \n \n Start with an analogy : Compare the code to something from everyday life \n Draw a diagram : Use ASCII art to show the flow, structure, or relationships \n Walk through the code : Explain step-by-step what happens \n Highlight a gotcha : What's a common mistake or misconception? \n \n Keep explanations conversational. For complex concepts, use multiple analogies.

Production-grade code standards emphasizing correctness, crash-safety, and Rust idioms over convenience. \n \n Prioritizes data integrity: crash on invalid state rather than corrupt data; assert invariants aggressively; handle all errors explicitly \n Rust-specific patterns: make illegal states unrepresentable, use exhaustive pattern matching and enums over strings, minimize allocations \n Comments document why , not what ; avoid temporal markers, AI conversation references, and code-repeating e

Comprehensive software craftsmanship guide based on Robert C. Martin's "Clean Code: A Handbook of Agile Software Craftsmanship", updated with modern corrections where the original 2008 advice has been superseded. Contains 48 rules across 10 categories, prioritized by impact to guide code reviews, refactoring decisions, and new development. Examples are primarily in Java but principles are language-agnostic.

Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. \n \n Analyzes recently modified code and applies refinements following project-specific standards from CLAUDE.md, including ES modules, explicit type annotations, and proper error handling patterns \n Enhances readability by reducing unnecessary complexity, eliminating redundant abstractions, and replacing nested ternaries with switch statements or if/else chains \n Preserves exact func

Refactor code while preserving behavior, improving clarity, and reducing complexity. \n \n Covers five core refactoring patterns: Extract Method, DRY principle removal, conditional-to-polymorphism conversion, parameter object introduction, and SOLID principle application \n Includes behavior validation workflow with pre-refactoring analysis, post-refactoring testing (unit, type, lint, snapshot), and change documentation \n Provides refactoring checklist covering function length, parameter count,

Skill by ara.so — Daily 2026 Skills collection.

Evaluates Next.js App Router code against best practices for Server Components, Client Components, Server Actions, caching strategies, and production-readiness criteria. Produces actionable findings categorized by severity with concrete code examples. Delegates to typescript-software-architect-review agent for architectural analysis.

Language-agnostic reference for SOLID principles, design patterns, DRY, KISS, and clean code fundamentals. \n \n Covers seven rule categories prioritized by impact: SOLID principles, core principles (DRY, KISS, YAGNI), design patterns, code organization, naming, functions, and documentation \n Includes 23 rules across SOLID (5), core principles (8), and design patterns (8), with 4 additional categories planned \n Provides quick reference tables, TypeScript code examples, and an audit output form