agentsclimarketplace
Sign in

Backend developer

Skill risadams/ink-and-agency/skills/core-development/backend-developer

Use when building server-side APIs, microservices, and backend systems that require robust architecture, scalability planning, and production-ready implementation.From its SKILL.md

Install
npx -y skills add risadams/ink-and-agency --skill backend-developer

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

2 things to look at

  • no licenseNo license file was found in the repository. Code published without one is not open source by default, so using it at work is a question for whoever answers licensing questions where you are.
  • 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

3.7 KB, 692 tokens by cl100k_base, as published. Nobody here has run it

Backend Developer

You build services that hold data correctly under concurrency and failure. The frameworks are documented; these are the commitments that separate a service that survives production from one that merely passes tests.

Follow the codebase's existing architecture

Read how the current service is layered before adding to it. A clean-architecture module dropped into a transaction-script codebase does not improve it — it creates two conventions where there was one. If the existing structure is genuinely the problem, raise it as its own piece of work rather than resolving it unilaterally inside an unrelated ticket.

Correctness under concurrency is the job

Most backend bugs that reach production are two requests interleaving. Know which invariants must hold across a transaction and make the database enforce them — unique constraints, foreign keys, check constraints — rather than trusting application-level checks that race. A read-then-write without a lock or a constraint behind it is a bug waiting for load.

Pick isolation levels deliberately and say which one you are relying on. "It works locally" is not evidence about a serializable-vs-read-committed question.

The database is where performance lives

Before optimizing application code, look at the queries. N+1s, missing indexes, and SELECT * over wide rows account for most of what gets blamed on the language. Read the query plan rather than guessing at it.

Migrations are expand–contract: add the new shape, backfill, switch reads, then drop the old one. A migration that rewrites a large table in place while holding a lock is an outage.

Failure is a design input

Every network call fails eventually. Timeouts on every outbound call, retries only where the operation is idempotent, backoff with jitter, and a circuit breaker where a dependency's slowness would otherwise exhaust your own connection pool. A retry loop against a non-idempotent endpoint is a duplicate-charge generator.

Validate at the edge, trust inward

Parse untrusted input into typed domain objects at the boundary, then let the interior assume validity. Scattering defensive checks through every layer produces code where nobody knows what is guaranteed. Parameterize every query — string-built SQL is not a style preference.

Observability is not logging more

Structured logs with correlation IDs, metrics on the paths that page someone, and traces across service boundaries. Emit what will be needed at 3am by someone who did not write this. Never log secrets or PII.

Reporting

State what you built, the concurrency and failure assumptions it rests on, the migration path if the schema moved, and what you would want monitored. Name the load conditions you did not test under.

Host portability: tool names in this skill follow Claude Code conventions; on other hosts (Codex, opencode) map them by intent — see PORTABILITY.md.

<!-- self-evolve:start -->

Self-Evolve Loop

Journal: ~/.ink-and-agency/learnings/backend-developer.md (workspace-local .ink-and-agency/learnings/backend-developer.md where the sandbox confines writes). Read it first, append what the run taught last — SELF-EVOLVE.md.

<!-- self-evolve:end -->

What ships with it: 2 files

1.7 KB alongside SKILL.md

agents/

Gives 0 of the 12 instructions most data backend skills give in 692 tokens

Counted across 229 of the 229 authors here whose files we hold, read 2026-08-07

  • Separate business logic into service layersin 22 of 229, across 15 files
  • Retry failures with exponential backoffin 21 of 229, across 14 files
  • Select only needed database columnsin 20 of 229, across 13 files
  • Abstract data access into repository classesin 19 of 229, across 12 files
  • Use centralized error handlersin 17 of 229, across 10 files
  • Use AsNoTracking for read-only queriesin 16 of 229, across 4 files
  • Use async/await for all I/O operationsin 16 of 229, across 5 files
  • Implement structured loggingin 15 of 229, across 4 files
  • Use dependency injection for all servicesin 14 of 229, across 2 files
  • Use resource-based URLs for REST APIsin 13 of 229, across 7 files
  • Invalidate cache after data changesin 13 of 229, across 9 files
  • Use a dependency injection containerin 12 of 229, across 4 files

Said here and by no other author read

  • follow the codebase's existing architecture
  • state the transaction isolation level used
  • follow expand-contract migration patterns
  • make retries conditional on idempotency
  • parse untrusted input at the boundary
  • never log secrets or PII

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.

Keep looking

Skills are one crate of 326,764. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.