How julianoczkowski/solidjs works
Project Type and Purpose
• This is primarily a front-end application template and documentation system built with SolidJS/SolidStart (TypeScript) that integrates Trimble Modus Web Components for UI, supplemented by AI-driven developer tooling (Cursor Memories & Rules) and Figma MCP for design-to-code context. It’s often deployed as a static+SSR site with an associated local AI/IDE integration and design-system bridge.
File Structure Analysis
• Top-level directories:
• Cursor Memories (AI memory definitions)
• Cursor Project Rules (AI rule sets enforcing standards)
• Cursor User Rule (developer’s personal workflow)
• MCP (Model Context Protocol config for Figma & Context7)
• WebComponentsDocs (40+ MD guides for each Modus component)
• README.md orchestrates usage of SolidStart + Modus components + Cursor + MCP. There are no classic “backend” or “database” directories—SSR is handled by SolidStart internally.
Key Architecture Insights from README
• SSR + hydration via SolidStart
• Custom Elements registration (defineCustomElements)
• Styling via Modus CSS custom properties (+ optional Tailwind)
• Cursor IDE communicates with local MCP servers (Context7, Figma)
• Documentation is a static markdown site alongside the code
Main Components
a. Developer Environment
• IDE/Text Editor (with Cursor plugin)
• Cursor Memories & Rules loaded from project folders
b. Build & Runtime
• Vite (or SolidStart build tool)
• Node‐based SSR Server (SolidStart)
• Client Browser (CSR + hydration)
c. UI Library & Styling
• TypeScript declarations (global.d.ts)
d. Documentation Subsystem
• Static markdown files (WebComponentsDocs)
• MDX/Markdown rendering pipeline (e.g., VitePress or custom)
e. External Services
• Figma MCP Server (via MCP/mcp.json)
• Context7 MCP server (Cursor’s AI backend)
Relationships & Data Flows
• Developer → IDE with Cursor → loads Memories & Rules → provides inline AI assistance
• Source code → Build tool (Vite/SolidStart) → outputs SSR server + static assets
• SSR Server ↔ Browser: initial HTML + JS for hydration (Mount Guard pattern)
• Browser → Modus Web Components (registered custom elements)
• SSR Server ↔ MCP servers:
• Context7 (AI context)
• Figma (design tokens & component specs)
Architectural Patterns & Principles
• SSR + CSR hydration (Show fallback until mounted)
• Custom Web Components as UI primitives
• Model Context Protocol for AI/design integration
• AI-first developer workflow (Cursor Memories & Rules)
• CSS custom properties for theming