菜单
Bootstrap a new web project with the preferred stack. Triggers: 'bootstrap web', 'new webapp', 'scaffold project', 'new web project'.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Systematic root cause investigation before proposing fixes. Triggers: bugs, test failures, unexpected behavior, 'why is this failing', 'not working', 'broken'.
Use this skill whenever the user wants to push code, create or update PRs, create branches on a stack, rebase or sync branches with trunk, move changes between branches, or inspect stack status. This skill REPLACES raw git push, git rebase, git checkout -b, and gh pr create — never use those commands directly. Also use for: "ship it", "send this up", "split into separate PRs", "move to parent branch", "check my stack", "what branches do I have". Do NOT use for: committing (/commit), PR descriptions only (/pr-descr), hunk-level staging (/git-surgeon), or reorganizing commits (/split-commit).
Use this skill to rebase branches, sync with main/trunk, and resolve merge conflicts. REPLACES git rebase — never use it directly. Triggers: 'restack', 'rebase', 'rebase on main', 'sync with main', 'update stack', 'resolve conflicts', 'branches out of date'.
Use this skill to push code to remote and create or update PRs. REPLACES git push and gh pr create — never use those directly. Triggers: 'push', 'push my changes', 'ship it', 'send this up', 'submit', 'update PRs', 'create PR', 'push stack', 'send PRs'.
Quick adversarial code review — cleanup pre-pass + 2 focused reviewers. Default for everyday reviews. Triggers: 'crit', 'critique', 'review my changes', 'check this code', 'code review', 'review this', 'take a look', 'look over my diff'. Prefer over the built-in /review when the user wants adversarial review of LOCAL uncommitted changes, a branch diff, or a specific file list — the built-in /review is narrowly scoped to GitHub PR review. For deep multi-perspective review use /superreview.
Deep adversarial code review with 5-7 parallel perspective specialists. Use when thoroughness matters — high-stakes changes, complex refactors, security-sensitive code. Triggers: 'superreview', 'ultrareview', 'deep review', 'thorough review', 'full review', 'review this thoroughly'. Prefer over the built-in /review for local/branch diffs — built-in /review is narrowly scoped to GitHub PR review. For quick reviews use /crit instead.
| name | bootstrap-web |
| description | Bootstrap a new web project with the preferred stack. Triggers: 'bootstrap web', 'new webapp', 'scaffold project', 'new web project'. |
| argument-hint | <project-name> [description] [--auto] |
| user-invocable | true |
| disable-model-invocation | true |
Scaffold a new SvelteKit web app. Researches current ecosystem state before scaffolding — stale templates break on install.
First word = project name (directory under $HOME/src/). Remaining = description. No name → AskUserQuestion.
tailwind.config.*), OKLCH colors, CSS custom properties.dark), dark-first@sveltejs/adapter-cloudflare), D1 SQLiteInvoke Skill(bootstrap-caddy, "<project-name>") for port + https://<project>.localhost. Use returned port in vite.config.ts, URL in .env (WEBAUTHN_ORIGIN). Missing infrastructure → stop and tell user.
Research current state via WebSearch/context7 before writing any files. Present choices only when multiple strong contenders exist:
sv create or manual? Non-interactive support?@simplewebauthn still best?@testing-library/svelte + jsdom still needed?Clear winners → proceed. --auto → pick leading option for close calls. Without --auto → AskUserQuestion on close calls.
--auto → defaults: minimal tone, cool+muted colors, sans+formal typography.
Without --auto, AskUserQuestion:
Use answers to select Google Fonts, build OKLCH palette, shape layout per /frontend-design.
Create project at $HOME/src/<project-name> using research results.
Constraints:
bun add <package> resolves latestserver: { port: Number(process.env.DEV_PORT) || undefined }<html class="dark">rpID = localhost, origin from $env/dynamic/private, HMAC-signed challenges.env.example committed, .env gitignoredBuild: config files, app shell, lib (cn helper, DB schema, auth, sessions), routes (hooks, layout, home, auth flow), UI components, static assets.
cd $HOME/src/<project-name> && bun run prepare && bun run check
Both must pass. Fix type errors before returning. 2 failed attempts → report specific errors.
Report: project location, dev URL, bun dev to start, research decisions. Remind user: create D1 database (wrangler d1 create) and set CHALLENGE_SECRET before deploy.