一键导入
schedule
Reads backlog and produces multi-stage work orders including test and deploy stages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
菜单
Reads backlog and produces multi-stage work orders including test and deploy stages.
用 Codex 或 Claude 帮你安装 复制这段 Prompt,粘贴到 Codex、Claude 或其他助手里,让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, typography, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, font smoothing, tabular numbers, image outlines, box shadows.
Systematic planning for medium-to-large tasks. Gathers context, identifies domain skills, writes phased plans to brain/plans/. Does NOT implement. Use for new features, multi-file refactors, or architectural changes — not small fixes. Triggers: "plan this", "break this down".
Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
Adversarial code review using cross-model approach. Spawns reviewers on the opposing model (Claude uses Codex, Codex uses Claude) to challenge work from distinct critical lenses. Produces a synthesized verdict with findings and lead judgment. Triggers: "adversarial review".
Structural code search via ast-grep — use when code shape and element relationships matter, not just text. E.g., "find async functions without error handling", "refactor foo(a, b) to foo({ a, b })". Use Grep for simple name lookups.
Read/write brain files (Obsidian vault at brain/). Use for any task that persists knowledge — reflection, planning, or direct edits. Triggers after debugging sessions, mistakes, corrections, architectural decisions, or any insight worth preserving across sessions. Use on 'add to brain', 'remember this', 'write a note', or brain/ modifications.
| name | schedule |
| description | Reads backlog and produces multi-stage work orders including test and deploy stages. |
| schedule | When orders are empty or after backlog changes |
Read brain/todos.md for backlog items. Write .noodle/orders-next.json with orders.
Build multi-stage pipelines. A typical order:
execute — implement the changetest — run the test suite against the changedeploy — deploy if tests pass{
"orders": [
{
"id": "1",
"title": "the backlog item title",
"rationale": "why this order was scheduled",
"status": "active",
"stages": [
{"task_key": "execute", "skill": "execute", "provider": "claude", "model": "claude-sonnet-4-6", "runtime": "process", "status": "pending"},
{"task_key": "test", "skill": "test", "provider": "claude", "model": "claude-sonnet-4-6", "runtime": "process", "status": "pending"},
{"task_key": "deploy", "skill": "deploy", "provider": "claude", "model": "claude-sonnet-4-6", "runtime": "process", "status": "pending"}
]
}
]
}
When no unchecked items remain, write {"orders": []}.