Individual skill
typescript-source-organization
Apply, review, and explain TypeScript source organization conventions. Use automatically for tasks involving feature-based organization, code colocation, import paths, import sorting, monorepos, or frontend and backend project structure.
skills/typescript-source-organization/SKILL.md
Source commit 170074a0df9b07f4a4a78e3596ec1edf06a14da7
What was checked
- Matches the observed repository HEAD
- Yes
- Scanner rules are current
- No
- Repository scan complete
- No
- Skill scan complete
- No
- Observed behavior
- Not checked yet
- Last checked
- Nov 4, 2026
These are observations at the recorded commit, not a guarantee of safety. Review the source before running it.
Install this skill
Choose an agent in your Stack or copy a command below. Commands fetch the pinned commit and copy only this skill directory. Existing destinations are refused. Copying a command does not install anything.
An install command is unavailable: current rules, complete repository and skill scans, an eligible behavior level and a permitted license are required.
Repository context
- Repository stars (not skill ratings)
- 785
- Repository last updated
- Sep 3, 2026
- License
- MIT
Observed agent integration: No specific integration evidence. Standard SKILL.md installation does not imply verified compatibility.
- coding-conventions Repository topic
- coding-guidelines Repository topic
- reactjs Repository topic
- typescipt Repository topic
- style-guide Repository topic
- nodejs Repository topic
- ai Repository topic
- ai-agent Repository topic
- ai-skill Repository topic
- ai-tools Repository topic
- engineering Derived category
Files and excerpt
File metadata and permitted, redacted excerpts come from the recorded scan. Source links are pinned to that commit.
Read excerpt
# Source Organization
Apply the TypeScript Style Guide's source organization conventions in the context of the current task.
## Workflow
1. Inspect the consuming repository's existing structure, framework conventions, and configuration.
2. Let explicit repository conventions take precedence over this opinionated guidance.
3. Apply, review, or explain only the guidance relevant to the task.
4. State important tradeoffs when organization depends on project size, framework, or team conventions.
## Boundaries
- Keep formatting and linting tools responsible for import sorting when configured.