code-style

Enforce code style conventions for components, functions, and destructuring patterns.

Updated Feb 25, 2026
One-click install
npx skills add https://github.com/ludicroushq/vertex --skill code-style-ludicroushq
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: code-style
Source: https://github.com/ludicroushq/vertex/tree/main/.agents/skills/code-style
Command: npx skills add https://github.com/ludicroushq/vertex --skill code-style-ludicroushq

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Code style conventions for components, functions, and destructuring patterns in frontend codebases to improve readability and maintainability.

Core Features & Use Cases

  • Enforced props destructuring: accept a single props variable and destructure it afterwards.
  • Function parameter patterns: prefer a single object parameter with named keys and destructure inside the function.
  • Review and onboarding: standardize code structure during reviews to reduce churn and ambiguity.

Quick Start

Run the code style checklist when starting a new component or reviewing code to ensure consistency.

Frequently Asked Questions about code-style

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

FAQPage Schema
How do I enforce consistent component and function style in a TypeScript codebase?

You can enforce consistent code style by standardizing props destructuring and function parameter patterns, aligning your React components and TypeScript signatures with linting rules and reviewer checklists to reduce ambiguity during code reviews.

What is the best way to standardize React component props destructuring during code reviews?

The best way to standardize React component props destructuring is to enforce accepting a single props variable and destructuring it afterwards, which reduces churn and ambiguity during code reviews and onboarding.

How do I standardize function parameter patterns in frontend development?

To standardize function parameter patterns in frontend development, prefer a single object parameter with named keys and destructure inside the function, ensuring typed signatures align with your coding standards and linting rules.

Does this code style convention work with existing linting rules and typing standards?

Yes, the code style conventions align directly with existing linting rules and typing standards, targeting frontend projects using typed signatures to improve readability and maintainability without conflicting with your current configuration.

When do I need to apply a code style checklist for TypeScript and React components?

You need to apply a code style checklist when starting a new React component, reviewing code, or onboarding new developers, ensuring consistent destructuring patterns and typed signatures throughout the development process.