Summary
The component-md renderer instruction (references/component-md/agent-component-md-instruction.md) emits API configuration examples as Property | Value | Notes markdown tables. But create-api's SKILL.md parses examples only in the "description + fenced code block" shape. Result: when a canvas run consumes a generated .md, the examples section silently yields no parsed examples — the Config Examples panel and its live previews are dropped without an error.
Where
- Emitter:
references/component-md/agent-component-md-instruction.md (Config examples section shape)
- Consumer:
create-api SKILL.md example-parsing step
Reproduction
- Generate a spec with
create-component-md — the .md's "Configuration examples" arrive as Property | Value | Notes tables.
- Run
create-api against that .md.
- The example parser finds no fenced code blocks → examples/live previews are silently omitted from the rendered API Overview frame.
Impact
Fired on every component in our batches (30+ components across atoms/molecules/organisms). Workaround: manually map table rows onto the template's example slots at render time.
Suggested fix
Either emit examples as description + fenced code from the renderer instruction, or teach create-api's parser to accept the table shape. Aligning the two contracts in either direction resolves it.
Summary
The component-md renderer instruction (
references/component-md/agent-component-md-instruction.md) emits API configuration examples asProperty | Value | Notesmarkdown tables. Butcreate-api's SKILL.md parses examples only in the "description + fencedcodeblock" shape. Result: when a canvas run consumes a generated.md, the examples section silently yields no parsed examples — the Config Examples panel and its live previews are dropped without an error.Where
references/component-md/agent-component-md-instruction.md(Config examples section shape)create-apiSKILL.md example-parsing stepReproduction
create-component-md— the.md's "Configuration examples" arrive asProperty | Value | Notestables.create-apiagainst that.md.Impact
Fired on every component in our batches (30+ components across atoms/molecules/organisms). Workaround: manually map table rows onto the template's example slots at render time.
Suggested fix
Either emit examples as description + fenced code from the renderer instruction, or teach create-api's parser to accept the table shape. Aligning the two contracts in either direction resolves it.