SuperAPI AI Directory

ts-dev

Coding & development

View repository

Updated 10-16 06:21

About this skill

TS Dev

When implementing, modifying, or initializing a TypeScript frontend, use this Skill as the project standard. In existing projects, prioritize the existing UI library, build configuration, CI, and test setup, and add only the missing standards.

Process-specific references

Depending on the task, read the necessary reference first.

  • New creation, adding dependencies, UI foundation selection: setup.md
  • Vite+ / vp usage, verification, troubleshooting: vite-plus.md
  • Implementation, JSDoc/TSDoc, comments, public utilities: implementation.md
  • Oxlint/Oxfmt/tsgo configuration, recommended lint rules, applying to existing configuration: lint-rules.md
  • pre-commit, tests, Playwright, vulnerability updates, GitHub Actions: verification.md

When adding rules in the future, add the details to the process-specific reference, andSKILL.md write only the reference destination and applicable timing.

Always applied

  • Write JSDoc/TSDoc for functions, components, and public utilities. Explain the purpose, arguments, and return values, and also write about exceptions and side effects if any.
  • When writing comments, write in Japanese, and write reasons and cautions rather than a word-for-word explanation of the code.
  • If you change the behavior of a public utility, docs/ leave the usage and changes in
  • Use Playwright for UI/E2E tests.
  • Git hookは pre-commit use, and do not use husky.

Application procedure

  1. Read the reference for the applicable process.
  2. If it conflicts with the existing project's configuration, introduce the differences while preserving the existing intent.
  3. In a Vite+ project, always vite-plus.md の vp confirm the prerequisites before choosing commands.
  4. When creating or changing Oxlint/Oxfmt/tsgo configuration, always lint-rules.md check the recommended rules and CLI execution paths, and apply them to the configuration in a form where the reasons for adoption or rejection are clear.
  5. After changes, verification.md run the lightweight checks, and leave a reason for anything that cannot be run.