skills.rest
WesleySmits
WesleySmitsCOMMUNITY
Explore all skills by this author →
Website𝕏@iamwesleysmitsGitHub

typescript-standards

Enforce TypeScript coding standards across the Oh My Brand! WordPress FSE theme codebase.

Updated Jan 5, 2026
Search Tags:#typescript#linting#frontend#type-safety#coding-standards#style-guide#web-components
One-click install
npx skills add https://github.com/WesleySmits/oh-my-brand-wp-fse --skill typescript-standards-wesleysmits
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: typescript-standards
Source: https://github.com/WesleySmits/oh-my-brand-wp-fse/tree/main/.github/skills/typescript-standards
Command: npx skills add https://github.com/WesleySmits/oh-my-brand-wp-fse --skill typescript-standards-wesleysmits

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

TypeScript coding standards for the Oh My Brand! WordPress FSE theme ensure consistency, readability, and safety by enforcing strict typing, interfaces, and shared patterns across components and utilities.

Core Features & Use Cases

  • Enforces strict mode, explicit typing, and interfaces for all TS files.
  • Provides naming conventions, private fields usage, and comprehensive documentation guidance.
  • Use during component development, editor patterns, and web components to maintain maintainable code.

Quick Start

Enforce the TypeScript standards across the codebase by running the standard checks during development.

Frequently Asked Questions about typescript-standards

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

FAQPage Schema
How do I enforce TypeScript coding standards across a WordPress FSE theme codebase?▼

You enforce TypeScript coding standards by applying strict mode, explicit typing, and interfaces across all components, utilities, and web components to ensure consistency, readability, and safety.

What TypeScript naming conventions should I use for components and editor patterns?▼

TypeScript naming conventions for components and editor patterns specify using private fields, explicit typing, and interfaces to maintain readable and maintainable code across the codebase.

Does this style guide require strict mode and explicit typing for all TypeScript files?▼

Yes, the style guide requires strict mode and explicit typing for all TypeScript files, applying these rules to components, utilities, web components, and editor patterns during development and code reviews.

When do I need to use interfaces and private fields in TypeScript web components?▼

You need interfaces and private fields in TypeScript web components to enforce type safety, maintain strict structural contracts, and prevent unintended external access to component internals.

How do I co-locate tests with TypeScript components during development?▼

You co-locate tests with TypeScript components by placing test files alongside the components themselves, following the specified documentation guidelines and coding standards to ensure maintainable code.

Related Skills

Explore More Software Engineering Skills→
WesleySmitsWesleySmits

php-standards

Enforce PHP coding standards for WordPress theme development.

Community
Advanced
pluto-atom-4pluto-atom-4

review-code

Lint, type-check, and validate accessibility in Next.js projects.

Community
Advanced
ianyimiianyimi
1

Global Tech Stack

Enforce coding standards for the global tech stack in Claude Code.

Community
Basic
tianhuiltianhuil

ts-coding-skill

Enforces a TypeScript Node.js coding standard covering type safety and functional patterns.

Community
Advanced