GravionLabs/elysion / .agents/skills/ts-implementation
ts-implementation
VerifiedTypeScript implementation and test rules (Vitest) extending `implementation`. Use when writing or changing TypeScript or Node.js code.
Framework
- Tests: Vitest — see
ts-test - Format/Lint: Biome for plain TypeScript (
setup-biome-husky); ESLint (flat config) + Prettier when the project already uses them or is Angular (setup-prettier-eslint-husky) — see## Format
Format
- Extensions: prettier
.ts .tsx .js .mjs .cjs .jsx .json .css .html; eslint only.ts .tsx .js .mjs .cjs .jsx - Format:
npx --no-install prettier --write {files}thennpx --no-install eslint --fix {files} - Check (read-only):
npx --no-install prettier --check {files}andnpx --no-install eslint {files} - Biome project (
biome.json[c], the default for new plain-TS projects):npx biome check --write --no-errors-on-unmatched {files}/ checknpx biome check --no-errors-on-unmatched {files}; never run prettier on the same files - Run after green tests, before the commit:
pwsh <implementation dir>/scripts/Format-Changed.ps1 -Language ts(-Checkfor the check commands; not-configured, override: references/format.md ofimplementation)
Imports
- ES modules only —
importnotrequire - Relative imports carry the
.jsextension (import { foo } from "../foo.js") only whenmoduleResolutionisNodeNext/Node16; withbundler(Vite, Angular) follow the project
Conventions
- Types: never
any. Use explicit interfaces or type aliases. - Async:
async/awaitonly, no raw.then(). - File naming:
kebab-case.ts.
Tests
Runner config, test file naming, mocking and coverage live in ts-test.
Review rules
- 🔴 Lint run (
Format-Changed.ps1 -Lint -Language ts, ESLint or Biome) exits non-zero: error-level findings; 🟡 warning-level findings - No
any— useunknownand narrow;strict: trueintsconfig.json - No floating promises; async functions propagate or handle errors
- ESM
importonly;path.join/path.resolvefor file paths - No
eval()/new Function(); validate input before queries, paths, shell commands - Tests isolated with specific assertions (not just
toBeTruthy()) — rules ints-test
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the work | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixes | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation code | Stars: 319k | Updated | Claude CodeCodex | Verified | Install |
| skill-creatoranthropics/skillsCreate new skills, modify and improve existing skills, and measure skill performance. Use when users want to create a skill from scratch, edit, or optimize an existing skill, run evals to test a skill, benchmark skill performance with variance analysis, or optimize a skill's description for better triggering accuracy. | Stars: 196k | Updated | Claude CodeCodex | Verified | Install |