菜单
Use when any coding, development, analysis, debugging, or code-related task is detected. Triggers on: implementing features, fixing bugs, refactoring code, reviewing diffs, investigating errors, evaluating approaches, or making architecture decisions.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Temporary inboxes for agent signup QA — create disposable addresses, wait for verification email, extract OTP or magic links. Use when automating signup, login, or email verification without parsing HTML manually.
Spin up isolated sandboxes ("boxes") for coding agents, run them in parallel, queue background runs with -i, and push commits safely through the host relay. Use when the user wants to run Claude Code / Codex / OpenCode in a sandbox, start more boxes, attach to a running box, or otherwise operate the `agentbox` CLI on their laptop.
Use when building an HTTP val — a web endpoint, API route, webhook receiver, or any val that responds to HTTP requests. Covers the handler signature, Hono usage, the endpoint URL, CORS behavior, redirects, and Val Town-specific limitations.
Use when creating a new val and choosing which starter to fork. Covers the catalog of official starter templates, which project shape each one fits, and when forking an existing val is the better starting point.
Switch coding-agent accounts on a usage/rate limit, routed by host and agent.
Use Agent Mail from Codex for file leases, notifications, inboxes, and conflict prevention.
| name | core-dev |
| description | Use when any coding, development, analysis, debugging, or code-related task is detected. Triggers on: implementing features, fixing bugs, refactoring code, reviewing diffs, investigating errors, evaluating approaches, or making architecture decisions. |
| user-invocable | false |
| allowed-tools | Glob, Grep, Read, Bash, Skill, AskUserQuestion |
Triage (PASS_THROUGH/LIGHT/FULL) is upstream in using-development-skills. If you're here, you're FULL. Iron Rules: ../../shared/iron-rules.md.
Grep("Status: In Progress", path="docs/plans/", glob="*.md"). Match → read the plan file, resume at the phase listed (skip language detection — plan already specifies). Still invoke the language skill for implementation rules. No match → step 2.
Default: invoke development-skills:brainstorming with the user's full request as args.
Skip ONLY if all three hold:
Specialized routes:
development-skills:debuggingdevelopment-skills:create-testUser bypass: "skip brainstorming", "just code it", "I already know the approach" → respect it. "Fast" is NOT a bypass.
| Your thought | Reality |
|---|---|
| "User said exactly what to do" | WHAT ≠ HOW. Multiple approaches → brainstorm. |
| "I already have a good approach" | First approach ≠ best. Brainstorming costs nothing. |
| "Just analysis / investigation" | Analysis IS development. Brainstorm. |
| "User confirmed, so my analysis was correct" | Confirmation validates the decision, not the analysis. |
After brainstorming returns (or after a skip-decision), detect language:
| Signal | Skill |
|---|---|
next.config.*, app/{layout,page}.tsx, @raycast/api, vite.config.* + react, *.tsx + react dep | frontend-dev |
*.py, requirements*.txt, pyproject.toml | python-dev |
*.ts, tsconfig.json (no frontend signals) | typescript-dev |
*.java, pom.xml, build.gradle, *.kt | java-dev |
*.swift, Package.swift | swift-dev |
Frontend signals trump pure TypeScript. Invoke the matching skill before writing any code.