coding-standards

Enforces correct-by-construction TypeScript and Effect coding standards across design, implementation, and testing.

Updated Apr 23, 2026
One-click install
npx skills add https://github.com/sndrgrdn/skills --skill coding-standards-sndrgrdn
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/sndrgrdn/skills/tree/main/coding-standards
Command: npx skills add https://github.com/sndrgrdn/skills --skill coding-standards-sndrgrdn

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? TypeScript and Effect codebases drift into inconsistent error handling, weak typing, tangled module ownership, and unreliable tests. This Skill provides a complete, opinionated standards workflow that keeps code correct by construction: parse data into meaningful types, make expected failures explicit typed values, keep effects behind cohesive services, and test through real interfaces. ## Core Features & Use Cases - Five-phase engineering workflow: Establish local rules, trace behavior and load applicable references, design from public types inward, implement the complete changed behavior, and verify through public interfaces. - Deep reference library: Fifteen-plus references covering Effect services, Layers, streams, caching, scheduling/retry, HTTP clients, Schema data modeling, Alchemy Workers and Durable Objects, errors, persistence, testing, lint policy, and module design. - Use Case: When refactoring an Effect service that calls an external HTTP API, the Skill directs you to the errors, HTTP client, retry, and testing references so the change uses typed failures, correct retry ownership, and interface-level tests. ## Quick Start Use the coding-standards skill to review and refactor this TypeScript Effect service so its errors, layers, and tests follow the project's standards.

Frequently Asked Questions about coding-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I apply TypeScript and Effect coding standards to a code change?▼

Follow the five-phase workflow: read local conventions, trace the changed behavior and load every applicable reference, design public types first, implement all paths with typed errors, then verify through public interfaces. Each phase has an explicit completion checklist.

What Effect topics does this standards guide cover?▼

It covers Effect services and Layers, Schema data modeling, streams, caching and request batching, scheduling and retry, HTTP clients, configuration, testing with TestClock, and Alchemy Workers and Durable Objects. Each topic has a dedicated reference with rules and completion checks.

How should expected failures be modeled in TypeScript?▼

Expected failures are typed values: custom tagged errors in Effect, better-result, or a small local Result union. Throws and promise rejections are reserved for defects, and outer boundaries translate typed errors into protocol outcomes.

Does this approach work with existing repository conventions?▼

Yes. A decision priority orders conflicts: correctness first, then these standards for new and changed behavior, then compatible repository conventions. Local policy may tighten the guardrails, and incompatible older patterns are contained at existing edges.

When should I create a new service or Adapter in Effect code?▼

Only after the deletion test: an abstraction earns its place when removing it would spread meaningful complexity into callers. Check existing services, clients, and Adapters first, reuse cohesive contracts, and record why reuse or extension did not fit.