Translate alpha ADR implementation contracts into code and passing Vitest suites.
npx skills add https://github.com/Pionpill/retikz --skill develop-implement
Please help me install this Agent Skill. Skill: develop-implement Source: https://github.com/Pionpill/retikz/tree/main/.agents/skills/develop-implement Command: npx skills add https://github.com/Pionpill/retikz --skill develop-implement
It provides a disciplined way to turn an alpha ADR “implementation contract” into working code and passing tests, ensuring the IR remains AI-friendly and contract-compatible.
.describe(...) on every schema field, and TikZ vocabulary-aligned naming to protect LLM tool use.Use develop-implement to implement a Proposed ADR “契约段” by first generating the schema stub and Vitest tests in a Spec-First workflow, then implement code step-by-step until all tests pass.
High-intent search queries and answers about installing and using this skill.
To implement ADR contracts using spec-first TDD, generate a Zod schema stub and Vitest test cases first, then write implementation code step-by-step until all tests pass. This enforces JSON-serializable IR and TikZ-aligned naming.
Spec-first TDD for JSON-serializable IR is a development workflow where you define Zod schemas with English `.describe(...)` fields and write Vitest tests before implementation. It ensures round-trip equivalence and protects LLM tool use.
You enforce contract constraints with Vitest and Zod schemas by running eslint, tsc, and full vitest gates for every step. This deterministic loop forbids changing schema field names or types and prevents breaking the implementation contract.
No, you cannot change test expectations during the ADR implementation loop. The guarded implementation process forbids altering test expectations or modifying schema field names and types to prevent breaking the contract.
You need spec-first TDD for ADR contracts when implementing “契约段” changes, especially during red (mandatory) stages. It is required to enforce JSON-serializable IR, TikZ-aligned naming, and round-trip equivalence with step-scoped commits.
Yes, this spec-first TDD workflow explicitly works with the retikz TikZ/IR pipeline. It translates an alpha Proposed ADR implementation contract into working code while enforcing JSON-serializable IR and TikZ vocabulary-aligned naming.
PionpillGenerate adversarial IR inputs to test retikz JSON and zod contracts.
yo-stevenVerifies numerical parity for Hugging Face to Megatron weight conversions via state-dict round-trips and forward-pass tests.
carrot-foundationValidate and standardize JSON Schemas generated from Zod definitions.
robit-manConfigure TDD enforcement with pre-commit hooks and CI coverage gates.