dev-process-kit

# dev-process-kit Show what you understood as one HTML file. The user operates and comments on it in the browser and hands the review back as a brief; you rewrite the file. Repeat until you agree. ## Principles Humans have little context and do not read long text well. - **Visualize.** Put the structure in a map or diagram; prose only for what a picture cannot say. - **Narrow.** Include only what the user needs to agree or disagree. Omit the obvious and the off-topic. - **Dig through dialogue.** Surface decisions and uncertain points instead of pre-answering them, and go deeper where the user's comments point. ## Steps 1. Get the latest version: the `version` of <https://registry.npmjs.org/dev-process-kit/latest>. Use that exact version everywhere below. 2. Read the docs of that version at its Git tag: `https://raw.githubusercontent.com/d-kimuson/dev-process-kit/v<version>/docs/index.md`. 3. Pick one template (and any components) and read only their pages: `…/v<version>/docs/templates/<name>.md` and `…/v<version>/docs/components/<name>.md`. 4. Write the HTML in the user's language and give the user the file. Load the bundle from jsDelivr with the version pinned — `https://cdn.jsdelivr.net/npm/dev-process-kit@<version>/dist/templates/<name>.js` — never `@latest`: the page has to keep working after a new release. jsDelivr is also what a Claude Artifact is allowed to load scripts from. 5. On a brief, apply it to the base data and answer the comments in the next version. | Agree on | Template | | ----------------------------------------- | -------------------------------- | | Scope and release slicing | `usm` | | Domain events, commands and causality | `event-storming` | | Rules of a story, with concrete examples | `example-mapping` | | Screen flow and what each step looks like | `prototype` | | Decisions you need from the user | `grill` | | Anything else | `plain`, with diagram components |