code-artisan

Default starter for any frontend-only app — landing pages, dashboards, todo lists, content sites, calculators, anything that runs entirely in the browser. Reach for this first; use it for the vast majority of user requests. Stack: Vite + React + TypeScript + Tailwind v3 + shadcn/ui + TanStack Router + TanStack Query + Zustand. The platform's iframe runtime plugin is pre-wired in vite.config.ts and the dev server boots automatically from .code-artisan/manifest.json. Trigger on: 落地页, 网页, 应用, 网站, 仪表盘, todo, 笔记, dashboard, landing page, web app, frontend, UI, page, todos, blog, content site, build me a, create a, make a.

Use this skill ONLY when the app needs a real server layer — calling third-party APIs with hidden keys (LLM, Stripe, OpenAI, payment processors), proxying webhooks, server-side rate limiting, or complex orchestration that can't run safely from the browser. For frontend-only apps (with or without persistence), use `frontend-starter` instead — it's simpler. Stack: Vite + React + TypeScript + Tailwind v3 + shadcn/ui + TanStack Router + TanStack Query + Zustand (frontend); Hono + Bun (backend, unified dev server via @hono/vite-dev-server). Pair with the `supabase` skill for any persistent data — the server stays for server-only work, data goes through frontend-direct Supabase + RLS.

Use this skill when the app needs persistent data, user accounts, file storage, or realtime updates. The platform integrates with the user's own Supabase organization via OAuth — this skill provisions a project under that org, runs schema + Row Level Security via the Management API, and wires the generated app to it through platform-injected env. Trigger on: "save data", "login / sign in / sign up", "user accounts", "database", "todos with auth", "file uploads", "realtime / live updates", or any spec where state must survive reload.