lang-tsx

Standardize React and TSX component structure, typing, and architecture.

Updated Mar 19, 2026
One-click install
npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-tsx
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lang-tsx
Source: https://github.com/dragoscirjan/opencode-config/tree/main/skills/lang-tsx
Command: npx skills add https://github.com/dragoscirjan/opencode-config --skill lang-tsx

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill prevents inconsistent React and TSX patterns by giving you a clear, opinionated standard for component structure, typing, and architecture.

Core Features & Use Cases

  • Frontend Standards: Guides React and TSX code toward predictable, maintainable conventions.
  • Typing Discipline: Encourages explicit prop types and careful hook typing when inference is not enough.
  • Component Design: Supports functional components only, composition over prop drilling, and colocated styles and tests.
  • Tooling Alignment: Matches common TypeScript and React tooling such as Prettier, eslint-plugin-react, and typescript-eslint.
  • Use Case: Use it when building a new React feature, refactoring a component tree, or reviewing TSX code for consistency.

Quick Start

Ask the assistant to apply lang-tsx standards to your React component or TSX file and enforce functional components, explicit prop typing, and composition-first structure.

Frequently Asked Questions about lang-tsx

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

FAQPage Schema
How do I standardize React and TSX component structure for maintainability?

To standardize React and TSX code, enforce functional components, explicit prop typing, and composition-first architecture, aligning with linting and formatting guidance for maintainable frontend codebases.

What is the best way to type React hooks in TypeScript?

The best way to type React hooks in TypeScript is using careful hook annotations when inference is not enough, ensuring explicit typing for complex state and effect dependencies in TSX codebases.

Does this approach work with eslint-plugin-react and typescript-eslint?

Yes, this approach works with eslint-plugin-react and typescript-eslint by aligning frontend standards with common TypeScript and React tooling like Prettier to enforce consistent formatting and linting rules.

How do I enforce explicit prop typing in functional React components?

To enforce explicit prop typing in functional React components, apply strict typing discipline by defining explicit prop interfaces, avoiding implicit any types, and using careful annotations for complex component structures.

When should I use composition over prop drilling in React applications?

You should use composition over prop drilling in React applications when building new features or refactoring component trees, adopting a composition-first structure to prevent inconsistent patterns and maintain predictable frontend architecture.