agentleFS
Sign inStart free
ingsergiovtingsergiovt/claude-code-hexagonal-kit/.claude/skills/new-use-case/SKILL.md

new-use-case

Skill1 starsChanged 36 days agoMITView on GitHub

Add an application use case to an existing module, test first. Use for any new business operation such as "refund an order" or "list products".

1 other project uses a version of this.

Adopted by

Most recently taken up by

  • Other versions1 project uses a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 1

    1. SebastianKuehnau/sandbox-demo★ 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 repository5 other files it gives its agents.

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 1 is distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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. Very specific:

    If the use case needs something new from the outside world (clock, mail, payment...), add a port interface to domain/ports.ts.

    line 14
  2. Very specific:

    Test first: Create application/<use-case-name>.test.ts (or extend use-cases.test.ts) using the fakes in application/testing/fakes.ts: …

    line 15
  3. Distinctive:

    Never call a use case from another use case through composition.

    line 25

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

New use case

Location: src/modules/<module>/application/<use-case-name>.ts (kebab-case file, one use case per file).

Steps

  1. Decide where each rule lives. Invariants and state transitions go in domain/ (entity function that throws a DomainError); the use case only orchestrates: load, call domain, save.
  2. If the use case needs something new from the outside world (clock, mail, payment...), add a port interface to domain/ports.ts. Do not import an adapter.
  3. Test first. Create application/<use-case-name>.test.ts (or extend use-cases.test.ts) using the fakes in application/testing/fakes.ts: success path, every domain error, "nothing persisted on failure", deterministic ids/time. Run pnpm test and watch it fail.
  4. Implement with the factory pattern from templates/use-case.ts.tpl: make<UseCaseName>(deps) returns a function; export the function type as <UseCaseName>.
  5. Re-export it from application/index.ts. It is then part of the module API through index.ts.
  6. Wire it in src/composition/<module>.ts by adding it to the exported use-case object.
  7. Run pnpm check.

Rules

  • Imports allowed: ../domain only (plus src/shared). No next, react, zod, adapters, or Date.now().
  • Throw domain errors; do not return error codes or catch-and-swallow.
  • Never call a use case from another use case through composition; inject the port or the other use case type.

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.

Check your setup, free