New: 97,000+ skills indexed from GitHub repos with 100+ stars · every skill safety-checkedBrowse top skillsTop skills
Esc to closeBrowse all skills
Submit a skillBrowse skills
Submit a skillBrowse skills

Agent skill

Siteboon Backend Module Standards

by siteboon in siteboon/claudecodeui

Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

AGPL-3.0Auto-check passedDevelopment

Install Siteboon Backend Module Standards

skills CLI
$ npx skills add siteboon/claudecodeui --skill backend-module-standards -a claude-code

Project install by default; add -g for ~/.claude/skills/.

GitHub CLI
$ gh skill install siteboon/claudecodeui backend-module-standards --agent claude-code

Project scope by default; add --scope user for a personal install. Needs GitHub CLI 2.90.0 or later (public preview).

Manual copy
$ git clone --depth 1 https://github.com/siteboon/claudecodeui.git skills-src && mkdir -p .claude/skills && cp -r skills-src/.agents/skills/backend-module-standards .claude/skills/backend-module-standards && rm -rf skills-src

Use ~/.claude/skills/ instead of .claude/skills for a personal install. The folder must contain SKILL.md.

Claude Code skills documentation · loads skills from .claude/skills/

Facts

Skill name
backend-module-standards
GitHub stars
14k
Token cost
~1.2k tokens
SKILL.md length
587 words
Files
2
Skills in repo
2
Repo updated
First seen
Licence
AGPL-3.0

At a glance

Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong.

  • Works in 3 steps: Identify the owning feature module and… → Search for existing shared types,… → Search for every consumer before…
  • Creating a new backend feature module in this repository
  • SKILL.md covers Inspect before editing, Organize backend modules, Place types, interfaces, and… and Design exports deliberately, plus 3 more sections
  • Calls npm

What it does

The skill applies only to backend code under server/ and is meant to make touched or newly generated code compliant without turning into a repository-wide migration. Before editing, it has the agent identify the owning feature module and its existing barrel, services, routes and tests, search for existing shared types and utilities before adding new ones, and find every consumer before changing a module's public exports.

Organization rules put each feature in server/modules/<feature>/, require TypeScript throughout (migrating any touched JavaScript utility), and give every module an index.ts barrel exposing only its intended public API; other modules must be imported only through that barrel, never by deep-importing routes, services or repositories directly. server/shared/ holds cross-module types, interfaces and utilities in fixed files (types.ts, interfaces.ts, utils.ts), and module-local files with those same names are disallowed.

Further rules cover when to use type versus interface, export type and import type conventions, and moving a definition to shared only once it is used in two or more places, each with a documented purpose and constraints.

When your agent uses it

  • Creating a new backend feature module in this repository
  • Refactoring backend code under server/ to follow the module standards
  • Reviewing a pull request that touches server/ for architecture compliance
  • Deciding whether a type or utility belongs in a module or in server/shared/

Example prompts

  • “Create a new billing feature module under server/modules following our standards.”
  • “Review this PR's changes under server/ for barrel and shared-type violations.”
  • “This utility is now used in two routes. Move it to server/shared/utils.ts.”

Requirements

  • A TypeScript backend codebase organized under server/

Workflow steps

3 steps, taken from the first numbered list in SKILL.md.

  1. Identify the owning feature module and its existing barrel, services, routes, and tests.
  2. Search for existing shared types, interfaces, and utilities before adding any definition.
  3. Search for every consumer before changing a module's public exports.

What it can do on your machine

Read from SKILL.md and the folder at commit dc7cb6c. It shows what the files ask for, not the result of running them.

  • Tool permissions

    Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

    From allowed-tools in the SKILL.md frontmatter.

  • Runs code

    Shell commands in SKILL.md call:

    • npm

    From the folder's file list and the shell code blocks in SKILL.md.

  • Network

    No URLs in SKILL.md. Its commands use npm, which can reach the network depending on how they are called.

    From URLs in SKILL.md, links to its own repository left out.

  • Credentials

    Names no API keys, tokens, secrets or passwords.

    From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

Context cost

Siteboon Backend Module Standards loads about 1.2k tokens when it runs. Until then it costs about 88 tokens; SKILL.md has 587 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it
~88
When it runs · the whole SKILL.md, loaded when a task matches
~1.2k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

Auto-check passed

The automated check found no risky patterns in SKILL.md.

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from siteboon/claudecodeui at commit dc7cb6c, republished under its AGPL-3.0 licence (© siteboon). 587 words, ~1,170 tokens.

