Results for “codeableconcept”

Generates customizable prompts for scanning codebases to identify and document high-quality code exemplars, supporting multiple programming languages and configurable analysis depth.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling.

Mines a codebase for evidence-backed improvement opportunities, forcing two escalation gates to surface breakthrough ideas, and outputs a ranked portfolio with a plan seed without implementing.

Find deepening opportunities in a codebase, informed by the domain language in CONTEXT.md and the decisions in docs/adr/. Use when the user wants to improve architecture, find refactoring opportunities, consolidate tightly-coupled modules, or make a codebase more testable and AI-navigable.

Write readable, maintainable code through disciplined naming, small functions, and clean error handling. Use when the user mentions "code review", "naming conventions", "function too long", "code smells", "readable code", "boy scout rule", "single responsibility", or "unit test quality". Also trigger when reviewing pull requests for readability, refactoring messy functions, debating comment styles, or improving error handling patterns. Covers SRP, comment discipline, formatting, and unit testing. For refactoring techniques, see refactoring-patterns. For architecture, see clean-architecture.

Codebase Onboarding

Codebase Onboarding

Review an entire codebase for architecture, engineering health, and exploitable risk; generate a prioritized remediation plan, an evidence-anchored system knowledge document, or both.

Design scalable distributed systems using structured approaches for load balancing, caching, database scaling, and message queues.

Shared vocabulary for designing deep modules — a small interface hiding a lot of behavior. Use when designing or improving a module's interface, deciding where a seam belongs, deciding whether to extract or merge modules, or making code more testable.

Craft messages that are understood, remembered, and drive action using the SUCCESs framework (Simple, Unexpected, Concrete, Credible, Emotional, Stories).

Transforms working code into clean, readable, and maintainable code following Robert C. Martin's principles.

Design MOOCs with scalable engagement. TRIGGERS - Use when user needs help with mooc-design related tasks.

Analyze an unfamiliar codebase and generate a structured onboarding guide with architecture map, key entry points, conventions, and a starter CLAUDE.md. Use when joining a new project or setting up Claude Code for the first time in a repo.

Writing maintainable code - readability principles, SOLID patterns applied pragmatically, and the judgment to know when rules should bendUse when "code quality, clean code, readability, naming, SOLID, refactor, code review, best practices, maintainable, how should I structure, clean-code, solid, readability, maintainability, code-review, naming, functions, principles" mentioned.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.