backend-module-standards
Enforce this repository's TypeScript backend module architecture standards. Use whenever creating, modifying, refactoring, or reviewing backend code under `server/`, including routes, services, modules, repositories, shared backend code, and backend tests. Do not apply these rules to frontend code or non-backend scaffolding.
Оригинален текст · няма потвърден превод на българскиПърво прочетете инструкцията.
Файлът се зарежда от посочения източник само по ваше действие. Можете да го прочетете тук, да го копирате или да го запазите като .md.
GitHub хранилище- Звезди на репото
- 13 785
- Лиценз
- AGPL-3.0
- Последна проверка на записа
- 20.09.2026 г.
Добавете в своя инструмент.
Командата отваря избора на skills от репозитория. Прочетете файла и условията на автора преди изпълнение.
npx skills add siteboon/claudecodeuiСтраницата копира текст. Не инсталира и не изпълнява нищо на устройството ви.
Откъс от SKILL.md
Началото на файла на автора, без превод.
Backend Module Standards
Apply these rules after the repository's basic scaffolding is in place. Limit them to backend code under server/. Preserve the requested task scope: make touched and newly generated backend code compliant without performing an unrelated repository-wide migration.
Inspect before editing
- Identify the owning feature module and its existing barrel, services, routes, and tests.
- Search for existing shared types, interfaces, and utilities before adding any definition.
- Search for every consumer before changing a module's public exports.
Organize backend modules
- Place each feature in
server/modules/<feature>/. - Use TypeScript for every file inside
server/modules/. Do not add JavaScript backend module files. - When touched JavaScript utilities belong to the work, migrate them to TypeScript. Place a one-use utility in its sole component; place a utility used in at least two locations in
server/shared/utils.ts. - Give every feature module an
index.tsbarrel that exposes only its required public API. - Import another feature module only through that module's
index.ts. Never deep-import another module's routes, services, repositories, adapters, or internal files. - Treat
server/shared/as the shared module. Keep shared definitions inserver/shared/types.ts,server/shared/interfaces.ts, andserver/shared/utils.ts, and expose only required cross-module members through its barrel. - Do not create module-local
types.ts,interfaces.ts, orutils.tsfiles. - Keep module-private implementation details unexported.