solidjs-architecture

Organize SolidJS project structure and module boundaries for scalable apps.

Updated Apr 21, 2026
One-click install
npx skills add https://github.com/gregoryraymond/claude-agents-and-skills --skill solidjs-architecture
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: solidjs-architecture
Source: https://github.com/gregoryraymond/claude-agents-and-skills/tree/main/skills/solidjs-architecture
Command: npx skills add https://github.com/gregoryraymond/claude-agents-and-skills --skill solidjs-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Streamlines the organization of SolidJS/SolidStart projects by defining standard folder structure, module boundaries, and recommended placement of components, utilities, and server code.

Core Features & Use Cases

  • Establishes baseline app layout (public/, src/, routes/, app.config.ts, etc.) and recommended folders (components/, lib/, server/, stores/, styles/, types/).
  • Guides module boundaries and file-based routing practices to keep features decoupled.
  • Use Case: scaffolding a new SolidStart app or refactoring an existing one to align with consistent architecture.

Quick Start

Apply the SolidJS architecture guidelines when scaffolding a new app, reorganizing folders, or reviewing structural changes.

Frequently Asked Questions about solidjs-architecture

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

FAQPage Schema
What is the recommended folder structure for a scalable SolidStart app?▼

A scalable SolidStart app folder structure separates concerns into public/, src/, routes/, and app.config.ts, alongside components/, lib/, server/, stores/, styles/, and types/ directories to keep features decoupled.

How do I organize module boundaries in a SolidJS project?▼

Organize SolidJS module boundaries by placing shared utilities in lib/, state in stores/, and backend logic in server/, ensuring clear separation of client and server code to keep features decoupled.

How do I scaffold a new SolidStart project with proper routing?▼

Scaffold a new SolidStart project using file-based routing practices within the routes/ directory, establishing a baseline app layout that decouples features and defines standard module boundaries.

What is the best way to separate client and server code in SolidJS?▼

The best way to separate SolidJS client and server code is by isolating backend logic into a dedicated server/ folder while keeping UI components in components/, ensuring clear module boundaries.

Can I use these architecture guidelines to reorganize an existing SolidJS app?▼

Yes, you can apply these SolidJS architecture guidelines when refactoring an existing app by reorganizing folders into components/, lib/, and stores/ to align with consistent baseline architecture.

When do I need to review module boundaries in a SolidStart PR?▼

Review SolidStart module boundaries in a pull request when changes touch routing, components, or lib boundaries, ensuring proper file-based routing and separation of client/server code.