excalidraw-system-sketchlisted

Create one readable spatial sketch plus durable Markdown summary. ## Scope Use when placement, grouping, swimlanes, or exploration matters. Use Mermaid for exact sequence, state, dependency, or GitHub-rendered architecture. ## Inputs - Diagram purpose and audience. - Components, actors, systems, and flows. - Trust boundaries, secrets, user data, and external services. - Existing `.excalidraw` file or visual conventions, if any. User or repository owns system facts. Mark inferred nodes and unresolved flows. ## Workflow 1. State one diagram question. 2. List boxes, groups, arrows, boundaries, and annotations. 3. Choose layout: left-to-right flow, swimlanes, nested zones, or before/after. 4. Separate internal, external, trusted, and untrusted areas. 5. Label secret and user-data entry points without including secret values. 6. Create or update `.excalidraw` when compatible tooling exists. 7. Write companion `.md` summary with purpose, components, boundaries, flows, and open questions. ## Drawing Rules - One concept per sketch. - Short labels. Verb-led arrows. - Color encodes one stable meaning or stays decorative-free. - Boundaries visible without color alone. - When text is enclosed by a shape, bind it when possible: shape `boundElements` includes `{ "type": "text", "id": "<text_id>" }`, and text element points back with `containerId`. - Avoid file-level detail unless diagram question requires it. - Keep uncertain elements labeled `Assumption` or `Open`. ## Fallbacks