菜单
Execute a SETI project implementation task by reading its plan, architecture, and rules, then implementing the code. Use when the user asks to "run task X-Y", "implement task", "do task", "execute task", or references a task number like "0-1", "1-3", "2-5", etc.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Brand design system for Terraforming Mars (TFM). Use when building or styling any frontend page/component in this project. Defines the visual language — colors, typography, spacing, component patterns — for a dark sci-fi Mars colonization theme.
Create distinctive, production-grade frontend interfaces with high design quality. Generates creative, polished code that avoids generic AI aesthetics. Use when the user asks to build web components, pages, artifacts, posters, or applications, or when any design skill requires project context. Call with 'craft' for shape-then-build, 'teach' for design context setup, or 'extract' to pull reusable components and tokens into the design system.
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.
| name | task-runner |
| description | Execute a SETI project implementation task by reading its plan, architecture, and rules, then implementing the code. Use when the user asks to "run task X-Y", "implement task", "do task", "execute task", or references a task number like "0-1", "1-3", "2-5", etc. |
When given a task identifier (e.g. 0-1, 2-3, task 1-5), follow these steps in order.
Map the task ID {stage}-{seq} to its plan file:
docs/plan/stages/stage-{stage}-*/task-{seq:02d}-*.md
Use Glob to find the exact path (e.g. docs/plan/stages/stage-0-*/task-01-*.md for task 0-1).
Read the full task file — it contains title, description, implementation details, directory structure, and acceptance criteria.
Determine the task's domain from its stage number and content:
| Stages | Domain | Architecture doc |
|---|---|---|
| 0 (common/mixed) | both | docs/arch/arch-server.md + docs/arch/arch-client.md |
| 1, 2, 3, 4 | server | docs/arch/arch-server.md |
| 5, 6, 7 | client | docs/arch/arch-client.md |
| 8 (alien) | both | docs/arch/arch-server.md + docs/arch/arch-client.md |
| 9 (polish/e2e) | client | docs/arch/arch-client.md |
Read the corresponding architecture document(s) to understand module structure, patterns, and conventions.
Read docs/arch/prd-rule.md for game rule details relevant to the task. Focus on sections that relate to the task's domain (e.g. solar system rules for task 2-1, scoring rules for task 3-3).
In docs/plan/summary.md, find the row matching the task ID and replace ⬜ with 🔨 in the status column.
Example: change | 0-1 | ... | ⬜ | → | 0-1 | ... | 🔨 |
Execute the task according to:
I prefix, Types: T prefix, Enums: E prefix, constants: CONSTANT_CASE)Also read and follow the relevant agent skills:
.agents/skills/board-game-architecture/SKILL.md.agents/skills/brand-guidelines/SKILL.md and .agents/skills/frontend-design/SKILL.mdAfter implementation, run the acceptance checks listed in the task file (typecheck, build, tests, etc.).
After all acceptance criteria pass, update docs/plan/summary.md: replace 🔨 with ✅ for the task.
Example: change | 0-1 | ... | 🔨 | → | 0-1 | ... | ✅ |