What problem does it solve?
Makepad 2.0 developers often know the DSL syntax but struggle with architectural decisions: how to structure state, split components, and reason about GPU rendering. This Skill acts as the entry point for any Makepad task, routing syntax questions to the correct specialized skill while applying conceptual design anchors for judgment calls.
Core Features & Use Cases
- Skill Routing: Maps any Makepad question domain (layout, events, shaders, themes, etc.) to the correct one of 13 compliance-layer skills to co-load.
- Design Judgment Anchors: Applies six conceptual anchors — Elm Architecture for data flow, Presentational/Container split for components, immediate-mode GPU rendering mental model, Flexbox-style layout, SDF shader thinking, and Flutter-style cross-platform rendering.
- Anti-Sycophancy Protocol: Anchors answers to Makepad's actual API behavior instead of agreeing with incorrect user approaches.
- Use Case: When asked "how should I structure a Makepad app with shared state across screens", the Skill routes to app-structure and events skills for syntax, then applies the Elm Architecture anchor to recommend centralized state with
Cx::post_action as the async-to-UI bridge.
Quick Start
Ask how to architect or structure a Makepad 2.0 application, such as how to organize state and components for a multi-screen app.
