Loading...
Loading...
Found 58 Skills
The practice of restructuring and simplifying code continuously – reducing complexity, improving design, and keeping codebases clean.
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
Executes large-scale architectural refactoring and technical debt reduction across the entire codebase. Ensures consistency with modern design patterns.
Analyzes code complexity, technical debt, and industry trends to propose a 3-month strategic roadmap. Aligns engineering effort with business ROI.
Translates engineering metrics (DORA, error rates, technical debt) into business KPIs and financial impact. Helps justify technical investments to stakeholders.
Systematic framework for resurrecting and modernizing legacy codebases through archaeology, resurrection, and rejuvenation phases. Activate on "legacy code", "inherited codebase", "no documentation", "technical debt", "resurrect", "modernize". NOT for greenfield projects or well-documented active codebases.
Invoke IMMEDIATELY via python script when user requests refactoring analysis, technical debt review, or code quality improvement. Do NOT explore first - the script orchestrates exploration.
Technical leadership advisor for CTOs on architecture decisions, engineering strategy, team scaling, technical debt management, and technology evaluation.
Use when solution space exploration is complete and you're ready to create an implementation plan. Enforces "simple over easy" - the fundamentally right solution, not the path of least resistance. Triggers after /design-solution, when a solution has been chosen, or when asked to "make a plan" or "create a plan".
Adaptive sprint workflow: deep analysis, evolving roadmap, one-at-a-time sprints, formal debt tracking, and re-entry prompts for context persistence. Trigger: When the user wants to analyze a project, create a roadmap, generate/execute sprints iteratively, or check project status and technical debt.
Clean up code, remove dead code, and optimize project structure. Use when user wants to clean codebase, remove unused code, or optimize imports.
This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.