What problem does it solve? Testing the ade CLI normally requires live API calls to parse documents, which makes end-to-end verification slow, costly, and network-dependent. This Skill shows how to verify CLI changes offline by seeding a local store with the exact artifacts parse would produce, then running the real CLI and inspecting generated outputs like view.html in a browser. ## Core Features & Use Cases - Offline Store Seeding: Write parse.json, parse.md, elements.json, and meta.json directly into a store directory, matching what parse.py::write_artifacts produces, so no API call is needed. - Deterministic Fixtures: Build markdown piecewise so every element's range is exact, reuse tests/parse_fixtures.py shapes, and draw a matching invoice PNG so bounding boxes visibly align. - Browser-Driven Verification: Serve the doc directory over HTTP (since the in-app browser refuses file://), deep-link to elements with #element=<id>, and inspect selection state via JavaScript. - Use Case: After modifying the view command, seed a store with ADE_HOME=<dir>, run uv run ade view, serve the output on http://127.0.0.1:8742/view.html, and confirm element highlighting and rebuild fingerprinting behave correctly. ## Quick Start Seed an offline ade store with parse artifacts, point the CLI at it using ADE_HOME, then serve and inspect the generated view.html in a browser to verify the changes.
