Releases: devallibus/shaderbase
Releases · devallibus/shaderbase
v0.2.0 — Agent-First Registry
What's New
ShaderBase is now a full agent-first shader registry — the "shadcn for shaders."
Highlights
CLI (@shaderbase/cli on npm)
npx @shaderbase/cli search --query "gradient" --env r3fnpx @shaderbase/cli add gradient-radial --env r3f— copies shader files into your project
MCP Server (Cloudflare Worker)
search_shadersandget_shadertools via Streamable HTTP- Add to Claude:
"url": "https://mcp.shaderbase.com/mcp"
Static Registry
- CI builds JSON index + per-shader bundles from the git corpus
- Deployed to CDN — CLI and MCP server consume it
Web App
- AI-only submit flow that creates GitHub PRs
- Manual form removed, reviews migrated to Cloudflare D1
- Custom domain, favicon, proper meta tags
CI/CD
- GitHub Actions: test, typecheck, validate, build registry, deploy to Cloudflare Pages, publish CLI to npm
- Railway auto-deploy for web app
Distribution Model
shadcn-style: the CLI copies shader source files into your project. No npm dependency per shader. You own the code.
v0.1.1 — Detail Pages & AI Submission
What's New
Shader detail pages, AI-powered submission, and a review system.
Highlights
- Shader detail pages — full view with live Three.js preview, metadata, and GLSL source
- AI-first submission — paste GLSL, AI parses metadata and generates
shader.json - Review system — ratings and reviews stored in SQLite
- Performance — lazy-loaded Three.js, offscreen pause, proper WebGL disposal
v0.1.0 — Initial Foundation
What's New
The initial ShaderBase release: a git-backed shader corpus with Zod-validated manifests.
Highlights
- Shader manifest schema —
shader.jsonwith Zod validation, provenance rules, and compatibility model - Seed corpus — initial licensed shaders with normalized metadata and integration recipes
- Web app — SolidJS + TanStack Start frontend for browsing and searching shaders
- Validation pipeline —
bun run validate:shaderschecks all manifests against schema