菜单
Use whenever you write new or refactored code during a renovation (frontend or backend) — author tests first (red-green-refactor) and build the automated test coverage the modernized system needs. Cross-cutting; invoke on every code-producing step. Composes with the tdd skill.
用 Codex 或 Claude 帮你安装 复制这段 Prompt，粘贴到 Codex、Claude 或其他助手里，让它检查 Skill 页面并帮你完成安装。
基于 SOC 职业分类
Implement one Azure-backed strangler slice in the target repository after architecture, requirements, Azure review, rollback plan, and touched-seam harnesses are green. Produces tested, observable, reversible code and deployment evidence.
Use before any destructive refactor or UX/backend change to capture the legacy system's current behavior as characterization tests and golden-master fixtures — the safety net that catches regressions. This is the harness gate; it must be green before modernization code begins.
Implement a vetted legacy-web UX slice in the target repository after requirements and touched-seam harnesses are green. Discovers the real frontend stack, changes code test-first, and records implementation evidence before browser validation and review.
Use when starting or resuming a legacy web modernization (UI/UX and/or backend) — routes between renovation phases, tracks state in plan.md, and enforces the harness/test/review gates. Entry point for the harness-driven-renovate workflow.
Use to modernize a legacy backend incrementally using the strangler-fig pattern — route slices of traffic to new event-driven / cloud-native services behind stable seams while the characterization harness guards against regressions. Requires the harness gate to be green.
Use as a mandatory gate before any renovation change is considered done or merged — rigorous review focused on harness regressions, legacy parity, security, and readability. Cross-cutting; invoke on every change. Composes with requesting-code-review / code-review agent.
| name | test-authoring |
| description | Use whenever you write new or refactored code during a renovation (frontend or backend) — author tests first (red-green-refactor) and build the automated test coverage the modernized system needs. Cross-cutting; invoke on every code-producing step. Composes with the tdd skill. |
Cross-cutting skill for every code-producing step of the renovation. New and
refactored code ships with tests written test-first. This is forward-facing
(tests for the new system), complementing behavior-harness (which pins the
old system).
frontend-code-implementation, backend-slice-implementation,
ux-modernization, strangler-backend, or ai-augmentation produces or changes
code.If a tdd / test-driven-development skill is available in the environment,
invoke it for the red-green-refactor loop — do not reimplement it here. This
skill adds renovation-specific guidance on what to test.
Follow red → green → refactor:
requirements-grilling) before the implementation exists.ai-augmentation
evals.Once green, hand the change to strict-code-review. The change is not done until
both this gate and the review gate pass.
scripts/create-test-evidence.sh <repo-root> <target-name>