DeeplyClear

View saved version →

---
name: deeplyclear
description: Create interactive, editable, shareable mind maps and mindmaps in DeeplyClear. Use whenever the user mentions DeeplyClear or asks to create, generate, visualize, structure, organize, map, or transform a topic, conversation, research, plan, document, codebase, or messy notes into a mind map, mindmap, concept map, knowledge map, systems map, idea map, argument map, research map, visual map, architecture map, or codebase map. Also use for requests to visualize relationships or turn complex information into a navigable map, even without the words "mind map." Return a visual preview and editable link. Do not use when the user specifically asks for a static image, illustration, poster, or infographic.
---

# DeeplyClear

Create a useful saved map and return both its visual preview and editable DeeplyClear link.

## Workflow

1. Inspect the source material before creating the map.
   - For a topic, conversation, plan, document, research, or notes, identify the main concepts, supporting details, and relationships.
   - For a repository or codebase, read relevant guidance such as `AGENTS.md`; identify languages, frameworks, manifests, entry points, subsystems, dependencies, data flows, and external services.
2. Choose a structure that matches the source material.
   - Use a clear hierarchy with concise node labels and preserve important relationships.
   - For broad or ambiguous topics, create a useful balanced overview without asking unnecessary setup questions.
   - For a repository or codebase, use the repository as the root and branch into the important architectural concerns, such as entry points, core services, data and events, external services, and cross-cutting concerns.
   - Show representative data or control flows as cross-links between those branches.
   - Do not collapse distinct ideas or code paths into one chain. Use a linear map only when the source genuinely describes one sequence.
3. Call `deeplyclear_create_map` with a prompt that includes:
   - a concise map title and purpose;
   - the important systems or concepts;
   - their hierarchy and relationships;
   - key data or control flows;
   - external dependencies and cross-cutting concerns when relevant.
   - Keep visibility private unless the user explicitly requests a public map.
4. Inspect the returned structure and preview.
   - Confirm the map covers the requested scope and has meaningful branches and relationships.
   - For a codebase map, confirm the requested architectural dimensions are represented and the result is not unjustifiably linear.
   - If needed, refine the saved map with `deeplyclear_edit_map`.
   - If creation did not return a visual preview, call `deeplyclear_preview_map`.
5. Return the visual preview, editable map link, and a brief statement of the represented scope.

Do not substitute Mermaid or a prose-only outline when `deeplyclear_create_map` is available. If DeeplyClear is not connected or authenticated, explain the required connection and retry after access is available.