tech-typescript
Skill1 starsChanged 28 days agoMITView on GitHub
Technology skill loaded when working in a TypeScript codebase.
In this repository29 other files it gives its agents.
- exec-accessibilitySkill
- exec-architectureSkill
- exec-code-reviewSkill
- exec-debuggingSkill
- exec-documentationSkill
- exec-performanceSkill
- exec-refactoringSkill
- exec-repo-patternsSkill
- exec-securitySkill
- exec-testingSkill
- exec-ui-uxSkill
- exec-verificationSkill
- tech-dockerSkill
- tech-flutterSkill
- tech-goSkill
- tech-graphqlSkill
- tech-kotlinSkill
- tech-nextjsSkill
- tech-nodeSkill
- tech-postgresSkill
- tech-pythonSkill
- tech-reactSkill
- tech-rustSkill
- tech-swiftSkill
- tech-tailwindSkill
- tech-vueSkill
- linear-spanks-gitSkill
- linear-spanksSkill
- linear-workflowSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 11
When writing TypeScript, adhere to strict typing constraints:
- Very specific: line 13
No
any: Never use the any type. Use unknown if the type is truly dynamic, and narrow it down with type guards. - Very specific: line 14
Strict Null Checks: Always handle null and undefined explicitly.
- Very specific: line 15
Interfaces vs Types: Use interface for object shapes and class contracts.
- Distinctive: line 16
Generics: Use generics to create reusable, type-safe functions instead of duplicating logic.
≈ “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.
Files
TypeScript Best Practices
Apply this skill after inspecting repository conventions and supported versions. Treat its rules as defaults unless they protect a concrete safety property; preserve an established project pattern when it conflicts, and record the reason in the implementation plan.
When writing TypeScript, adhere to strict typing constraints:
- No
any: Never use theanytype. Useunknownif the type is truly dynamic, and narrow it down with type guards. - Strict Null Checks: Always handle
nullandundefinedexplicitly. - Interfaces vs Types: Use
interfacefor object shapes and class contracts. Usetypefor unions, intersections, and primitives. - Generics: Use generics to create reusable, type-safe functions instead of duplicating logic.
- Inference: Rely on TypeScript's type inference for simple variable assignments; don't over-annotate.
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
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.