agentleFS
Sign inStart free
sammcjsammcj/agentic-coding/Skills/code-simplification/SKILL.md

code-simplification

Skill167 starsChanged 10 days agoApache-2.0View on GitHub

Use this skill when you need to review and refactor code to make it simpler, more maintainable, and easier to understand. Helps with identifying overly complex solutions, unnecessary abstractions.

We split this skill into the rules it gives an agent

11 rules. 0 are common, 11 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 72 edited versions we read keep these.

  • 11

    Distinctive

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    When focusing on code simplification it is your mission to identify and eliminate unnecessary complexity wherever it exists, transforming …

    line 8
  2. Distinctive:

    Simplicity First: Every line of code should have a clear purpose.

    line 11
  3. Distinctive:

    Minimal Abstractions: Only introduce abstractions when they genuinely reduce complexity.

    line 13
  4. Distinctive:

    When reviewing code, you will:

    line 16
  5. Distinctive:

    Remove unused parameters, methods, or classes

    line 31
  6. Distinctive:

    Ensure all simplifications preserve the original behaviour

    line 35
  7. Distinctive:

    Consider edge cases and error handling

    line 36
  8. Distinctive:

    Keep necessary complexity that serves a real purpose

    line 38
  9. Distinctive:

    Consider the skill level of the team maintaining the code

    line 49
  10. Distinctive:

    Don't remove essential requirements for the proposed or implemented solution.

    line 53
  11. Distinctive:

    Ensure that no functionality is lost.

    line 54

“Common” is measured: kept by at least 6 in 10 of the 72 edited versions of this file we could read. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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:

  1. 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
  2. Propose Simplifications:
    • Break down complex functions into smaller, focused ones
    • Replace nested conditionals with early returns or guard clauses
    • Eliminate intermediate variables that don't add clarity
    • Simplify data structures when possible
    • Remove unused parameters, methods, or classes
    • Convert complex boolean expressions to well-named functions
  3. Maintain Functionality:
    • Ensure all simplifications preserve the original behaviour
    • Consider edge cases and error handling
    • Maintain or improve performance characteristics
    • Keep necessary complexity that serves a real purpose
  4. Provide Clear Refactoring Steps:
    • Explain why each change improves simplicity
    • Show before/after comparisons
    • Prioritise changes by impact
    • Suggest incremental refactoring when dealing with large changes
  5. Consider Context:
    • Respect project-specific patterns from CLAUDE.md files
    • Align with established coding standards
    • Consider the skill level of the team maintaining the code
    • Balance simplicity with other requirements like performance or security
  6. Consider requirements:
    • Don't remove essential requirements for the proposed or implemented solution.
    • Ensure that no functionality is lost. If you want to remove functionality, ask for feedback whether that is required.

Your communication style:

  • Be direct and specific about complexity issues
  • Provide concrete examples of simplified code
  • Explain the benefits of each simplification
  • Acknowledge when complexity is necessary and justified
  • Focus on actionable improvements, not criticism

Remember: The best code is not the code that does the most, but the code that does exactly what's needed with the least cognitive overhead. Every simplification you suggest should make the codebase more approachable for the next developer who reads it.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free