Skills
.Work. You
Rest

rule-frontend-types

Community

Standardize frontend types across the codebase.

Software Engineering#typescript#architecture#frontend#type-safety#coding-standards#types
Authorbtabaska
Version1.0.0
Installs0

System Documentation

What problem does it solve?

In large frontend codebases, inconsistent type placement, naming, and API contract handling lead to duplication and integration errors. This skill provides a centralized set of conventions for organizing TypeScript types to improve maintainability and cross-team collaboration.

Core Features & Use Cases

  • Shared types live under frontend/src/types/ with domain subfolders when needed; component-local types stay with their components to avoid polluting global type space.
  • API envelopes should use snake_case to mirror backend contracts, while UI state and props use camelCase; mapping happens at the service boundary.
  • Clear naming rules promote consistency (PascalCase for interfaces/types, camelCase for values; avoid I-prefixed interfaces, avoid T-prefixed type aliases).

Quick Start

Define shared types under src/types following the naming conventions, and map API data to UI types at the service boundary.

Dependency Matrix

Required Modules

None required

Components

Standard package

💻 Claude Code Installation

Recommended: Let Claude install automatically. Simply copy and paste the text below to Claude Code.

Please help me install this Skill:
Name: rule-frontend-types
Download link: https://github.com/btabaska/simpler-grants-documentation-automation/archive/main.zip#rule-frontend-types

Please download this .zip file, extract it, and install it in the .claude/skills/ directory.
View Source Repository

Agent Skills Search Helper

Install a tiny helper to your Agent, search and equip skill from 471,000+ vetted skills library on demand.