typescript-standards

Enforce TypeScript strict typing and naming conventions across a monorepo.

Updated Jan 15, 2026

Search Tags:#typescript #frontend #backend #type-safety #coding-standards #prisma #shared-types

Ready to run

npx skills add https://github.com/feraudet/ssii --skill typescript-standards-feraudet

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: typescript-standards
Source: https://github.com/feraudet/ssii/tree/main/.claude/skills/typescript-standards
Command: npx skills add https://github.com/feraudet/ssii --skill typescript-standards-feraudet

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This document codifies TypeScript conventions used across the monorepo to ensure consistent typing, safer code, and easier maintenance.

Core Features & Use Cases

Enforces strict type safety with strict: true, prefers unknown over any, and as const for immutable literals
Standardizes naming conventions for interfaces, types, and enums across backend and frontend
Aligns Prisma types and shared types to enable reliable cross-project integration

Quick Start

Follow the project conventions when introducing new types to ensure alignment with all workspaces.

Frequently Asked Questions about typescript-standards

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I enforce consistent TypeScript types across a monorepo?▼

To enforce consistent TypeScript types across a monorepo, apply shared conventions to both backend and frontend workstreams. This standardizes interfaces, requires strict typing, and aligns Prisma types with shared definitions to ensure reliable cross-project integration.

What TypeScript coding standards improve type safety in frontend and backend projects?▼

Type safety standards include enabling strict: true, preferring unknown over any, and using as const for immutable literals. These conventions standardize naming for interfaces and enums across your workstreams to ensure safer code.

How do I align Prisma types with shared TypeScript definitions?▼

Align Prisma types with shared TypeScript definitions by applying monorepo conventions that standardize naming and interfaces. This ensures reliable cross-project integration by keeping backend types consistent with shared utilities.

Why should I prefer unknown over any in TypeScript coding standards?▼

Prefer unknown over any in TypeScript coding standards to enforce strict type safety without bypassing the compiler. Using unknown requires explicit type checking, which results in safer code and easier maintenance across your monorepo.

When do I need standardized TypeScript conventions for cross-project integration?▼

You need standardized TypeScript conventions for cross-project integration when adding new types or APIs across backend and frontend workspaces. This ensures consistent interfaces and shared utilities, enabling reliable integration within a monorepo.