typescript-zero-fat

Enforce zero-fat TypeScript standards banning comments, any, and relative imports.

Updated Jan 19, 2026
One-click install
npx skills add https://github.com/KAFKA2306/yt3 --skill typescript-zero-fat
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: typescript-zero-fat
Source: https://github.com/KAFKA2306/yt3/tree/main/.agent/skills/typescript-zero-fat
Command: npx skills add https://github.com/KAFKA2306/yt3 --skill typescript-zero-fat

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates drifting, brittle TypeScript code by enforcing a strict "zero-fat" standard so types, names, and structure express intent rather than comments or defensive holes. It prevents silent failures, inconsistent configuration, and fragile relative imports that make refactors and reviews costly.

Core Features & Use Cases

  • Opinionated code standards: Prohibits comments and JSDoc for business intent, bans any usage, forbids try-catch in business logic, and disallows hardcoded values and relative imports.
  • Tooling alignment: Targets Bun runtime, Biome linting, and tsc --strict type checking with Zod validation at system boundaries to guarantee runtime safety.
  • Use Case: Run this protocol during code generation or PR review to ensure new or refactored TypeScript functions follow strict typing, centralized config, and schema validation before merging.

Quick Start

Run the TypeScript Zero-Fat review whenever generating or editing TypeScript in the repository to enforce no comments, no any, no try-catch in business logic, absolute imports, and centralized configuration usage.

Frequently Asked Questions about typescript-zero-fat

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

FAQPage Schema
How do I enforce strict TypeScript linting rules that ban comments and any types?

To enforce strict TypeScript linting, this Skill bans comments, any types, try-catch in business logic, hardcoded values, and relative imports. It targets Bun, Biome, and tsc --strict to ensure types and structure express intent without defensive holes.

Can I use Biome and tsc --strict together for TypeScript code review?

Yes, you can use Biome and tsc --strict together for TypeScript code review. This Skill aligns with Biome linting and tsc --strict type checking, enforcing strict typing and centralized config usage during PR reviews and code generation workflows.

How do I prevent try-catch blocks and relative imports in TypeScript projects?

Preventing try-catch blocks and relative imports in TypeScript requires an opinionated code standard. This Skill forbids try-catch in business logic and disallows relative imports, enforcing absolute imports and eliminating silent failures during refactoring.

Does Zod validation work with Bun runtime for TypeScript boundary checking?

Zod validation works with Bun runtime for TypeScript boundary checking. This Skill enforces Zod validation at system boundaries alongside Bun runtime and tsc --strict, guaranteeing runtime safety and schema validation before merging new or refactored code.

What is the best way to eliminate defensive code holes in TypeScript?

The best way to eliminate defensive code holes in TypeScript is enforcing a zero-fat standard. This Skill bans any usage, comments, and try-catch in business logic, ensuring types and names express intent rather than relying on defensive programming patterns.

When should I not use automated TypeScript code standards enforcement?

You should not use automated TypeScript code standards enforcement when your project relies on JSDoc comments for documentation generation, requires try-catch blocks for critical error handling, or needs relative imports for specific module resolution strategies outside Bun and Biome ecosystems.