noddde: Skill for Claude Code

Step 2: Generate Tests (RED Phase)

Create or update a vitest test file from a spec's ## Test Scenarios section.

Pipeline step 2 of 6. Called by the /spec orchestrator after step 1 (spec creation/editing).

Key principle: Tests MUST be generated BEFORE the implementation. This proves the tests are meaningful — they fail when the behavior is missing and pass when it's present. If tests are generated alongside the implementation, you can't know if they'd catch regressions.

Step 1: Find the Spec

If a spec path is provided, read it directly. Otherwise, find it:

• From a source file: replace packages/core/src/ with specs/core/ and .ts with .spec.md
• From a module name: look in specs/core/<module-path>.spec.md
• From a test file: reverse the mapping below

Step 2: Read the Spec

Read the full spec. Focus on:

• title from frontmatter (used for describe() block name)
• status from frontmatter (must be ready or later — refuse to generate tests from draft specs)
• ## Test Scenarios section (the source of truth for tests)
• ## Type Contract (for understanding imports needed)
• exports from frontmatter (for import statements)

Step 3: Determine Test File Path

Spec path	Test file path
specs/core/<path>/<name>.spec.md	packages/core/src/__tests__/<path>/<name>.test.ts
specs/integration/<name>.spec.md	packages/core/src/__tests__/integration/<name>.test.ts

Create parent directories if they don't exist.

Step 4: Generate the Test File

Structure

import { describe, it, expect, expectTypeOf } from "vitest";
import {} from /* exports from spec */ "@noddde/core";

describe("<spec title>", () => {
  // One it() block per ### heading in Test Scenarios
  it("<heading text>", async () => {
    // Code from the TypeScript code fence under that heading
  });
});