slop-cleaner
Skill0 starsChanged 4 months agoNo licenceView on GitHub
Checklist para identificar e remover "AI slop" visual e estrutural (cara de interface gerada por IA sem curadoria). Use ao revisar/auditar qualquer tela ou componente novo antes de considerá-lo terminado, ou quando o usuário disser que algo "parece feito por IA" / "tem cara de AI slop". Baseado nos vídeos "How to Avoid AI Slop in Vibe-Coded Landing Pages" (DesignCode) e "10 Ways to Prevent AI Slop in Your Frontend UIs" (Tom Is Loading), mais observações de campo do usuário. Aplica-se a qualquer projeto de frontend, independente de stack.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- arbones/claude-skillstheir own version, first seen Mar 29, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- arbones/claude-skills★ 0same name
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 repository60 other files it gives its agents.
- animateSkill
- api-and-interface-designSkill
- apple-higSkill
- arrangeSkill
- auditSkill
- bolderSkill
- book-to-obsidianSkill
- browser-testing-with-devtoolsSkill
- ci-cd-and-automationSkill
- clarifySkill
- claude-code-playbookSkill
- code-review-and-qualitySkill
- code-simplificationSkill
- colorizeSkill
- context-engineeringSkill
- critiqueSkill
- debugging-and-error-recoverySkill
- delightSkill
- deprecation-and-migrationSkill
- design-principlesSkill
- diagram-designSkill
- distillSkill
- documentation-and-adrsSkill
- doubt-driven-developmentSkill
- extractSkill
- find-skillsSkill
- frontend-designSkill
- frontend-ui-engineeringSkill
- git-workflow-and-versioningSkill
- hallmarkSkill
- hardenSkill
- hig-project-contextSkill
- idea-refineSkill
- incremental-implementationSkill
- interview-meSkill
- karpathy-guidelinesSkill
- lucas-setupSkill
- make-interfaces-feel-betterSkill
- normalizeSkill
- observability-and-instrumentationSkill
- onboardSkill
- optimizeSkill
- overdriveSkill
- performance-optimizationSkill
- planning-and-task-breakdownSkill
- polishSkill
- quieterSkill
- security-and-hardeningSkill
- security-auditSkill
- seo-auditSkill
- shipping-and-launchSkill
- source-driven-developmentSkill
- spec-driven-developmentSkill
- teach-impeccableSkill
- test-driven-developmentSkill
- transitions-devSkill
- typesetSkill
- using-agent-skillsSkill
- vault-setupSkill
- yt-to-obsidianSkill
The file
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.