Automated summary
Refines code for clarity, consistency, and maintainability while preserving all functionality, focusing on recently modified sections and applying project-specific standards.
Strengths
- Preserves exact functionality while simplifying structure
- Automatically enforces project coding standards from AGENTS.md
- Balances simplification with readability, avoiding overly compact or clever solutions
- Targets only recently changed code for minimal disruption
Limitations
- Requires project standards (AGENTS.md) to be well-defined for best results
- Does not fix bugs or alter behavior
- Limited scope may leave older code unchanged
Perfect for polishing code right after writing or editing, ensuring it adheres to project conventions and remains maintainable.
Avoid when a major rewrite or behavior change is needed, as the skill preserves functionality and may not suit large refactors.
Security analysis
SafeThis skill is a text-based instruction set for a code refactoring AI assistant. It does not declare any tools, nor does it instruct the execution of shell commands, network access, file deletion, or any actions that could compromise security. The instructions are purely about improving code clarity and maintainability without altering functionality, posing no direct security risk.
No concerns found
How this analysis is madeExamples
Simplify the React component I just added. Apply our project standards from AGENTS.md: use function keyword, explicit Props type, remove nested ternaries, and consolidate related logic.Refactor the recently modified code for clarity. Preserve all functionality, use ES module imports with extensions, avoid arrow functions, and ensure naming consistency.name: code-simplifier description: Simplifies and refines code for clarity, consistency, and maintainability while preserving all functionality. Focuses on recently modified code unless instructed otherwise. model: opus
You are an expert code simplification specialist focused on enhancing code clarity, consistency, and maintainability while preserving exact functionality. Your expertise lies in applying project-specific best practices to simplify and improve code without altering its behavior. You prioritize readable, explicit code over overly compact solutions. This is a balance that you have mastered as a result your years as an expert software engineer.
You will analyze recently modified code and apply refinements that:
-
Preserve Functionality: Never change what the code does - only how it does it. All original features, outputs, and behaviors must remain intact.
-
Apply Project Standards: Follow the established coding standards from AGENTS.md including:
- Use ES modules with proper import sorting and extensions
- Prefer
functionkeyword 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
-
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
-
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
-
Focus Scope: Only refine code that has been recently modified or touched in the current session, unless explicitly instructed to review a broader scope.
Your refinement process:
- Identify the recently modified code sections
- Analyze for opportunities to improve elegance and consistency
- Apply project-specific best practices and coding standards
- Ensure all functionality remains unchanged
- Verify the refined code is simpler and more maintainable
- Document only significant changes that affect understanding
You operate autonomously and proactively, refining code immediately after it's written or modified without requiring explicit requests. Your goal is to ensure all code meets the highest standards of elegance and maintainability while preserving its complete functionality.
From the file to a first result
The download contains exactly the content displayed on this page. This copy may differ from the latest version in the source repository.
View the source and supporting filesThis download contains SKILL.md only. Any scripts, references, templates and dependencies are not included. Get the required files from the source, preserving their directory structure, before continuing.
1. Download the file
Download SKILL.mdFrom the root of a test project, save the file as .skill-downloads/code-simplifier-mm5t8a60/SKILL.md, or use the command below. This folder is for inspecting the skill before installation.
Command for macOS/Linux or WSL: requires a POSIX shell and curl. On Windows without WSL, use the download button and create the folder manually.
mkdir -p '.skill-downloads/code-simplifier-mm5t8a60' && curl --fail --show-error --location 'https://skills-guides.com/api/skills/code-simplifier-mm5t8a60/download' --output '.skill-downloads/code-simplifier-mm5t8a60/SKILL.md.part' && mv '.skill-downloads/code-simplifier-mm5t8a60/SKILL.md.part' '.skill-downloads/code-simplifier-mm5t8a60/SKILL.md'2. Check prerequisites
Read SKILL.md before using it. If it references scripts or external services, inspect them and prepare the required access in your test environment.
No recognized prerequisites section in this file. This does not mean it is self-contained: libraries, tools and access requirements may be mentioned elsewhere in the content or source repository.
The platforms on this page are catalog indications. The paths below follow tool documentation; they do not prove this skill has been run in those tools. No minimum tool version is confirmed for this listing.
3. Load the skill
After inspection, copy the complete folder into your project using one of the commands below, then open a new tool session. The command stops if a folder with the same name already exists: compare the files before replacing it.
Claude Code
test -f '.skill-downloads/code-simplifier-mm5t8a60/SKILL.md' && test -s '.skill-downloads/code-simplifier-mm5t8a60/SKILL.md' && mkdir -p '.claude/skills' && test ! -e '.claude/skills/code-simplifier' && cp -R '.skill-downloads/code-simplifier-mm5t8a60' '.claude/skills/code-simplifier'OpenSkills
OpenSkills must already be installed. The local install/read procedure is checked with OpenSkills 1.5.0, which requires Node.js ≥ 20.6.0. Catalog slugs are not resolved automatically.
Official OpenSkills installationopenskills install './.skill-downloads/code-simplifier-mm5t8a60'openskills read 'code-simplifier-mm5t8a60'Reading should display the installed file content and its base directory. It does not run the skill or install its dependencies.
For an agent that reads AGENTS.md, then sync the index. This command changes AGENTS.md: review the diff before using it.
openskills syncManual method or another tool: attach SKILL.md to a conversation, or open it in an agent that can read files. Include any required supporting resources. No universal folder is recognized by every tool.
4. Try a first task
Use a short, synthetic input: an API endpoint, a small document or an interface brief. In a new conversation, attach the file or give the agent its path, then adapt this request:
Read .skill-downloads/code-simplifier-mm5t8a60/SKILL.md and apply its instructions to this example: [describe a test input]. Identify any missing files, dependencies or access. Produce the result requested by the skill without inventing data or running unreviewed scripts.Expected result: output matching the skill instructions, or a precise list of missing prerequisites. A read confirmation alone does not validate a first use. If an external resource is unavailable, that path remains untested.
React Hook Form Best Practices
Development
Master React Hook Form: avoid anti-patterns, manage subscriptions, and handle reset, dirty state, and controlled inputs correctly.
Emotion to Mantine Migration
Development
Migrate Emotion styled-components to Mantine components with style props and CSS modules. Use when converting .styled.tsx files or removing @emotion imports.
Scope Creep Detector
Development
Analyzes git diffs against a stated intent to detect scope creep, unrelated files, broad PRs, and oversized changes, then suggests keep, split, or justify actions.