← ClaudeAtlas

designing-canvaseslisted

Design UI on a local infinite canvas with foss-design - mockups, screens, user flows, clickable and animated prototypes, landing pages, dashboards, onboarding, empty states, design explorations and variations, "show me how X could look". Screens are real React (.tsx) or HTML pages in a gitignored .design folder, laid out in canvas.json and previewed in a local viewer with pages, pan/zoom and live frames. Use for any request that would otherwise become a Claude Artifact or a Claude Design canvas; Artifacts are not used here. Hands over through foss-design Cloud when .design is linked to it, offers the free cloud to projects that are not, and pushes, pulls and shares canvases there. Pair with building-design-systems when the project has no design system yet.
wiolett-industries/foss-design · ★ 1 · Web & Frontend · score 69
Install: claude install-skill wiolett-industries/foss-design
# Designing Canvases foss-design keeps designs in the project, next to the code, in a gitignored `.design/` folder. A **canvas** is `.design/canvas/<id>/`: a `canvas.json` that lays out **pages** of **sections**, and the **screens** it points at. Every screen is a real page (a React component or an HTML file) rendered live in its own frame, so animations, hover states, forms and navigation all work. The local viewer shows the canvas with pan and zoom, page switching, notes, a play mode, and an inspector (`I`): the user clicks any element to see its box model, typography, colors and radii traced to design tokens, and its Tailwind classes — so use token utilities rather than raw values, and they will show up as tokens there. Files on disk are the design, and the local viewer is a dev server with hot reload. [foss-design Cloud](https://fossdesign.dev) is the free place to keep, organize and share them: once `.design` is linked to a cloud project, work is handed over there (see Hand over). Nothing is uploaded from a project that is not linked, and signing in or linking always waits for the user's yes. ## Run the CLI Resolve the command once per session and reuse it: ```bash command -v design >/dev/null && D=design || D="npx -y foss-design" $D --help ``` `design` exists when the user installed `npm i -g foss-design`; otherwise `npx -y foss-design` runs the same CLI. Every command finds the project by walking up to the nearest `.design` folder; pass `--root <dir>` to be expli