writing-clean-ts
Skill0 starsChanged 3 months agoNo licenceView on GitHub
Expert in TypeScript codebase patterns for backend and frontend: services, repositories, DALs, entities, models, enums, controllers, handlers, use cases, app boot, React components, and UI screens. Make sure to use this skill whenever the user mentions TypeScript, Node.js, Express, TypeORM, Electron, React, React Router, React Native, Expo, creating an API endpoint, building a feature, CRUD operations, or codebase architecture - even if they don't say "clean architecture". Also use it when creating a new project or package from scratch (scaffolding, folder structure, lint setup), when extending or refactoring existing TypeScript (moving code between layers, renaming, splitting big files, constants/config/env, enums, singletons), when reviewing it against these conventions, and when cleaning it up - the same rule set governs creating, editing, extending, and cleanup, so code written with this skill must come out of a cleanup pass with nothing to fix. Also use it for linting setup (ESLint, Prettier, json-sort-cli, lint scripts), and for ES module / import path setup (#src alias, absolute imports, tsconfig paths, "type": "module"). For tests, use the contract-testing-ts skill.
In this repository11 other files it gives its agents.
- ai-documentationSkill
- commit-messageSkill
- mom-test-coachSkill
- mono-repo-typescriptSkill
- orchestrating-ts-agentsSkill
- planning-storiesSkill
- plantuml-diagrammingSkill
- speed-datingSkill
- writing-clean-shellSkill
- writing-tech-specsSkill
- writing-woodpecker-ciSkill
The file
We split this skill into the rules it gives an agent
5 rules. About 0 are common, 2 are distinctive, and 3 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.
≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.
Does it work?
Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.
No reviews yet
People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.
- It worked
- Partly
- It didn't
Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.
Your trail
Files you open will collect here, so you can find them again.
Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.
Now do this for your own.
Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

