skills.rest
evrendom
evrendomCOMMUNITY
Explore all skills by this author →
Website𝕏@evrendomGitHub

typescript-standards

Enforce TypeScript coding standards for named exports, imports, and type safety.

289|16|Updated Feb 16, 2026
Search Tags:#typescript#refactoring#type-safety#coding-standards#coding-conventions#named-exports#static-imports
One-click install
npx skills add https://github.com/evrendom/rudel --skill typescript-standards-evrendom
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-standards
Source: https://github.com/evrendom/rudel/tree/main/.claude/skills/typescript-standards
Command: npx skills add https://github.com/evrendom/rudel --skill typescript-standards-evrendom

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

TypeScript projects often diverge in style and safety; this Skill provides a centralized set of standards to enforce consistent, type-safe code across teams, reducing bugs and onboarding time.

Core Features & Use Cases

  • Enforces named exports and explicit public interfaces.
  • Promotes static and type-only imports to improve tree-shaking and readability.
  • Provides rules for naming conventions and discriminated unions to ensure robust type safety.
  • Use Case: When auditing a large TS codebase, apply these standards to align modules and simplify refactoring.

Quick Start

Apply the TypeScript standards to new and existing code to ensure compliance.

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 coding standards across a large monorepo?▼

TypeScript coding standards are enforced by applying centralized rules for named exports, type-only imports, and naming conventions across all modules. This reduces style divergence and simplifies refactoring in large monorepos.

What are the best TypeScript type-safety conventions for reducing bugs during refactoring?▼

Type-safety conventions for refactoring include deriving types from schemas, using discriminated unions, and discouraging type casts. These practices ensure robust static analysis and prevent runtime type errors.

Why should I use named exports and type-only imports in a TypeScript codebase?▼

Named exports and type-only imports improve TypeScript codebase readability and tree-shaking. They enforce explicit public interfaces and ensure only necessary types are bundled, optimizing bundle size.

Can I apply these TypeScript coding rules to an existing library for an audit?▼

You can apply these TypeScript coding rules to existing libraries during an audit. The standards help align existing modules with consistent naming conventions and type-safety practices to streamline onboarding.

When do I need to derive types from schemas instead of manually defining them?▼

Deriving types from schemas is needed when enforcing robust type safety and avoiding manual type casts. This practice ensures your TypeScript interfaces remain synchronized with your data structures during refactoring.

Related Skills

Explore More Software Engineering Skills→
korchasakorchasa
3

flow-setup-agent-code-style-ts-strict

Inject TypeScript strict mode code style rules into AGENTS.md files.

Community
Basic
flutterflutter
2.8k

dart-run-static-analysis

Run Dart static analysis and apply automated lint fixes.

Official
Intermediate
theodrosyimertheodrosyimer

type-driven-zod-boundaries

Pair TypeScript domain types with Zod v4 schemas to validate module boundaries.

Community
Advanced
mDevsLabsmDevsLabs
1

typescript

Enforce TypeScript style and strict type-safety across TS/TSX/MTS projects.

Community
Intermediate