Skip to content

GravionLabs/elysion / .agents/skills/ts-implementation

ts-implementation

Verified

TypeScript 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} then npx --no-install eslint --fix {files}
  • Check (read-only): npx --no-install prettier --check {files} and npx --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} / check npx 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 (-Check for the check commands; not-configured, override: references/format.md of implementation)

Imports

  • ES modules only — import not require
  • Relative imports carry the .js extension (import { foo } from "../foo.js") only when moduleResolution is NodeNext/Node16; with bundler (Vite, Angular) follow the project

Conventions

  • Types: never any. Use explicit interfaces or type aliases.
  • Async: async/await only, 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 — use unknown and narrow; strict: true in tsconfig.json
  • No floating promises; async functions propagate or handle errors
  • ESM import only; path.join/path.resolve for file paths
  • No eval()/new Function(); validate input before queries, paths, shell commands
  • Tests isolated with specific assertions (not just toBeTruthy()) — rules in ts-test
finishing-a-development-branchobra/superpowersUse when implementation is complete, all tests pass, and you need to decide how to integrate the workStars: 319kUpdated Claude CodeCodexVerifiedInstall
systematic-debuggingobra/superpowersUse when encountering any bug, test failure, or unexpected behavior, before proposing fixesStars: 319kUpdated Claude CodeCodexVerifiedInstall
test-driven-developmentobra/superpowersUse when implementing any feature or bugfix, before writing implementation codeStars: 319kUpdated Claude CodeCodexVerifiedInstall
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: 196kUpdated Claude CodeCodexVerifiedInstall