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

new-adapter

Skill1 starsChanged 36 days agoMITView on GitHub

Implement a port with a new infrastructure adapter (for example a database repository replacing the in-memory one) and wire it in the composition root. Use when the user wants Postgres, an HTTP client, a mailer, etc.

  • Reads credentials

2 other projects use a version of this.

Adopted by

Most recently taken up by

  • Other versions2 projects use a version of this.

    Word for word · 0

    None found.

    Edited · 0

    None found.

    Wrote their own version · 2

    1. lbb00/ai-rules-sync★ 37same name
    2. anthril/vibe-guard★ 2same 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

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    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:

    Read the port in domain/ports.ts.

    line 13
  2. Very specific:

    Never import src/app or src/composition from an adapter.

    line 24

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

Location: src/modules/<module>/infrastructure/<adapter-name>.ts.

Steps

  1. Read the port in domain/ports.ts. The adapter must satisfy it exactly; do not change the port to fit the technology. If the port really must change, change it test-first in the domain and update every adapter and fake.
  2. Test first. Copy the contract tests from infrastructure/in-memory-order-repository.test.ts (or equivalent) so the new adapter is held to the same behaviour: missing id returns null, save overwrites, list returns everything. Tests needing a real service (database, network) must be skippable and must not be required for pnpm test to pass.
  3. Implement class <AdapterName> implements <Port>. Take clients and config through the constructor; never read process.env inside the adapter. Map storage rows to domain objects (use the domain factory, not object literals, so invariants hold).
  4. Export it from infrastructure/index.ts.
  5. Switch the wiring in src/composition/<module>.ts (the only file allowed to import infrastructure). Read env vars and build clients there.
  6. New npm dependency? Add it with pnpm add; it is allowed in infrastructure and composition only, never in domain or application.
  7. Run pnpm check.

Rules

  • Infrastructure contains no business rules (no pricing, no status checks). If you want to write an if about the business, it belongs in the domain.
  • Never import src/app or src/composition from an adapter.

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