typescript-backend-coder-01

Estrellas10

Forks3

Actualizado11 de abril de 2026 a las 06:45

Reliability-first backend TypeScript skill for APIs, workers, queues, CLIs, and long-running services. Use when writing Node, Bun, Deno, or worker code that needs request and env parsing, branded identifiers, explicit result errors, cancellation propagation, idempotent writes, persistence evolution, or contract and integration tests.

Instalación

Instalar con Codex o Claude Copia este prompt, pégalo en Codex, Claude u otro asistente, y deja que revise la página de la skill y la instale por ti.

Fuente

that-in-rust

that-in-rust/agent-room-of-requirements

Abrir repositorio de GitHub Ver repositorios del creador

Descarga

Ocupaciones relacionadasSOC

Basado en la clasificación ocupacional SOC

Desarrolladores de softwareOcupaciones informáticas y matemáticas·SOC 15-1252

Explorador de archivos

5 archivos

SKILL.md

readonly

Más de este repositorio

mismo repositorio

strata-202607

that-in-rust/agent-room-of-requirements

Use Strata, the Legacy Code Labs macOS visual-spec app, through its local Streamable HTTP MCP server. Trigger when Codex needs to create, read, validate, update, version, diff, or restore Strata diagrams; build visual specs from user flows, discovery trees, architecture sketches, or D2; diagnose Strata MCP setup; or verify a feature against a shared Strata canvas.

2026-07-1610

clarity202606

that-in-rust/agent-room-of-requirements

Use Clarity, the LegacyCodeHQ structural design CLI, for dependency impact graphs, architecture/refactoring verification, before-commit design checks, code review context, cycle/module/workspace exploration, AGENTS.md Clarity setup, or rebuilding/probing Clarity command availability. Use when Codex needs to run or interpret clarity show, watch, languages, extensions, modules, cycles, workspace, setup, or version-specific Clarity commands.

2026-07-0810

kotlin-backend-delivery-01

that-in-rust/agent-room-of-requirements

Plan, build, harden, and review Kotlin backend services with Spring Boot, Ktor, coroutines, typed configuration, persistence, migrations, testing, security, resilience, and operations. Use for Kotlin HTTP APIs, workers, service refactors, production-readiness reviews, or JVM backend architecture decisions.

2026-07-0510

kotlin-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Kotlin skill for implementing, refactoring, or reviewing Kotlin libraries, CLIs, JVM modules, shared domain code, coroutine code, and Java interop boundaries. Use when work needs null-safety discipline, value and sealed types, idiomatic scope-function use, typed errors, structured concurrency, testing, or JVM quality gates.

2026-07-0510

python-coder-01

that-in-rust/agent-room-of-requirements

Reliability-first Python skill for implementing, refactoring, or reviewing Python packages, CLIs, services, scripts, async code, tests, and typed modules. Use when work needs type hints, dataclasses, boundary parsing, exception design, context managers, asyncio cancellation, packaging, pytest or unittest strategy, ruff, mypy, pyright, or runtime safety.

2026-07-0510

local-vision-ollama

that-in-rust/agent-room-of-requirements

Analyze images using local Ollama vision model (qwen3.5:4b) with automatic pre-resizing and filename sanitization for reliable processing.

2026-05-1010

name	typescript-backend-coder-01
description	Reliability-first backend TypeScript skill for APIs, workers, queues, CLIs, and long-running services. Use when writing Node, Bun, Deno, or worker code that needs request and env parsing, branded identifiers, explicit result errors, cancellation propagation, idempotent writes, persistence evolution, or contract and integration tests.

TypeScript Backend Reliability

Overview

Use this skill for server-side TypeScript where IO lies can corrupt business logic. It concentrates on safe request parsing, domain-safe IDs, adapter boundaries, cancellation, retry safety, and persistence evolution.

When To Use

HTTP handlers, RPC endpoints, webhooks, queues, cron jobs, workers, or CLIs
.ts backend modules in Node.js, Bun, Deno, serverless, or edge runtimes
Config and environment bootstrapping, transport adapters, provider clients, repositories, or service layers
Reviews where the main risks are bad inputs, retries, timeouts, or storage drift

Workflow

Assume all inbound data is untrusted. Parse requests, events, queue payloads, and env at the boundary.
Read references/reference-map.md, then the relevant sections in references/backend-reliability-reference.md. Pull in typescript-coder-01 as the shared baseline when needed.
Apply the default backend patterns in order: schema-first parsing, branded IDs, explicit result error algebra, deadline propagation, transport normalization, ports-and-adapters, and idempotent mutation boundaries.
Keep the service core framework-light. Push HTTP, queue, database, and provider quirks to adapters.
Validate with contract or integration tests for the real boundary, not only unit tests inside the core.

Reference Use

Use references/reference-map.md first for fast routing.
Use references/backend-reliability-reference.md for the full scored backend patterns and anti-patterns.
For large-file navigation, prefer heading search such as rg '^##|^###' references/backend-reliability-reference.md.

Output Expectations

Expected business failures stay visible in signatures.
Writes should be retry-safe when the environment can retry them.
Deadline and cancellation handling should flow through the whole call chain.
The final design should make the risky boundary obvious from a quick skim.