Drop-in instruction sets that give Claude (or another AI) a specific capability — shareable, reusable, one per task.
AGENTS.md and CLAUDE.md files tell your AI coding assistant how to work in a project — commands, conventions, context. Browse community examples or submit your own.
Model Context Protocol servers connect Claude to live tools and data — file systems, APIs, databases. Self-host or point at a public endpoint.
Configuration files for AI coding tools. Drop a CLAUDE.md, .cursor/rules, or opencode.json in your repo root to shape how the AI codes.
API services that accept direct micropayments via Lightning (L402 protocol) — pay per call, no subscription required. AgentList is a directory only; verify a service before use.
Tip! Simply ask your agent directly to install the skill:
- it's a skill folder, with everything in it directly. easier to ingest than the listing page.
Tip! Share
for the raw content of this listing — easier to ingest in an agent.
API services that accept direct micropayments via Lightning (L402) or X402 — pay per call, no subscription required.
AgentList is a directory only; verify a service before use.
Category: skill Author: npub1carj2jw…h8c9 Date: 10 Aug 2026 Votes: 0
---
name: clean
description: >-
Polish your own diff by hand with KISS/DRY and local style — the pre-handoff
pass, not a test run and not a subagent sweep. Use for /clean, "clean it up",
"tidy this", and automatically before creating, updating, or automerging a PR
or moving to the next one.
---
# Clean
KISS/DRY and copy the local code style. Be elitist, shorthand, clever, concise,
efficient, and elegant.
**"Clean" means polishing the code — it does NOT mean running the test suite,
tsc, or lint as the task.** Run a check only if it's genuinely needed to confirm
the polish is safe.
Clean is a standalone pass, not just a pre-PR step — run it whenever things get
messy, including mid-work. Also run it automatically before any PR handoff
(creating, updating, automerging, or moving to the next PR) without being told
each time.
## Do
1. Re-read your diff. Cut dead code, leftover debug logging, and duplication.
2. Extend existing helpers — don't parallel-implement.
3. Match neighboring style (names, imports, file layout, comment density).
4. Prefer the small sharp version over ceremony.
5. UI work: only after they like the UI (`ui-only`). Use `ui-system` for
primitives.
6. On the PR: title/body describe the change as a whole (a short intro), not a
changelog of steps. Split into topical commits (`pr-update`), run
`no-tropes` on the text, and link the PR.
## Don't
- Run the test suite / tsc / lint just because you were told to "clean"
- Unrelated refactors
- New abstractions with one caller
- Scope creep dressed up as cleanup
Discussion