メニュー
Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first.
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 | using-development-skills |
| description | Use when starting any conversation - establishes how the development-skills plugin works and how to invoke its components on each platform (Claude Code, Codex). Read first. |
If dispatched as a subagent for a specific task: skip this skill.
If any skill might apply (even 1% chance), invoke it. Skills are the disciplined entry points — the meta-rule (spirit beats letter) covers the rest.
14 principles (0-13) + 1 meta-rule (spirit beats letter). Canonical: shared/iron-rules.md. Do not duplicate.
Classify the task before reading its content in depth:
shared/workflow.md # Tier selection) → follow the 6-step inline flow. Default on uncertainty → FULL.docs/plans/NNNN__YYYY-MM-DD__implementation_plan__slug.md + HOW-level Q&A locks (data shapes · edge cases · error semantics · contract boundaries · test scope · rollback).docs/chronicles/NNNN__YYYY-MM-DD__topic.md capturing initial decisions.staff-reviewer subagent review.Rules during FULL:
AskUserQuestion for discrete options; plain text otherwise; Codex fallback in references/codex-tools.md).Rules during LIGHT: Tier is qualitative (ambiguity / logic impact / new-pattern) — not file count. A 30-file mechanical rename is LIGHT; a 1-file new-caching-strategy is FULL. All Iron Rules still apply. Mid-execution discovery breaks LIGHT criteria → escalate to FULL per shared/workflow.md # LIGHT (final paragraph).
Routing: Bug fixes → development-skills:debugging. Test work → development-skills:create-test.
SKILL bodies use Claude Code tool names as canonical. On Codex, translate via references/codex-tools.md (Task → spawn_agent, AskUserQuestion fallback, staff-reviewer dispatch recipe, hooks, marketplace files).
User instructions (CLAUDE.md, AGENTS.md, direct requests) > development-skills > default system prompt.