agentleFS
Sign inStart free
zekhoizekhoi/claude/.agents/skills/kit-typescript-rules/SKILL.md

kit-typescript-rules

Skill0 starsChanged 20 days agoMITView on GitHub

TypeScript conventions for this project. Use when reading, writing, or reviewing files matching `**/*.ts`, `**/*.tsx`, `**/*.mts`, `**/*.cts`. Do not use for other files.

We split this skill into the rules it gives an agent

6 rules. About 0 are common, 3 are distinctive, and 3 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    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:

    Follow the project's tsconfig strictness.

    line 8
  2. Very specific:

    Avoid any. Use unknown at untrusted boundaries and narrow it with type guards or the project's validation library.

    line 9
  3. Distinctive:

    Prefer types inferred from runtime schemas or existing declarations over duplicated hand-written types.

    line 10
  4. Very specific:

    Use non-null assertions (!) only where an invariant guarantees a value.

    line 11
  5. Distinctive:

    Keep exported APIs explicitly typed.

    line 13
  6. Distinctive:

    Run the project's type check after changes, not only the tests.

    line 16

≈ “Common” is an estimate: at least 1 in 5 of the 308,232 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 conventions

  • Follow the project's tsconfig strictness. Do not loosen compiler options or add @ts-ignore / @ts-expect-error to silence errors without a comment explaining why.
  • Avoid any. Use unknown at untrusted boundaries and narrow it with type guards or the project's validation library.
  • Prefer types inferred from runtime schemas or existing declarations over duplicated hand-written types.
  • Use non-null assertions (!) only where an invariant guarantees a value; prefer explicit checks.
  • Model alternatives with discriminated unions rather than optional flags that can contradict each other.
  • Keep exported APIs explicitly typed; let local variables infer.
  • Match the project's module system (ESM or CommonJS) and import style, including file extensions where required.
  • Handle rejected promises: await them, return them, or attach handling. Do not leave floating promises.
  • Run the project's type check after changes, not only the tests.

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