BTMuliBTMuli/TeyvatGuide/.agents/skills/typescript-standards/SKILL.md

typescript-standards

Skill428 starsChanged 10 days agoMITView on GitHub

Write and review TypeScript and Vue code using TeyvatGuide's ESLint, Prettier, type declaration, const-enum, runtime-value, and TSDoc conventions. Use when changing .ts, .d.ts, or .vue files, especially types, enums, exported APIs, and Vue state.

We split this skill into the rules it gives an agent

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

0
Common
Most of the 9 edited versions we read keep these.
0
Distinctive
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Read ../../rules/typescript-rules.md, source metadata rules, and the nearest code before editing.
line 8
Very specific:
Treat eslint/vueEslint.js, .prettierrc.yml, and tsconfig.json as executable sources of truth when prose and configuration differ.
line 10
Very specific:
Use Array<T>, type, explicit public function types, and angle-bracket assertions where an assertion is unavoidable.
line 12
Very specific:
Do not add native TypeScript enum.
line 16
Very specific:
Read TSDoc conventions when adding or changing functions, types, or exported declarations.
line 18
Very specific:
Use package.json's since (never version) for changed file headers and affected declaration tags.
line 19

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

Read ../../rules/typescript-rules.md, source metadata rules, and the nearest code before editing.
Treat eslint/vueEslint.js, .prettierrc.yml, and tsconfig.json as executable sources of truth when prose and configuration differ.
Use Array<T>, type, explicit public function types, and angle-bracket assertions where an assertion is unavoidable. Prefer narrowing and unknown first.
Reuse shared types from src/types/<Domain>/*.d.ts (or an existing plugin types directory) and keep file-local types near their use; do not create Types/ or a separate types.ts just for types.
Do not add native TypeScript enum. Read enum patterns when adding a value set or mapping declaration-space values to runtime objects.
Read TSDoc conventions when adding or changing functions, types, or exported declarations. Use package.json's since (never version) for changed file headers and affected declaration tags; non-Vue functions changed without docs need a short TSDoc, while Vue files keep the documented header exception.
Preserve NodeNext .js import extensions, follow the grouping enforced by import-x/order, and use import type { ... } for type-only imports.
Respect the ESLint TS error rules: no unused variables or expressions (including short-circuit/ternary chains), no @ts-ignore/@ts-nocheck or description-less @ts-expect-error, no runtime namespaces (declare only in .d.ts), and as const/<const> over literal type assertions.
Validate with pnpm lint-vue and pnpm lint:code; add pnpm lint:style when Vue styles change.

Download now (ZIP)

Other versions9 projects use a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 9
TangleML/tangle-ui★ 104same name
AlemTuzlak/skills★ 45same name
LiorCohen/sdd★ 43same name
jackleekopij/claude-skills★ 3same name
motola10/claude-code-base★ 1same name
rkdxodud-tyk/SKILLS★ 1same name
sapientsai/panel-mcp-server★ 1same name
alexander-zuev/agent-skills★ 0same name
gerardbalaoro/skills★ 0same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository10 other files it gives its agents.
- AGENTS.mdAGENTS.md
- fluent2-designSkill
- frontend-designSkill
- git-workflowSkill
- sentry-mcpSkill
- tauri-connectorSkill
- testingSkill
- teyvat-guideSkill
- vue3-standardsSkill
- web-design-guidelinesSkill

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