What problem does it solve? It prevents TypeScript codebases from degrading into disorganized files with mixed responsibilities, barrel re-exports, and monolithic React components by enforcing single-responsibility file organization and feature-based folder structure. ## Core Features & Use Cases - Feature-based file placement: Maps every new source file to the correct frontend or backend folder (views, components, hooks, use-cases, repositories) based on behavior ownership. - React componentization rules: Enforces view/page orchestration versus presentational component splits, narrow props, and role-based naming for UI files. - Quality gate references: Provides dedicated guidance for performance-sensitive code and security-sensitive code (auth, input validation, secrets handling). - Use Case: When adding a new order-tracking screen, use this Skill to place the view under features/<feature>/views/, extract UI regions into sibling component files, colocate owned types, and wire direct imports without creating barrel files. ## Quick Start Ask the AI to create or refactor a TypeScript component, hook, or backend use-case following the writing-typescript skill's SRP and feature-folder rules.
