Traction scoreGitHub stars can be faked, so popularity alone can be misleading. Traction Score looks for broader signs of recent attention, adoption, and active maintenance.
This collection provides a framework for implementing consistent naming conventions and function API designs in TypeScript. It helps developers maintain codebases by standardizing how identifiers, generic type parameters, and component responsibilities are handled.
The guide includes specific patterns for managing React props and state, as well as the use of discriminated unions to prevent invalid application states and ensure exhaustiveness checking.
WHO IT'S FOR
TypeScript developers
implementing consistent naming and function patterns
Frontend engineers
typing React props and managing component state
Technical leads
establishing coding standards for state management
Compatible AgentsThe repository documents support for these agents. The skills may also work with other agents that can load SKILL.md files, but they may need some setup or small changes.
Replace <path-to-typescript-file> with the path of a TypeScript file containing the function or functions to review.
Use the typescript-functions skill to review the functions in <path-to-typescript-file>. Respect the repository's existing conventions and give me one small, concrete refactoring recommendation focused on responsibility, explicit dependencies, side-effect isolation, argument design, or return types. Explain any important tradeoff; do not change unrelated code.
Replace <path-to-test-file> with the path of a TypeScript or TSX test file.
Use the typescript-tests skill to review <path-to-test-file>. Respect the repository's test runner and conventions, then identify up to three high-value improvements involving AAA structure, isolation, public behavior, query choice, descriptions, or snapshot use. Show a concise rewrite of one test when the supplied file provides enough context; do not rewrite unrelated tests.
Replace <path-to-project-or-feature> with the directory whose TypeScript source organization should be reviewed.
Use the typescript-source-organization skill to review the structure under <path-to-project-or-feature>. Respect the repository's framework and existing conventions. Recommend one limited improvement involving feature-based organization, code colocation, or relative versus absolute imports, and explain the tradeoff. Do not reorganize unrelated files.
Claude