markdowntown-workbench

Resolve Workbench UI/state mismatches with the export/compile pipeline.

Updated Dec 31, 2025
One-click install
npx skills add https://github.com/joelklabo/markdowntown-cli --skill markdowntown-workbench
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: markdowntown-workbench
Source: https://github.com/joelklabo/markdowntown-cli/tree/main/codex/skills/markdowntown-workbench
Command: npx skills add https://github.com/joelklabo/markdowntown-cli --skill markdowntown-workbench

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Coordinating Workbench UI, normalized state (UAM v1), and the export/compile pipeline is complex and error-prone, causing mismatched adapter outputs, missing targets, and confusing compile warnings that block exports and integrations.

Core Features & Use Cases

  • Workbench UI & state guidance: Where to find key components and the single source of truth in useWorkbenchStore for selection, scopes, blocks, and scan handoff.
  • Export and compile pipeline: How the Export panel, /api/compile endpoint, compile aggregation, and adapter registry interact and where to change behavior.
  • Adapter management: Registering adapters, resolving target/version metadata, and updating adapter output or options with docs alignment.
  • Tests & validation: Recommended checks to run and where to update unit and integration tests when export behavior changes.
  • Use Case: When an adapter produces file collisions or incorrect formatting, reproduce the compile result in the Export panel, update the adapter or compile logic, and validate warnings surface correctly.

Quick Start

Reproduce the failing compile via the Workbench Export panel, inspect the compile output and adapter mapping, then update the compile or adapter code and rerun tests to verify warnings are resolved.

Frequently Asked Questions about markdowntown-workbench

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
Why does my Next.js Workbench export pipeline produce mismatched adapter outputs?

To debug Workbench compile warnings, reproduce the compile result via the Export panel, inspect the compile output and adapter mapping, then update the adapter or compile logic and rerun tests to verify the warnings are resolved.

How do I fix file collisions and incorrect formatting in Workbench export adapters?

To fix export adapter file collisions, reproduce the failing compile in the Workbench Export panel, inspect the adapter mapping, update the adapter or compile aggregation code, and rerun tests to validate the corrected output.

How does the compile aggregation logic interact with the adapter registry?

Compile aggregation logic interacts with the adapter registry by resolving target and version metadata to route normalized state to specific export adapters. Updating this resolution logic or the adapter output options changes the final compiled export behavior.

Where is the single source of truth for Workbench UI state and scan handoff?

The single source of truth for Workbench UI state is the useWorkbenchStore hook. It manages selection, scopes, blocks, and scan handoff, ensuring the UI components reflect the correct state before the export pipeline processes the compile request.

What tests should I run when changing export behavior in a Next.js Workbench?

When changing export behavior, run unit and integration tests that validate compile outcomes and surface warnings. Update these tests within the adapter registry and compile aggregation logic to ensure the export pipeline produces correct target mappings.