agentleFS
axrmxvaxrmxv/claude-config/skills/standards-typescript/SKILL.md

standards-typescript

Skill1 starsChanged 4 months agoMITView on GitHub

TypeScript coding standards — strict mode, no any or as assertions, readonly and as const immutability, discriminated unions, zod validation at boundaries, Vitest/Jest with 80% coverage, Prettier and ESLint. Use when writing, reviewing, or testing TypeScript or TSX code.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    No any: Prefer unknown and narrow.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

TypeScript Standards

The TypeScript delta over the always-loaded rules in .claude/rules/common/. The camelCase / PascalCase / UPPER_SNAKE_CASE conventions and the immutability principle already live in common/ — this layer adds the TypeScript mechanisms and compiler settings only.

What applies immediately

  • strict: true in tsconfig.json. Non-negotiable.
  • No any. Prefer unknown and narrow. Do not silence the checker with as assertions or // @ts-ignore — fix the type.
  • A type is not a runtime guarantee. Validate and narrow external input (request bodies, query params, env vars, third-party responses) with a runtime schema such as zod, and derive the static type from the schema so the two cannot drift.
  • Never eval, new Function, or string arguments to setTimeout / setInterval.
  • readonly on what you expose; as const for literal and config objects.

Reference files

FileCovers
coding-style.mdType safety, immutability mechanisms, types vs interfaces, tooling
patterns.mdStructural interfaces, DTO types, Result discriminated unions, zod at boundaries
security.mdType-safe boundaries, dangerous APIs, prototype pollution, npm audit
testing.mdVitest/Jest, coverage command, compile-time type tests
hooks.mdPostToolUse Prettier/ESLint/tsc hooks, console.log warnings

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.