agentleFS
joelhooksjoelhooks/uncomplect/skills/keep-or-cut/SKILL.md

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

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
  1. Distinctive:

    Delete interfaces your product will not use.

    line 19
  2. Distinctive:

    Read AGENTS.md first. Keep unrelated product work.

    line 25
  3. Distinctive:

    every module imported by these files or retained core code, and their tests

    line 35
  4. Very specific:

    Keep apps/cli/src/surfaces.ts with only the toCommand composition and its imports.

    line 45
  5. Very specific:

    Remove stale exports from packages/capability/src/index.ts and any affected package barrel.

    line 123
  6. Distinctive:

    Remove stale imports, Layers, commands, and tests found by the compiler.

    line 124
  7. Distinctive:

    Update the package table in AGENTS.md so repo law matches the clone.

    line 125

≈ “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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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.ts
  • packages/capability/src/implement.ts
  • packages/capability/src/to-command.ts
  • packages/capability/src/call-watch.ts and packages/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/src and packages/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, and mcp commands from apps/cli/src/command.ts
  • apps/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.ts
  • packages/capability/src/code-mode.ts
  • packages/capability/src/sandbox-error.ts
  • packages/capability/src/sandbox-service.ts
  • packages/capability/src/sandbox-subprocess.ts
  • packages/capability/src/to-code-mode.ts
  • packages/capability/test/catalog.test.ts
  • packages/capability/test/sandbox.test.ts
  • packages/capability/test/to-code-mode.test.ts
  • codeMode and mcpServer.codeMode from apps/cli/src/surfaces.ts
  • the catalog command and --code-mode flag from apps/cli/src/command.ts
  • catalog and code-mode cases from apps/cli/test/cli.e2e.test.ts
  • the ./sandbox and ./code-mode exports from packages/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-api export from packages/capability/package.json
  • http, routes, and webServer from apps/cli/src/surfaces.ts
  • the openapi and serve commands from apps/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 test
  • packages/capability/test/mcp-harness.ts
  • tools and mcpServer from apps/cli/src/surfaces.ts
  • the mcp command from apps/cli/src/command.ts
  • MCP cases from apps/cli/test/cli.e2e.test.ts
  • the ./toolkit export from packages/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.ts and its test
  • xstate and @xstate/effect from packages/core/package.json
  • their minimumReleaseAgeExclude entries from pnpm-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/devtools from apps/cli/package.json
  • devtoolsRoutes, devtoolsWebServer, mcpServer.devtools, and mcpServer.devtoolsCodeMode from apps/cli/src/surfaces.ts
  • the --devtools flag from apps/cli/src/command.ts
  • the devtools cases from apps/cli/test/serve.test.ts and apps/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

  1. Remove stale exports from packages/capability/src/index.ts and any affected package barrel.
  2. 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.
  3. Update the package table in AGENTS.md so repo law matches the clone.
  4. Refresh the lockfile and format intentional changes:
pnpm install
pnpm fix
pnpm turbo run check test build

Let the compiler and checks find every stale reference. Do not silence errors or delete unrelated tests.

Download now (ZIP)

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
What did you use it for? e.g. Reviewing pull requests in a Rails app

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.