frontend-conventions

Standardize frontend coding practices across the monorepo.

Updated Mar 5, 2026

Search Tags:#ui #frontend #standards #coding #conventions #lint

Ready to run

npx skills add https://github.com/johwer/marketplace --skill frontend-conventions-johwer

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: frontend-conventions
Source: https://github.com/johwer/marketplace/tree/main/skills/frontend-conventions
Command: npx skills add https://github.com/johwer/marketplace --skill frontend-conventions-johwer

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Frontend coding conventions across the Repo monorepo reduce inconsistencies, onboarding time, and maintenance costs.

Core Features & Use Cases

Standardized component naming, file structure, and styling rules
Lint presets, templates, and example snippets to accelerate development
Use Case: New UI feature or library module can be implemented following the project-wide conventions

Quick Start

Follow the repository's frontend conventions to create a new UI component with the standard naming, structure, and wiring.

Frequently Asked Questions about frontend-conventions

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

FAQPage Schema

How do I standardize frontend coding conventions across a monorepo?▼

Standardize frontend coding conventions across a monorepo by applying consistent component APIs, naming standards, and folder layouts. This reduces inconsistencies and maintenance costs across apps and packages.

What are frontend UI component standards and when do I need them?▼

Frontend UI component standards are rules for naming, file structure, and styling. You need them when implementing new UI features or library modules to ensure code organization remains consistent and onboarding time is reduced.

How do I set up lint presets and templates for UI code consistency?▼

Set up lint presets and templates for UI code consistency by loading provided example snippets and config presets into your developer workspace. This accelerates development by enforcing standard styling and tooling rules.

Does this work for any frontend project or only monorepo environments?▼

This works primarily for monorepo environments containing multiple apps and packages. It standardizes component APIs and tooling across the repository, ensuring consistent code organization for new UI features and library modules.

What is the best way to organize frontend folder layouts and naming conventions?▼

The best way to organize frontend folder layouts and naming conventions is to apply standardized presets for component structure and wiring. This ensures consistent code organization across the monorepo and accelerates development.