agentleFS
Sign inStart free
TheOnlyFusionCubeTheOnlyFusionCube/potetos-for-everyone/skills/typescript-best-practices/SKILL.md

typescript-best-practices

Skill18 starsChanged 53 days agoMITView on GitHub

Apply disciplined TypeScript modeling and boundary parsing. Use when reading or editing TypeScript.

We split this skill into the rules it gives an agent

5 rules. 0 are common, 4 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 22 edited versions we read keep these.

  • 4

    Distinctive

    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. Distinctive:

    Prefer discriminated unions for mutually exclusive states and exhaustive handling for closed variants.

    line 8
  2. Very specific:

    Avoid widening useful literal information and avoid any as an escape hatch.

    line 10
  3. Distinctive:

    Use generics only when they express a real relationship between inputs and outputs.

    line 12
  4. Distinctive:

    Keep async/error states explicit at the public boundary.

    line 13
  5. Distinctive:

    Test behavior through exported APIs, not private helper choreography.

    line 14

“Common” is measured: kept by at least 6 in 10 of the 22 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 Best Practices

  • Parse unknown external data at the boundary; keep unknown until validated.
  • Prefer discriminated unions for mutually exclusive states and exhaustive handling for closed variants.
  • Give domain meaning to primitives when accidental mixing would be costly.
  • Avoid widening useful literal information and avoid any as an escape hatch.
  • Let callers consume one coherent return shape instead of correlated optional fields.
  • Use generics only when they express a real relationship between inputs and outputs.
  • Keep async/error states explicit at the public boundary.
  • Test behavior through exported APIs, not private helper choreography.

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