Loading...
Loading...
Found 74 Skills
Analyzes codebases to generate comprehensive documentation including structure, languages, frameworks, dependencies, design patterns, and technical debt. Use when user says "analyze repository", "understand codebase", "document project", or when exploring unfamiliar code.
Systematically analyze codebase structure, complexity, dependencies, and architectural patterns to understand project organization
Help users build and scale internal platforms and technical infrastructure. Use when someone is deciding whether to build vs buy tooling, designing developer platforms, creating shared services, or managing technical debt at scale.
Expertise in Senior Principal Engineering refactoring. Use when you need to eliminate technical debt, remove "AI Slop," simplify complex logic, and ensure DRY code.
Systematically evaluate architecture decisions, document trade-offs, and select appropriate patterns. This skill should be used when the user asks about 'architecture decision', 'ADR', 'design pattern selection', 'technology choice', or needs to evaluate architectural trade-offs. Keywords: architecture, ADR, patterns, trade-offs, technical debt, quality attributes, decision record.
Refactor code for quality, reduce technical debt, and improve maintainability. Use for cleanup tasks and code improvements.
Apply safe refactoring patterns to improve code structure without changing behavior. Use when cleaning up code, reducing technical debt, or improving maintainability.
Decision-making framework for software development, Y Combinator / Silicon Valley style. Based on real principles from Paul Graham, Sam Altman, Michael Seibel, Patrick Collison, and Brian Chesky. Use when: - Developing features or products - Making technical decisions (what to do, how, when) - Prioritizing work (P0, P1, P2) - Evaluating whether to refactor or patch - Deciding on technical debt - Evaluating whether to add tests, CI/CD, or automation - Any architecture or engineering decision Triggers: development, code, feature, refactor, architecture, prioritize, technical decision, what to do first, technical debt, tests, CI/CD, sprint, backlog
Audit rapidly generated or AI-produced code for structural flaws, fragility, and production risks.
Systematic detection and prioritization of neglected code quality issues: stale TODOs, unused imports, deprecated functions, high complexity, dead code. Use when user requests "code cleanup", "find TODOs", "technical debt scan", or "quality of life fixes". Do NOT use for bug fixing (use systematic-debugging), feature work (use test-driven-development), or formatting-only (use code-linting).
You are a technical debt expert specializing in identifying, quantifying, and prioritizing technical debt in software projects. Analyze the codebase to uncover debt, assess its impact, and create acti
Improve code quality, reduce technical debt, restructure for maintainability