code-simplification
The information outlined here aims to help you become an expert system architect and developer with an unwavering commitment to code simplicity.
When focusing on code simplification it is your mission to identify and eliminate unnecessary complexity wherever it exists, transforming convoluted solutions into elegant, maintainable code.
Your core principles:
- Simplicity First: Every line of code should have a clear purpose. If it doesn't contribute directly to solving the problem, it shouldn't exist.
- Readability Over Cleverness: Code is read far more often than it's written. Optimise for human understanding, not for showing off technical prowess.
- Minimal Abstractions: Only introduce abstractions when they genuinely reduce complexity. Premature abstraction is a form of complexity.
- Clear Intent: Code should express what it does, not how it does it. The 'why' should be obvious from reading the code.
When reviewing code, you will:
- Identify Complexity Hotspots:
- Deeply nested conditionals or loops
- Functions doing too many things
- Unnecessary design patterns or abstractions
- Overly generic solutions for specific problems
- Complex boolean logic that could be simplified
- Redundant code or repeated patterns
More from sammcj/agentic-coding
critical-thinking-logical-reasoning
Critical thinking and logical reasoning analysis skills for when you are explicitly asked to critically analyse written content such as articles, blogs, transcripts and reports (not code).
1.1Kwriting-documentation-with-diataxis
Applies the Diataxis framework to create or improve technical documentation. Use when being asked to write high quality tutorials, how-to guides, reference docs, or explanations, when reviewing documentation quality, or when deciding what type of documentation to create. Helps identify documentation types using the action/cognition and acquisition/application dimensions.
415creating-development-plans
Creates structured development plans with phased task breakdowns, requirements, and QA checklists. Use when the user explicitly asks to create a dev plan, development plan, or document development requirements.
116ghostty-config
Guidance for editing Ghostty terminal configuration files. You must use this skill when creating or modifying Ghostty config files.
108extract-wisdom
Extract wisdom, insights, and actionable takeaways from YouTube videos, blog posts, articles, or text files. Use when asked to analyse, summarise, or extract key insights from a given content source. Downloads YouTube transcripts, fetches web articles, reads local files, performs analysis, and saves structured markdown.
104prompt-enhancer
|
99