Download SKILL.mdSave it as .claude/skills/backend-module-standards/SKILL.md (or your agent's skills folder). This skill also uses 1 other file; get the full folder from GitHub.
name
backend-module-standards
description
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.

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

  1. Identify the owning feature module and its existing barrel, services, routes, and tests.
  2. Search for existing shared types, interfaces, and utilities before adding any definition.
  3. 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.ts barrel 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 in server/shared/types.ts, server/shared/interfaces.ts, and server/shared/utils.ts, and expose only required cross-module members through its barrel.
  • Do not create module-local types.ts, interfaces.ts, or utils.ts files.
  • Keep module-private implementation details unexported.

Place types, interfaces, and utilities

  • Use type by default. Use interface only for a contract that a class is intended to implement.
  • Use export type for type exports and import type for type-only imports.
  • Define a type, interface, or utility directly in its component file when it is used in only that location.
  • Move a type or interface used in two or more locations to server/shared/types.ts or server/shared/interfaces.ts as appropriate.
  • Move a utility used in two or more locations to server/shared/utils.ts.
  • Do not duplicate an existing shared definition to avoid importing it.
  • Give every shared type, interface, and utility a detailed doc comment explaining its behavior, valid usage, and important constraints.
  • Keep related shared definitions adjacent. Introduce each group with //----------------- DESCRIPTION OF GROUP ------------ and separate unrelated groups with // ---------------------------.
Show full SKILL.md (254 more words)Show less

Design exports deliberately

  • Export a function or variable at its declaration, such as export function loadSession(). Do not collect ordinary exports at the end of an implementation file.
  • The preceding rule does not apply to index.ts barrel exports.
  • For every exported component, add a brief comment at its definition naming the consuming module or modules and explaining why they use it. Update the comment when consumers change.
  • Do not export speculative helpers, implementation details, or symbols that have no cross-file consumer.
  • Use clear, specific names for functions and variables. Add a concise comment anywhere intent, ordering, invariants, or edge cases could be confusing.

Keep routes thin

  • Parse and validate transport input in the route, convert it to the service's expected typed input, call one or more services, and translate the result to the response.
  • Keep business logic, persistence, filesystem work, subprocess execution, and orchestration out of routes.
  • Allow a service to call other services. Access another module's services through that module's public barrel contract.

Test within the module

  • Put feature tests in server/modules/<feature>/tests/.
  • Add or update unit tests for changed service behavior and route parsing.

Verify the result

Before finishing:

  1. Confirm all cross-module imports use index.ts barrels and all public exports are necessary and documented.
  2. Confirm shared definitions follow the one-use versus multiple-use placement rule and grouping-comment format.
  3. Confirm routes only parse, call services, and format responses.
  4. Run the narrow relevant tests, then npm run build, npm run typecheck, and npm run lint when the task scope and environment permit.

© siteboon, AGPL-3.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file in .agents/skills/backend-module-standards of siteboon/claudecodeui.

  • SKILL.md
  • agents/openai.yaml

Open the folder on GitHubat commit dc7cb6c

Compare with similar skills

Siteboon Backend Module Standards next to the 5 skills that share the most tags, products or categories with it. Stars are the repository's; “used in” counts other GitHub owners with a copy.

Siteboon Backend Module Standards compared with similar skills
SkillStarsUsed inTokensAuto-checkLicenceRepo updated
Siteboon Backend Module Standards this skillsiteboon/claudecodeui14k—~1.2kAutomated safety check: PassAGPL-3.0
System Designaiskillstore/marketplace430—~1.1kAutomated safety check: PassNone
Mirage VFS Adapter Authoringstrukto-ai/mirage3.7k—~2.4kAutomated safety check: PassApache-2.0
Evolutionary Modular Architecturetech-leads-club/agent-skills7k—~3.7kAutomated safety check: PassCC-BY-4.0
Control Flow Diagramsslopus/happy24k—~654Automated safety check: PassMIT
Create Saleor Packagesaleor/apps162—~608Automated safety check: PassCustom licence

Similar skills

  • System Design

    aiskillstore/marketplace

    CTO's deputy for software architecture using Clean/Hexagonal Architecture principles.

    430 GitHub stars~1.1k tokensUpdated today
    DevelopmentAuto-check passed

  • Mirage VFS Adapter Authoring

    strukto-ai/mirage

    Builds or extends a custom Mirage virtual filesystem adapter for an API, database, object store or app data, with a working mount configuration and filesystem tests.

    3.7k GitHub stars~2.4k tokensUpdated today
    DevelopmentAuto-check passed

  • Evolutionary Modular Architecture

    tech-leads-club/agent-skills

    Guides design of modular-monolith platforms with DDD, flat-by-aggregate modules, anti-corruption layers, outbox events and resilience, plus an architecture document with SVG diagrams.

    7k GitHub stars~3.7k tokensUpdated 17 days ago
    DevelopmentAuto-check passed

  • Control Flow Diagrams

    slopus/happy

    Traces how an action moves through your code and draws it as a compact ASCII tree: functions called, payload types, state changes and components that re-render.

    24k GitHub stars~654 tokensUpdated today
    DevelopmentAuto-check passed

  • Create Saleor Package

    saleor/apps

    Scaffold a new shared package in the saleor-apps monorepo under ./packages/.

    162 GitHub stars~608 tokensUpdated 6 days ago
    DevelopmentAuto-check passed

  • Upgrade Starter Kit

    workadventure/map-starter-kit

    Upgrade a WorkAdventure map repository to the latest version of the map-starter-kit (github.com/workadventure/map-starter-kit) - refreshes package.json dependencies, vite/tsconfig/build config, CI…

    156 GitHub stars~1.3k tokensUpdated 5 days ago
    DevelopmentAuto-check: notes

More from siteboon/claudecodeui

  • Frontend Module Standards

    siteboon/claudecodeui

    Enforces one repository's React and TypeScript module layout for code under src/: source-root imports, feature barrels, deliberate exports and no deep imports.

    14k GitHub stars~2.6k tokensUpdated 2 days ago
    Auto-check passed

Works with

Categories

Questions about Siteboon Backend Module Standards

What does Siteboon Backend Module Standards do?

Enforces this repository's TypeScript backend module architecture under server/: feature folders, barrel exports, and where shared types and utilities belong. The skill applies only to backend code under server/ and is meant to make touched or newly generated code compliant without turning into a repository-wide migration. Before editing, it has the agent identify the owning feature module and its existing barrel, services, routes and tests, search for existing shared types and utilities before adding new ones, and find every consumer before changing a module's public exports.

When should I use Siteboon Backend Module Standards?

Siteboon Backend Module Standards fits situations like: creating a new backend feature module in this repository; refactoring backend code under server/ to follow the module standards; reviewing a pull request that touches server/ for architecture compliance; deciding whether a type or utility belongs in a module or in server/shared/.

How do I install Siteboon Backend Module Standards in Claude Code?

Run `npx skills add siteboon/claudecodeui --skill backend-module-standards -a claude-code`. Or copy the skill folder (.agents/skills/backend-module-standards in siteboon/claudecodeui) into .claude/skills/backend-module-standards in your project. Claude Code loads it when a task matches its description.

How do I install Siteboon Backend Module Standards in Codex?

Run `npx skills add siteboon/claudecodeui --skill backend-module-standards -a codex`. Or copy the skill folder (.agents/skills/backend-module-standards in siteboon/claudecodeui) into .agents/skills/backend-module-standards in your project. Codex loads it when a task matches its description.

Can I use Siteboon Backend Module Standards in Cursor, Gemini CLI or GitHub Copilot?

Cursor, Gemini CLI, GitHub Copilot and OpenCode also load SKILL.md folders. With the skills CLI, run `npx skills add siteboon/claudecodeui --skill backend-module-standards -a cursor` (or -a gemini-cli, github-copilot or opencode for the others). To copy it by hand, put the folder in .cursor/skills/backend-module-standards, .gemini/skills/backend-module-standards, .github/skills/backend-module-standards and .opencode/skills/backend-module-standards in your project.

What does Siteboon Backend Module Standards need to run?

Going by SKILL.md and its folder, Siteboon Backend Module Standards needs the command-line tools its instructions call (npm). Our summary lists: A TypeScript backend codebase organized under server/.

Does Siteboon Backend Module Standards access the network?

SKILL.md contains no URLs. Its commands use npm, which can reach the network depending on how they are called. This is read from the text; nothing was executed.

Is Siteboon Backend Module Standards safe to install?

Our automated static check of SKILL.md found no risky patterns, such as piping downloads into a shell, reading credential files or hidden Unicode. It is not a guarantee. Review the folder before installing.

What licence does Siteboon Backend Module Standards use?

Siteboon Backend Module Standards is published under the AGPL-3.0 licence (the repository's licence). It allows redistribution, so the full SKILL.md is shown on this page.

How many tokens does Siteboon Backend Module Standards use?

About 1.2k tokens (SKILL.md is roughly 4.7k characters). Agents keep only the skill's name and description in context until a task matches; then they load SKILL.md in full.

What are the alternatives to Siteboon Backend Module Standards?

Skills that share tags, products or a category with Siteboon Backend Module Standards: System Design (aiskillstore/marketplace, 430 stars), Mirage VFS Adapter Authoring (strukto-ai/mirage, 3.7k stars), Evolutionary Modular Architecture (tech-leads-club/agent-skills, 7k stars) and Control Flow Diagrams (slopus/happy, 24k stars). The comparison table on this page puts their stars, adoption, token cost, safety result and licence side by side.

Who maintains Siteboon Backend Module Standards?

siteboon (a GitHub organization) maintains it in siteboon/claudecodeui, which has 13,962 GitHub stars. The repository holds 2 skills in this directory. The repository was last updated on October 5, 2026.

Source: siteboon/claudecodeui on GitHub. Facts on this page come from the repository at the commit we read; the author's words are quoted as theirs.