pp-typescript

Standardize TypeScript naming, type constructs, file layout, and test placement.

Updated Jun 12, 2026

Search Tags:#typescript #testing #architecture #refactoring #coding standards

Ready to run

npx skills add https://github.com/phillippelevidad/ai-led-engineering --skill pp-typescript

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: pp-typescript
Source: https://github.com/phillippelevidad/ai-led-engineering/tree/main/skills/pp-typescript
Command: npx skills add https://github.com/phillippelevidad/ai-led-engineering --skill pp-typescript

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This skill eliminates inconsistency and technical debt in TypeScript codebases by providing a unified set of authoring standards for naming, type constructs, file layout, and testing.

Core Features & Use Cases

Standardized Authoring: Ensures all new TypeScript code follows strict typing, named exports, and top-down file ordering.
Context-Aware Refactoring: Provides guidance on how to align existing code with standards only when touching specific lines, preventing unnecessary churn.
Use Case: When adding a new service or module, use this skill to ensure the implementation uses branded types, discriminated unions, and colocated tests that match the existing project architecture.

Quick Start

Apply the pp-typescript standards to the current file to ensure all naming conventions and type constructs align with the project requirements.

Frequently Asked Questions about pp-typescript

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

FAQPage Schema

How do I enforce consistent TypeScript coding standards across my project?▼

Standardize TypeScript authoring conventions by applying unified rules for naming, type constructs, file layout, and test placement. This eliminates inconsistency and technical debt by enforcing strict typing, explicit return types, and named exports across all .ts and .tsx files.

What are the best practices for structuring TypeScript files and tests?▼

Best practices for TypeScript file structure include top-down file ordering and colocated behavioral tests. Files should use strict typing, named exports, branded types, and discriminated unions to align with project architecture and maintain clear module boundaries.

How do I refactor existing TypeScript code without unnecessary churn?▼

Refactor existing TypeScript code by aligning only the specific lines you are modifying with project standards. This context-aware approach prevents unnecessary churn by updating naming conventions and type constructs only where you are actively touching the code.

Does this TypeScript standards enforcement work with both .ts and .tsx files?▼

Yes, these TypeScript coding standards apply to all .ts and .tsx file generation, modification, and refactoring tasks. The conventions ensure strict typing and explicit return types are enforced consistently across both standard TypeScript and React JSX environments.

When should I use branded types and discriminated unions in TypeScript?▼

Use branded types and discriminated unions when adding new services or modules to ensure robust type safety. These standardized type constructs satisfy strict typing requirements and help align new implementations with your existing project architecture seamlessly.