tailrocks-typescript-best-practices
Apply strict TypeScript 7 and React language/UI policy when writing in-scope code involving state, runtime validation, typed failure, readonly APIs, or async ownership. Not review, refactoring, migration, project tooling, or backend business logic.
- License
- Apache-2.0
Pinned to revision 41768afec488, so it is the text this page describes rather than whatever the author pushed since.
Files
- skills/tailrocks-typescript-best-practices/SKILL.md
- skills/tailrocks-typescript-best-practices/agents/openai.yaml
- skills/tailrocks-typescript-best-practices/references/boundaries-and-domain-values.md
- skills/tailrocks-typescript-best-practices/references/mutation-and-api-safety.md
- skills/tailrocks-typescript-best-practices/references/react-and-async.md
- skills/tailrocks-typescript-best-practices/references/runtime-trust.md
- skills/tailrocks-typescript-best-practices/references/state-and-errors.md
- skills/tailrocks-typescript-best-practices/references/testing.md
Every link opens the file at its source, pinned to the revision this page describes.