coding-standards

Enforces TypeScript coding standards for modules, boundaries, async workflows, and Effect services.

2|Updated Sep 14, 2026
One-click install
npx skills add https://github.com/kwanpham2195/agent-stuff --skill coding-standards-kwanpham2195
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: coding-standards
Source: https://github.com/kwanpham2195/agent-stuff/tree/main/skills/workflow/coding-standards
Command: npx skills add https://github.com/kwanpham2195/agent-stuff --skill coding-standards-kwanpham2195

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve? Codebases drift into inconsistent patterns: untyped boundary data, floating promises, shallow modules, and ad hoc retry logic. This Skill gives the agent a rigorous, opinionated rulebook so every change follows the same architecture standards for TypeScript, Effect, and Cloudflare projects. ## Core Features & Use Cases - Boundary and parsing rules: Enforces parsing unknown input at seams, strict command schemas, and separate protocol versus persistence projections. - Async and workflow standards: Covers cancellation propagation, bounded concurrency, retry-safe commands, idempotency keys, and atomic transition guards. - Module and domain design: Guides deep module design, branded types, state machines, functional core / imperative shell separation, and dependency seams. - Effect and Cloudflare references: Provides dedicated guidance for Effect Services, Layers, Schema, scheduling, caching, HTTP clients, and Cloudflare Workers, Durable Objects, and Agents. - Use Case: When asked to add a new API endpoint that creates payments, the agent applies idempotency rules, parses the request body with a strict schema, models the invoice lifecycle as a state machine, and wraps the provider call in a typed Effect HTTP client. ## Quick Start Review my new TypeScript service module against the coding standards and report any violations with fixes.

Frequently Asked Questions about coding-standards

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

FAQPage Schema
How do I enforce coding standards during AI-assisted code review?▼

Load this Skill so the agent applies its rule files when reviewing or writing code. It checks boundaries, async ownership, module depth, and domain modeling, then reports violations with concrete fixes drawn from each rule file's review checklist.

What rules apply for parsing API request bodies in TypeScript?▼

Request bodies stay unknown until parsed by a concrete schema parser at the boundary, and the refined value flows inward. Mutating command parsers reject unknown fields by default, and JSON.parse results are never cast directly to domain types.

Does this Skill support Effect-based projects?▼

Yes, it includes dedicated Effect references for Services, Layers, Schema, configuration, scheduling, caching, streams, HTTP clients, and testing. These apply only to code already organized around Effect; non-Effect code follows the general standards.

How should retries and idempotency be handled for POST requests?▼

Mutating commands are treated as retryable by default and must not allocate fresh identity on retry. Use idempotency keys, unique constraints, or transactional outbox patterns, and guard lifecycle transitions with atomic conditional updates.

When should I use Durable Objects versus Durable Workflows on Cloudflare?▼

Durable Objects and Agents own serialized coordination and local state for one shard or entity. Durable Workflows handle multi-step cross-service processes needing retries, compensation, timers, or human approval.

What are the limitations of these coding standards?▼

The standards are opinionated toward TypeScript, Effect, and Cloudflare stacks and assume schema libraries like Zod or Effect Schema. They do not install tooling, and some areas like Effect RPC adoption criteria are intentionally left unsettled.