simplify-code
Skill2 starsChanged 36 days agoMITView on GitHub
Simplify recently changed or user-selected code while preserving observable behavior, public APIs, tests, and required safeguards. Use when asked to simplify, clean up, refactor for clarity, reduce nesting, remove duplication, or review an implementation for unnecessary complexity.
29 other projects use a version of this.
Adopted by
Most recently taken up by
- zedarvates/frugal-skillstheir own version, first seen Nov 8, 2026
- ashleysbrain/skillstheir own version, first seen Nov 8, 2026
- delorenj/skillstheir own version, first seen Nov 7, 2026
- marin-community/marintheir own version, first seen Nov 1, 2026
- LuisUrrutia/skillstheir own version, first seen Oct 18, 2026
- Fahrnetic/engineering-agent-skill-workflowtheir own version, first seen Oct 15, 2026
Used with
Projects with it also use competitor-news-monitor, blocked-page-recovery and 10 more.
Other files people use alongside this one.
Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
aivrarSkillcompetitor-news-monitor
Watch named companies for material news; cited digests.
Also in 7 projects that use this
aivrarSkillblocked-page-recovery
Recover blocked/paywalled/WAF'd pages via fallbacks.
Also in 7 projects that use this
john-data-chenSkillteams-meeting-pipeline
Operate the Teams meeting summary pipeline via Hermes CLI — summarize meetings, inspect pipeline status, replay jobs, manage Microsoft Graph subscriptions.
Also in 8 projects that use this
mae616Skillp5js
p5.js(クリエイティブコーディング)のProcessing由来「コードでスケッチ」思想を軸に、setup/drawループ・座標系・インタラクション・パフォーマンス最適化を整理する。p5.js、Processing、クリエイティブコーディング、ジェネラティブアート、インタラクティブ表現、ビジュアルプログラミング、Canvas描画、パーティクル、フラクタル、ノイズ表現に関する相談で必ず使うこと。ユーザーが「コードでアート」「動くビジュアル」「インタラクティブな描画」と言った場合にも適用する。
Also in 11 projects that use this
john-data-chenSkilltouchdesigner-mcp
Control a running TouchDesigner instance via twozero MCP — create operators, set parameters, wire connections, execute Python, build real-time visuals. 36 native tools.
Also in 5 projects that use this
Tommy-ywSkillpopular-web-designs
54 production-quality design systems extracted from real websites. Load a template to generate HTML/CSS that matches the visual identity of sites like Stripe, Linear, Vercel, Notion, Airbnb, and more. Each template includes colors, typography, components, layout rules, and ready-to-use CSS values.
Also in 11 projects that use this
- +4 more from aivrar
Other versions29 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 29
- NousResearch/hermes-agent★ 262ksame name
- vudovn/ag-kit★ 8.2ksame name
- vudovn/antigravity-kit★ 8.2ksame name
- marin-community/marin★ 4.1ksame name
- Cosmian/kms★ 372same name
- aivrar/portable-hermes-agent★ 239same name
- wundercorp/loki★ 28same name
- delorenj/skills★ 17same name
- Samin12/skills★ 8same name
- kevinforge/orbit★ 5same name
19 more not listed
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository43 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- .github/copilot-instructions.mdCopilot instructions
- accessibility-auditSkill
- ai-feature-reviewSkill
- api-design-reviewSkill
- architecture-reviewSkill
- cli-and-scripts-auditSkill
- coding-styleSkill
- data-auditSkill
- data-minimizationSkill
- debugSkill
- describe-changesSkill
- destructive-ops-approvalSkill
- docs-consolidationSkill
- explain-codebaseSkill
- full-project-auditSkill
- implement-featureSkill
- improve-promptSkill
- incident-responseSkill
- infrastructure-auditSkill
- legal-compliance-reviewSkill
- license-complianceSkill
- no-ai-tracesSkill
- operations-auditSkill
- performance-auditSkill
- prepare-releaseSkill
- production-readiness-reviewSkill
- refactorSkill
- repository-auditSkill
- review-codeSkill
- secret-hygieneSkill
- security-auditSkill
- start-projectSkill
- supply-chain-pinningSkill
- surgical-implementationSkill
- threat-modelSkill
- upgrade-dependenciesSkill
- ux-reviewSkill
- verify-changesSkill
- write-agent-instructionsSkill
- write-docsSkill
- write-testsSkill
The file
We split this skill into the rules it gives an agent
6 rules. 0 are common, 6 are distinctive, and 0 are very specific to this project.
0
Common
Most of the 28 edited versions we read keep these.
6
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
- Distinctive: line 9
Read the target code, nearby tests, and repository guidance before editing.
- Distinctive: line 11
Prefer direct control flow, clear names, existing abstractions, and fewer moving parts.
- Distinctive: line 12
Remove dead code, redundant wrappers, needless indirection, duplicate branches, and comments that only restate the code.
- Distinctive: line 13
Keep comments only for non-obvious intent, constraints, invariants, workarounds, or tradeoffs.
- Distinctive: line 14
Avoid broad rewrites, speculative abstractions, dependency changes, and unrelated formatting.
- Distinctive: line 15
Run focused tests or checks that demonstrate behavior was preserved.
“Common” is measured: kept by at least 6 in 10 of the 28 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.
Files
Simplify code
- Read the target code, nearby tests, and repository guidance before editing.
- Preserve observable behavior, public interfaces, error handling, security boundaries, and required compatibility unless the user explicitly requests a change.
- Prefer direct control flow, clear names, existing abstractions, and fewer moving parts.
- Remove dead code, redundant wrappers, needless indirection, duplicate branches, and comments that only restate the code.
- Keep comments only for non-obvious intent, constraints, invariants, workarounds, or tradeoffs. Write them in a short, neutral voice without process narration.
- Avoid broad rewrites, speculative abstractions, dependency changes, and unrelated formatting.
- Run focused tests or checks that demonstrate behavior was preserved. Report any unverified area plainly.
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
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.

