Skip to content
Back to skills

Simplify Code

ASecurity

Simplify and refine code. Only trigger on `/simplify-code`.

  • 5 stars
  • 0 votes
  • 0 copies
  • 1 view
  • Added September 23, 2026
developmentreactperformance

Security analysis

A100/100

Scanned September 23, 2026

npx -y skills add jamesblackwell/falcondeck --skill simplify-code --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Simplify Code?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Simplify Code
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/jamesblackwell-simplify-code/badge)](https://www.skillsdirectory.com/skills/jamesblackwell-simplify-code)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: simplify-code
description: Simplify and refine code. Only trigger on `/simplify-code`.
---

# Code Simplifier

Simplify and refine code for clarity, consistency, and maintainability while preserving all functionality. Focus on recently modified code unless instructed otherwise.

## What To Do

Analyze recently modified code and apply refinements that:

### 1. Preserve Functionality
Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.

### 2. Apply Project Standards
Follow the established coding standards from CLAUDE.md and AGENTS.md including:

- Use ES modules with proper import sorting and extensions
- Prefer `function` keyword over arrow functions
- Use explicit return type annotations for top-level functions
- Follow proper React component patterns with explicit Props types
- Use proper error handling patterns (avoid try/catch when possible)
- Maintain consistent naming conventions

### 3. Enhance Clarity
Simplify code structure by:

- Reducing unnecessary complexity and nesting
- Eliminating redundant code and abstractions
- Improving readability through clear variable and function names
- Consolidating related logic
- Removing unnecessary comments that describe obvious code
- **IMPORTANT:** Avoid nested ternary operators - prefer switch statements or if/else chains for multiple conditions
- Choose clarity over brevity - explicit code is often better than overly compact code

### 4. Maintain Balance
Avoid over-simplification that could:

- Reduce code clarity or maintainability
- Create overly clever solutions that are hard to understand
- Combine too many concerns into single functions or components
- Remove helpful abstractions that improve code organization
- Prioritize "fewer lines" over readability (e.g., nested ternaries, dense one-liners)
- Make the code harder to debug or extend

### 5. Focus Scope
Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.

## Refinement Process

1. Identify the recently modified code sections
2. Analyze for opportunities to improve elegance and consistency
3. Apply project-specific best practices and coding standards
4. Ensure all functionality remains unchanged
5. Verify the refined code is simpler and more maintainable
6. Document only significant changes that affect understanding

## When NOT to Simplify

- Working code that is already clear and maintainable
- Code where the "simplification" would make it harder to understand
- Third-party code or generated code
- Performance-critical code where the current structure is intentional

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…