lwc-well-architected

Enforce atomic design hierarchy and naming conventions for Salesforce Lightning Web Components.

Updated Apr 19, 2026
One-click install
npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill lwc-well-architected
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: lwc-well-architected
Source: https://github.com/cchrisv/professorFlowVisualPicker/tree/main/.agents/skills/lwc-well-architected
Command: npx skills add https://github.com/cchrisv/professorFlowVisualPicker --skill lwc-well-architected

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Traditional LWC development often results in monolithic, hard-to-maintain components without clear scalability paths. This skill provides an atomic design framework to structure components for reuse and consistency.

Core Features & Use Cases

  • Defines a clear hierarchy (Atom, Molecule, Organism, Template, Page, Utility, Flow) and naming convention to standardize component design.
  • Guides use cases including creation, refactoring, code review, Jest testing, and Flow integration for CPE components.
  • Supports accessibility, SLDS compliance, and cross-context rendering for desktop and mobile use.

Quick Start

Adopt the {app}{Level}{PascalName} naming scheme and organize files accordingly to begin building reusable LWCs.

Frequently Asked Questions about lwc-well-architected

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

FAQPage Schema
How do I structure Salesforce LWC components for better scalability and maintainability?

Structure Salesforce LWC components using an atomic design framework that organizes elements into atoms, molecules, organisms, templates, pages, and utilities to enable reuse and consistency. This approach replaces monolithic components with a scalable, maintainable UI architecture.

What is the best way to name Lightning Web Components in an atomic design hierarchy?

Name Lightning Web Components using the {app}{Level}{PascalName} naming scheme to standardize component design across atoms, molecules, organisms, templates, pages, utilities, and Flow-integrated components. This convention clarifies role responsibilities per hierarchy level.

How do I refactor monolithic LWC components into reusable atoms and molecules?

Refactor monolithic LWC components by applying the atomic design framework to break down large UI structures into discrete atoms, molecules, and organisms. Use the framework's review checklist to guide component creation and ensure role responsibilities are correctly assigned.

Does this LWC atomic design framework support Salesforce Flow integration?

Yes, the LWC atomic design framework supports Salesforce Flow integration and provides specific guidance for building Flow bridging and Custom Property Editor (CPE) components. It ensures components integrate correctly within Flow-driven processes.

Can I use atomic design for LWC code reviews and Jest testing?

Yes, you can use atomic design for LWC code reviews and Jest testing as the framework includes a comprehensive review checklist and testing guidance. This ensures components meet accessibility, SLDS compliance, and cross-context rendering requirements for desktop and mobile.