lhz960904

Build, launch, and drive Atrium to verify a change end-to-end. Use when a code change needs runtime observation in the real app (renderer UI, chat rendering, main-process behavior).

Use when a task needs to operate a native macOS app directly — click, type, read the on-screen UI, or drive a desktop workflow in an app like Notes, Music, Finder, System Settings, or any Mac app with no web version. For anything in a web browser or on a website, use browser-control instead. macOS only.

Use whenever a task needs a real web browser — opening a URL, searching, reading or extracting from a page, filling a form, clicking through a flow, or doing something on a site the user is signed in to (their GitHub, Gmail, Feishu, internal tools). Covers both public pages and the user's own logged-in sessions. Also use when the user asks to browse, "look this up on the site", or automate a web task.

A warm, conversational flow to establish or refine who the user is (their profile) and who you are (your persona). Use on first contact when neither is set, or whenever the user wants to (re)shape either identity — e.g. "let's get acquainted", "update my profile", "change how you act", "认识一下", "重新认识下", "调整你的人设". One question at a time; it should feel like meeting someone who gets you, never a form.

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.