القائمة
Enforces TypeScript and project-specific coding standards, including Bun usage and the zero-warning policy. Use this skill when creating or modifying any TypeScript or configuration files.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
| name | typescript-conventions |
| description | Enforces TypeScript and project-specific coding standards, including Bun usage and the zero-warning policy. Use this skill when creating or modifying any TypeScript or configuration files. |
This document outlines the coding standards and conventions used in Michael's TypeScript projects.
In Michael's TypeScript projects, we exclusively use Bun for all package management and script execution. NEVER use npm or yarn commands unless explicitly required by an external tool.
bun add <package>bun run <script>bun x <command>We follow a strict Zero Warning Policy. Warnings that do not fail the build are generally ignored and therefore useless.
All automated tools (TypeScript compiler, linting, etc.) MUST be configured to fail the build if any warning is detected. Problems should either be fixed properly or, if absolutely necessary, suppressed with an explicit reason; they should never be left as "just warnings".
After making any changes, you MUST validate the project using the available tooling, typically:
bun x tsc --noEmit to ensure TypeScript types are correct.nix flake check or bun run check (whichever is available in the specific project).testing skill guidelines.lefthook run pre-commit if applicable.Guidelines for Michael Vorburger's personal Git commit style.
Guidelines for Michael Vorburger's preferred Git workflow.
Java coding, testing, and logging conventions.
Guidelines for determining how to test a project based on its contents.
Update Nix flake inputs.
Conventions for naming files within the project.