agentleFS
Sign inStart free
aprameyakaprameyak/coding-skills/typescript-strict/SKILL.md

typescript-strict

Skill1 starsChanged 41 days agoMITView on GitHub

Write strict, idiomatic TypeScript. Use when editing TS/TSX code, fixing type errors, or designing shared types.

13 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use react-patterns and git-workflow.

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.
  • xenitV1Skill

    react-patterns

    Modern React patterns and principles. Hooks, composition, performance, TypeScript best practices.

    Also in 3 projects that use this

  • Microsoft AzureSkill

    git-workflow

    Squad branching model: dev-first workflow with insiders preview channel

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

5 rules. 0 are common, 2 are distinctive, and 3 are very specific to this project.

  • 0

    Common

    Most of the 13 edited versions we read keep these.

  • 2

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

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

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

    Prefer unknown over any; narrow before use.

    line 10
  2. Very specific:

    Avoid type assertions unless boundary-validated.

    line 12
  3. Distinctive:

    Keep shared types near their source of truth.

    line 13
  4. Very specific:

    Use readonly and as const where immutability helps.

    line 14
  5. Distinctive:

    Prefer typed errors and result shapes over thrown strings.

    line 16

“Common” is measured: kept by at least 6 in 10 of the 13 edited versions of this file we could read. “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 Strict

Rules

  • Prefer unknown over any; narrow before use.
  • Model domain data with precise types and discriminated unions.
  • Avoid type assertions unless boundary-validated; justify each as.
  • Keep shared types near their source of truth; do not duplicate.
  • Use readonly and as const where immutability helps.
  • Exhaustiveness-check switches on unions.
  • Prefer typed errors and result shapes over thrown strings.

Avoid

  • Disabling strict or broad eslint-disable to silence errors
  • Huge utility-type puzzles that hurt readability
  • Optional fields that should be required states in a union

Checklist

  • tsc / typecheck passes for touched packages
  • Public exports have intentional, stable types
  • No new any unless required at a typed boundary by the repo

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