agentleFS
Sign inStart free
cloudnative-cocloudnative-co/claude-code-starter-kit/skills/coding-standards/SKILL.md

coding-standards

Skill153 starsChanged 8 months agoMITView on GitHub

Universal coding standards, best practices, and patterns for TypeScript, JavaScript, React, and Node.js development.

120 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use everything-claude-code, everything-claude-code-conventions and 8 more.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • InfopibeSkill

    everything-claude-code

    Also in 9 projects that use this

  • mryeastcodeSkill

    everything-claude-code-conventions

    Development conventions and patterns for everything-claude-code. JavaScript project with conventional commits.

    Also in 8 projects that use this

  • niloykumarbarmanSkill

    agent-sort

    Build an evidence-backed ECC install plan for a specific repo by sorting skills, commands, rules, hooks, and extras into DAILY vs LIBRARY buckets using parallel repo-aware review passes. Use when ECC should be trimmed to what a project actually needs instead of loading the full bundle.

    Also in 8 projects that use this

  • tpavanipradeepSkill

    nextjs-turbopack

    Next.js 16+ and Turbopack — incremental bundling, FS caching, dev speed, and when to use Turbopack vs webpack.

    Also in 15 projects that use this

  • CodeWithBehnamSkill

    dmux-workflows

    Multi-agent orchestration using dmux (tmux pane manager for AI agents). Patterns for parallel agent workflows across Claude Code, Codex, OpenCode, and other harnesses. Use when running multiple agent sessions in parallel or coordinating multi-agent development workflows.

    Also in 17 projects that use this

  • InfopibeSkill

    investor-outreach

    Draft cold emails, warm intro blurbs, follow-ups, update emails, and investor communications for fundraising. Use when the user wants outreach to angels, VCs, strategic investors, or accelerators and needs concise, personalized, investor-facing messaging.

    Also in 22 projects that use this

  • +1 more from Infopibe

The file

Create a free account to mount
Files
SKILL.md

Coding Standards & Best Practices

Universal coding standards applicable across all projects. Detailed patterns and examples are in the references/ directory.

Quick Decision Guide

What you needReference file
Naming, immutability, types, error handling, asyncreferences/typescript-patterns.md
Components, hooks, state, memoization, lazy loadingreferences/react-patterns.md
REST API design, file structure, testing, code smellsreferences/api-testing-patterns.md

Categories

TypeScript/JavaScript Patterns

Variable and function naming conventions, immutability (critical), comprehensive error handling, async/await best practices, type safety, comments/documentation style, and database query performance.

See: references/typescript-patterns.md

React Patterns

Functional component structure with typed props, custom hooks (useDebounce pattern), proper state updates with functional setters, conditional rendering without ternary chains, useMemo/useCallback memoization, and lazy loading with Suspense.

See: references/react-patterns.md

API Design, Testing & Code Smells

REST conventions, consistent ApiResponse format, Zod input validation, project file organization and naming, AAA test pattern, descriptive test naming, and anti-pattern detection (long functions, deep nesting, magic numbers).

See: references/api-testing-patterns.md

Core Principles

  1. Readability First -- self-documenting code over comments
  2. KISS -- simplest solution that works
  3. DRY -- extract and reuse common logic
  4. YAGNI -- build only what is needed now
  5. Immutability -- never mutate; always spread

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