ide-rules-export
X-6 per §23 — one-way IDE rules export. Use when the operator wants to consume the active profile's resolved standards in Cursor / VS Code Copilot / Continue / Aider / Windsurf. Emits a read-only artifact per target IDE; rules never flow back into TDD Pro (the architectural moat — provenance per §2.1, control mapping per §2.9, grounded-standards citation — cannot be reconstructed from systems that do not produce it).
- License 许可
- Apache-2.0
- 最近更新
- 2026-11-09
- Stars
- ★ 0
- Forks
- 0
01 前言 Front Matter
- name
- ide-rules-export
- paths
- [ "**/*" ]
- description
- X-6 per §23 — one-way IDE rules export. Use when the operator wants to consume the active profile's resolved standards in Cursor / VS Code Copilot / Continue / Aider / Windsurf. Emits a read-only artifact per target IDE; rules never flow back into TDD Pro (the architectural moat — provenance per §2.1, control mapping per §2.9, grounded-standards citation — cannot be reconstructed from systems that do not produce it).
- budget_impact_estimate
- 0 tokens (mechanical config emit; no LLM in the path).
03 SKILL.md 正文
X-6 IDE rules export (§23 amendment)
Reads every rule from the active profile + resolved standards source folders (G-1 directory) and emits a target-IDE-shaped artifact.
Targets
- cursor —
.cursorrules+ per-rule prompts at.cursor/rules/<rule-id>.md - vscode-copilot —
.github/copilot-instructions.md+.github/prompts/<rule-id>.md - continue —
config.jsonrules section - aider —
.aider.conf.yml+CONVENTIONS.md - windsurf —
.windsurfrules
Invocation
/export-rules <ide> [--profile <name>] [--include <ns>] [--exclude <ns>] [--out <dir>] [--skip-fresh] [--dry-run]
<ide>— positional; one ofcursor/vscode-copilot/continue/aider/windsurf--profile <name>— override active profile (default: from.claude-tdd-pro/userConfig.yaml)--include <ns>— include only this source-namespace (repeatable)--exclude <ns>— exclude this source-namespace (repeatable)--out <dir>— output root (default: repo root)--skip-fresh— bypass the §2.17 freshness gate; logged to C-4--dry-run— emit plan; no file writes (per §2.14)
Provenance
Output artifacts carry a header stamp:
profile_snapshot_hash + exported_at + tdd_pro_version. /doctor
warns when the stamp is stale.
Cross-references
- §23 v1.9.1 amendment (this skill)
- §2.1 rubric rule schema (per-rule provenance)
- §2.9 controls mapping
- §2.17 freshness gate
- C-4 audit log
- G-1 standards source directory
04 同仓库更多 Skills
test-first-extract
Use when the user asks to EXTRACT or RELOCATE existing code into its own file, module, or component ("extract X", "split out Y", "pull Z into its own file", "decompose god-file"). NOT for net-new features (use tdd-feature-build) or behavior changes (use fix-bug). Enforces the 9-step extraction with isolated unit tests + integration regression tests as a two-tier safety net.
tdd-feature-build
Use when the user describes a NEW feature to add ("add X to Y", "implement Z", "build a feature that…", "make it possible to…"). Enforces TDD — failing test first, minimum code to pass, refactor. Refuses to ship code without a test that demonstrably catches its absence. Does NOT trigger on bug fixes (use bug-fix-discipline) or refactors (use test-first-extract). Will ask 1-3 clarifying questions before writing any code; safe to delegate from /feature command.
sync
Multi-machine git-backed sync of local TDD Pro state via the `tdd-pro-sync` branch. Use when operators run claude-tdd-pro on more than one machine and want their FAILURE-LOG, decisions, audit checkpoints, workflow state, operator-curated URL registries, operator/community trees, and paywalled attestations to follow them between hosts.
strict-component-tests
Use when writing or reviewing test files. Enforces strict assertions that actually catch regressions (getByRole, exact counts, jest-dom matchers) in contrast to permissive tests (queryAllByText length > 0) that pass against broken UIs. References QUALITY-BAR.md for the canonical strictness rules.
spec
暂无简介
spec-first
Use when the user describes a non-trivial feature or system that should be specified in writing before any code is written. Pattern from Geoffrey Huntley's "Ralph" loop, OpenSpec, intent-driven.dev, and Kent Beck's "augmented coding" framing — specs+tests are the durable artifact, code is the disposable one. Produces a Markdown spec document that the user reviews; only after approval does any code get written (typically via tdd-feature-build or /feature).