Skip to content
TrustedSkillsbeta
Back to all skills

Busirocket Typescript Standards

Listed
busirocket·vlatest·backend

Enforces Busirocket's TypeScript coding standards and best practices for robust, maintainable backend codebases.

Repository

Install on your platform

Showing Claude Code. One command installs this skill into any of the agents below.

  1. 1

    Run this in your project

    terminal
    $ npx skills add busirocket/agents-skills --skill busirocket-typescript-standards -a claude-code

  2. Uses the open-source skills CLI and needs Node.js. Add -g to install it for your user instead of this project.

What we know about this skill

Publisher

busirocket

Taken from the source listing. We haven't verified who controls this account.

Install target

Live repository

Not pinned. Installing fetches whatever the repository holds at the time you run the command.

No human has reviewed this code. The checks below are a static scan of the files at one commit — nobody has run this skill or judged whether it works. A skill runs with whatever access you give your agent, so read the source before you install it.

Automated safety checks

scanned

This skill failed 1 of 6 checks. A failure is not proof of bad intent; it means something in the code needs a human to look at it before you run it.

  • Declares what it does: failed

    SKILL.md frontmatter is missing description.

    SKILL.md exists, its frontmatter parses, and it declares a name and a description.

  • No undeclared network calls: passed

    Makes no network calls.

    Every host the skill dials — from its scripts, its config endpoints or the commands it tells the agent to run — is either well-known package and API infrastructure or declared in its own frontmatter. Links in documentation are not counted.

  • No obfuscated payloads: passed

    No encoded or obfuscated payloads.

    No base64, hex or compressed blob is decoded and then executed, and no encoded shell commands.

  • No credential access: passed

    Reads no keys, tokens, keychains or credential files.

    Neither the code nor the SKILL.md instructions read SSH keys, cloud credentials, keychains, token stores, browser cookie databases or dotfiles that hold secrets.

  • No pipe-to-shell installers: passed

    No pipe-to-shell or download-and-run installers.

    No `curl … | sh` pattern, in the code or in the instructions, that runs code fetched at run time.

  • Pinned to a commit: passed

    Scanned busirocket/agents-skills at d5e3054ad2.

    The exact upstream commit SHA that was scanned is recorded, so the result refers to specific bytes.

Commit
d5e3054ad2
Manifest
skills/busirocket-typescript-standards/SKILL.md
Scanned
12 files, 671 lines
This is a static scan, not a review. It reads the skill's files; it does not run them, and it cannot tell you whether the skill is any good or whether the code does what its description says. A skill runs with whatever access you give your agent.
What each check looks for →

About this skill

What it does

This skill enforces Busirocket's TypeScript and React coding standards, ensuring robust and maintainable backend codebases. It provides strict, reusable rules for projects involving .ts and .tsx files, promoting consistency in type naming, result shapes, and overall project structure. The skill is particularly helpful when working with Next.js applications where specific file types allow for extra exports.

When to use it

  • When writing or refactoring TypeScript/React code (.ts / .tsx).
  • To move inline types into dedicated type files.
  • For enforcing consistent type naming and result shapes across your project.
  • While working on Next.js projects, especially when dealing with special files like app/**/page.tsx or app/api/**/route.ts.

Key capabilities

  • Enforces one exported symbol per file for modules.
  • Prohibits inline interfaces and types in components, hooks, utils, services, and route handlers.
  • Mandates shared shapes to be placed under the types/<area>/... directory (one type per file).
  • Discourages barrel files (index.ts) to maintain dependency visibility.
  • Provides specific exceptions for Next.js special files allowing extra exports.
  • Includes rules covering language style, one-thing-per-file structure, types strictness, helper usage, and Next.js hygiene.
  • Defines conventions for type naming (Params, Result, Error, Props) and result shapes for boundaries that can fail.

Example prompts

  • "Enforce Busirocket TypeScript standards on this file."
  • "Check if this component adheres to the Busirocket Typescript Standards regarding inline types."
  • "Review my Next.js route handler (app/api/example/route.ts) for compliance with Busirocket's coding standards."

Tips & gotchas

  • After making meaningful changes, always run your project’s standard checks (e.g., yarn check:all).
  • Refer to the individual rule files (located in rules/) for detailed explanations and code examples of each standard. These files provide context and best practices beyond the core rules.