Kurocado Studio Engineering Style Guide
NPM | |
Repository | |
Releases |
A single, enforceable baseline for TypeScript projects—packaged as installable presets, shareable configs, and CI-ready workflows. Designed for internal teams, external contributors, and clients to ship with consistency by default.
Why this Style Guide
Onboard any repo to studio standards in minutes.
Keep formatting, linting, and commits aligned across projects.
Reduce review noise and drift with automated checks.
What’s included
TypeScript (tsconfig) presets — strict, sensible defaults for apps and packages.
ESLint + Prettier configs — curated rules that balance correctness and DX.
Commit conventions (commitlint) — Conventional Commits for clean history and automation.
GitHub Actions starters — lint, test, and release workflows ready to drop in.
Templates — Remix, NestJS, and NPM package scaffolds; CodeSandbox-friendly starters for rapid prototyping.
How it powers the Platform
Every platform module inherits this baseline—so QA, IAM, DevOps, and DX utilities all converge on the same standards. Any repository (inside or outside the platform) can adopt it and stay aligned over time.
See also: Kurocado Studio Platform
Use cases
Internal team adoption — the definitive reference for design & engineering standards.
External contributor alignment — freelancers and partners match studio expectations on day one.
Client collaboration — clients can fork and publish a variant (e.g., @ORG/CLIENT_NAME_STYLEGUIDE) without breaking the baseline.
Quick prototyping (CodeSandbox) — ready-to-run templates for fast iteration that still follow best practices.