fe-code-conventions

Enforce naming, return types, and module organization conventions in React projects.

Updated Apr 27, 2026
One-click install
npx skills add https://github.com/Conradmaker/copilot-cockpit --skill fe-code-conventions
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: fe-code-conventions
Source: https://github.com/Conradmaker/copilot-cockpit/tree/main/.github/skills/fe-code-conventions
Command: npx skills add https://github.com/Conradmaker/copilot-cockpit --skill fe-code-conventions

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Frontend code often becomes hard to read and maintain as a project grows; this Skill provides a structured set of conventions to keep naming, structure, and logic clear, consistent, and scalable.

Core Features & Use Cases

  • Guides readability improvements by reducing context, naming ambiguities, and messy conditionals.
  • Supports predictable refactoring and cohesive module organization across React projects.
  • Serves as a reusable reference for code reviews, planning, and onboarding new engineers.

Quick Start

Apply these conventions to your current frontend codebase to start improving readability and maintainability immediately.

Frequently Asked Questions about fe-code-conventions

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

FAQPage Schema
How do I enforce frontend code quality and maintainability in a growing React project?

Apply structured coding conventions to your React codebase to enforce consistent naming, disciplined return types, and clear module organization, improving readability and predictability as the project scales.

What are the best frontend coding standards for reducing messy conditionals and naming ambiguities?

Effective frontend coding standards reduce context and naming ambiguities by enforcing explicit gating rules and disciplined return types, ensuring conditionals remain clean and logic stays predictable during refactoring.

How do I set up cohesive module organization for React refactoring and code reviews?

Use a reusable convention reference that defines clear module organization and explicit gating rules, guiding cohesive refactoring and providing a consistent standard for code reviews and onboarding.

Can I use these coding conventions for onboarding new engineers to an existing React codebase?

Yes, these coding conventions serve as a reusable reference for onboarding new engineers, providing structured rules for naming, structure, and logic that make the existing React codebase easier to read and understand.

When should I apply strict coding conventions to my frontend codebase?

Apply coding conventions when your frontend code becomes hard to read and maintain as the project grows, using structured rules to keep naming, structure, and logic clear, consistent, and scalable during refactoring.