keep-or-cut
Skill2 starsChanged 36 days agoMITView on GitHub
Learn which pieces depend on each other, then keep only the ones your project needs.
- Installs packages
1 other project uses a version of this.
Adopted by
Most recently taken up by
- nivoset/skillstheir own version, first seen Nov 12, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- nivoset/skills★ 4same 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 repository15 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- add-a-capabilitySkill
- add-a-lifecycle-machineSkill
- add-a-storeSkill
- gardenerSkill
- investigate-a-failureSkill
- learn-alchemySkill
- profile-a-workerSkill
- query-designSkill
- rat-stack-modeSkill
- shipSkill
- test-behaviourSkill
- uncomplectSkill
- write-a-wiki-pageSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 5 are distinctive, and 2 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈5
Distinctive · estimate
This author's own choices. Worth a look.
2
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 19
Delete interfaces your product will not use.
- Distinctive: line 25
Read AGENTS.md first. Keep unrelated product work.
- Distinctive: line 35
every module imported by these files or retained core code, and their tests
- Very specific: line 45
Keep apps/cli/src/surfaces.ts with only the toCommand composition and its imports.
- Very specific: line 123
Remove stale exports from packages/capability/src/index.ts and any affected package barrel.
- Distinctive: line 124
Remove stale imports, Layers, commands, and tests found by the compiler.
- Distinctive: line 125
Update the package table in AGENTS.md so repo law matches the clone.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Files
Keep or cut rat-stack
Delete interfaces your product will not use. Do not keep code because you might need it one day.
A capability is one named action with a contract and a server-side handler. The contract defines its name, input, output, failure, and metadata. A projection builds a callable interface from capabilities.
CLI means command-line interface. MCP (Model Context Protocol) lets an agent discover and call tools. Effect describes work with typed failures and required dependencies.
Read AGENTS.md first. Keep unrelated product work. Check imports and tests before deleting files.
Smallest version: command line only
Keep these files:
packages/capability/src/contract.tspackages/capability/src/implement.tspackages/capability/src/to-command.tspackages/capability/src/call-watch.tsandpackages/capability/src/actor-watch.ts- every module imported by these files or retained core code, and their tests
- all of
packages/core - the CLI composition needed by the projected command
defineContract, implement, and toCommand keep the shipped stats command working. contract.ts does not depend on the other interfaces.
For CLI only, delete:
- unused projections and their matching tests in
packages/capability/srcandpackages/capability/test, only after tracing imports from the keep list
Keep apps/cli/src/surfaces.ts with only the toCommand composition and its imports. Remove these unused CLI interfaces:
catalog,openapi,serve, andmcpcommands fromapps/cli/src/command.tsapps/cli/test/serve.test.ts- catalog, OpenAPI, MCP, and code-mode cases from
apps/cli/test/cli.e2e.test.ts
Cut code mode
Delete:
packages/capability/src/catalog.tspackages/capability/src/code-mode.tspackages/capability/src/sandbox-error.tspackages/capability/src/sandbox-service.tspackages/capability/src/sandbox-subprocess.tspackages/capability/src/to-code-mode.tspackages/capability/test/catalog.test.tspackages/capability/test/sandbox.test.tspackages/capability/test/to-code-mode.test.tscodeModeandmcpServer.codeModefromapps/cli/src/surfaces.ts- the
catalogcommand and--code-modeflag fromapps/cli/src/command.ts - catalog and code-mode cases from
apps/cli/test/cli.e2e.test.ts - the
./sandboxand./code-modeexports frompackages/capability/package.json
Cut HTTP
Delete:
packages/capability/src/to-http-api.ts,packages/capability/src/http-api.ts, and the HTTP adapter test- the
./http-apiexport frompackages/capability/package.json http,routes, andwebServerfromapps/cli/src/surfaces.ts- the
openapiandservecommands fromapps/cli/src/command.ts apps/cli/test/serve.test.ts- the OpenAPI case from
apps/cli/test/cli.e2e.test.ts
Cut MCP
Delete:
packages/capability/src/to-toolkit.ts,packages/capability/src/toolkit.ts, and the MCP adapter testpackages/capability/test/mcp-harness.tstoolsandmcpServerfromapps/cli/src/surfaces.ts- the
mcpcommand fromapps/cli/src/command.ts - MCP cases from
apps/cli/test/cli.e2e.test.ts - the
./toolkitexport frompackages/capability/package.json
Code mode imports to-toolkit.ts. Cutting MCP therefore cuts code mode too; apply both lists.
Cut XState
This recipe applies only to a clone that has already removed interest and every other lifecycle except file inspection. packages/core/src/interest-machine.ts also depends on XState and @xstate/effect; replacing file inspection alone cannot remove those dependencies. Find every remaining import before removing either package. Keeping a lifecycle means keeping its runtime and actor-watch.ts.
Delete:
packages/core/src/inspect-machine.tsand its testxstateand@xstate/effectfrompackages/core/package.json- their
minimumReleaseAgeExcludeentries frompnpm-workspace.yaml scripts/oxlint-plugin-xstate-effect.ts- its entry in
oxlint.config.ts
Then call FileInspector.inspect directly from the capability handler in packages/core/src/inspect-file.ts.
Cut devtools
Delete:
packages/devtools@rat-stack/devtoolsfromapps/cli/package.jsondevtoolsRoutes,devtoolsWebServer,mcpServer.devtools, andmcpServer.devtoolsCodeModefromapps/cli/src/surfaces.ts- the
--devtoolsflag fromapps/cli/src/command.ts - the devtools cases from
apps/cli/test/serve.test.tsandapps/cli/test/cli.e2e.test.ts
In apps/web, swap devtoolsRoutes for contentRoutes in src/dev/backend.ts, point the development condition of #devtools-overlay in apps/web/package.json at ./src/features/shared/no-devtools.tsx, and delete src/dev/devtools, src/dev/client, and src/dev/features. vite dev keeps serving search and read; test/dev-content-routes.test.ts covers that path.
CallWatch, aroundHandlers, invokerFor, and watchActor stay in packages/capability. Devtools supplies CallWatch when the application is assembled. It observes calls without wrapping capability lists; its default does nothing. aroundHandlers remains the explicit policy wrapper over one list. invokerFor calls capabilities for code mode. watchActor lets machines report to devtools without depending on it.
Clean up after each cut
- Remove stale exports from
packages/capability/src/index.tsand any affected package barrel. - Remove stale imports, Layers, commands, and tests found by the compiler. A Layer builds services and supplies their construction dependencies. A service is a named interface for one job.
- Update the package table in
AGENTS.mdso repo law matches the clone. - Refresh the lockfile and format intentional changes:
pnpm install
pnpm fix
pnpm turbo run check test buildLet the compiler and checks find every stale reference. Do not silence errors or delete unrelated tests.
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.

