stand-ts
Skill1 starsChanged 11 days agoMITView on GitHub
TypeScript and JavaScript standards. Use when writing TS/JS code. Covers strict mode, type patterns, error handling, imports, naming, testing, React conventions, and package management with bun.
In this repository41 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- analyze-codeSkill
- analyze-projectSkill
- analyze-testsSkill
- audit-mergesSkill
- babysit-prSkill
- backlogSkill
- branchSkill
- coderabbitSkill
- commitSkill
- greptileSkill
- implement-issuesSkill
- issueSkill
- jiraSkill
- lintro-addSkill
- lintro-reviewSkill
- lintro-verifySkill
- lintSkill
- properizeSkill
- pr-raycastSkill
- prSkill
- raycastSkill
- rebaseSkill
- reconcileSkill
- scorecardSkill
- stand-ciSkill
- stand-generalSkill
- stand-odinSkill
- stand-pySkill
- stand-rustSkill
- sweep-prsSkill
- test-apiSkill
- test-shellSkill
- testSkill
- test-ui-qsfSkill
- test-uiSkill
- turbo-addSkill
- turbo-testSkill
- turbo-verifySkill
- which-prSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
18 rules. About 0 are common, 6 are distinctive, and 12 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
12
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 15
Prefer bun over npm
- Very specific: line 16
Use bun install instead of npm install
- Very specific: line 28
Prefer interface for object shapes.
- Very specific: line 30
Use satisfies over as for type narrowing — preserves the inferred type while validating the shape
- Very specific: line 32
Avoid enum — use as const objects instead:
- Distinctive: line 49
Prefer discriminated unions over optional fields for state modeling
- Very specific: line 53
Use unknown in catch clauses, not any:
- Distinctive: line 65
Never swallow errors with empty catch blocks
- Very specific: line 66
Prefer typed error results (Result<T, E> pattern) over thrown exceptions for expected failure paths
- Very specific: line 71
Use type-only imports for types: import type { Foo } from "./foo".
- Very specific: line 72
Avoid barrel files (index.ts re-exports) in libraries — they defeat tree-shaking and obscure dependency graphs
- Very specific: line 89
Follow the lint skill for linting and formatting workflow.
- Distinctive: line 93
Prefer Vitest over Jest
- Distinctive: line 94
Use test functions, not test classes
- Very specific: line 96
Use beforeEach / afterEach for shared setup/teardown
- Very specific: line 97
Use it.each or test.each for parameterized tests
- Distinctive: line 117
When working in React codebases:
- Distinctive: line 120
Prefer hooks over HOCs and render props
≈ “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 / JavaScript Standards
Standards for TypeScript and JavaScript code.
Package Manager
- Prefer
bunovernpm - Use
bun installinstead ofnpm install - Use
bun runinstead ofnpm run - Use
bunxinstead ofnpx
Strict Mode
- Enable
strict: trueintsconfig.json - No
anyescape hatches without justification — if unavoidable, add a comment explaining why
Type Patterns
- Prefer
interfacefor object shapes; usetypefor unions, intersections, and mapped types - Use
satisfiesoverasfor type narrowing — preserves the inferred type while validating the shape Avoid
enum— useas constobjects instead:// Good const Status = { Active: "active", Inactive: "inactive", } as const; type Status = (typeof Status)[keyof typeof Status]; // Avoid enum Status { Active = "active", Inactive = "inactive", }- Prefer discriminated unions over optional fields for state modeling
Error Handling
Use
unknownin catch clauses, notany:// Good catch (err: unknown) { if (err instanceof SpecificError) { ... } } // Bad catch (err: any) { ... }- Never swallow errors with empty catch blocks
- Prefer typed error results (
Result<T, E>pattern) over thrown exceptions for expected failure paths
Imports
- Use type-only imports for types:
import type { Foo } from "./foo"; - Avoid barrel files (
index.tsre-exports) in libraries — they defeat tree-shaking and obscure dependency graphs
Naming
PascalCasefor types, interfaces, classes, and React componentscamelCasefor variables, functions, and methodsUPPER_SNAKE_CASEfor constants and environment variable names- Prefix boolean variables/props with
is,has,should,can
Formatting Rules
- More than 1 arg/param requires a trailing comma (consistent with the
stand-pyskill) - Be explicit with named arguments in object parameters when more than 1 property
Linting
Follow the lint skill for linting and formatting workflow.
Testing
- Prefer Vitest over Jest
- Use test functions, not test classes
- Leverage
describeblocks for grouping, not class hierarchies - Use
beforeEach/afterEachfor shared setup/teardown - Use
it.eachortest.eachfor parameterized tests
// Good
describe("parseConfig", () => {
it("returns defaults for empty input", () => {
expect(parseConfig({})).toEqual(defaults);
});
it.each([
{ input: "yes", expected: true },
{ input: "no", expected: false },
])("parses '$input' as $expected", ({ input, expected }) => {
expect(parseBoolean(input)).toBe(expected);
});
});React
When working in React codebases:
- Function components only — no class components
- Prefer hooks over HOCs and render props
- Named exports for components (no
export default) - Co-locate component, styles, and tests in the same directory
- Extract custom hooks when logic is reused across components
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.

