deeplyclear6.23 KB
View saved version →
---
name: deeplyclear
description: Create, edit, and resume interactive, saved mind maps in DeeplyClear. Use for mindmap, concept map, research map, architecture map, or codebase map requests, and follow-up requests to refine an existing DeeplyClear map. Also use when the user wants complex information or relationships organized into a navigable map. Do not use for general questions about DeeplyClear, product analytics, troubleshooting without map work, or specifically requested static images, posters, or infographics.
---
# DeeplyClear
Help the user create a useful saved map and continue developing it across requests. Return its visual preview and editable link.
## Choose the right action
- **New map:** inspect the available source material and call `deeplyclear_create_map`. Use the conversation or supplied material without asking the user to paste it again. For a broad topic, make a useful balanced overview without unnecessary setup questions.
- **Follow-up edit:** “simplify it,” “add examples,” “add these notes,” and “expand this branch” normally refer to the current map. Reuse its ID from the current conversation or tool result. Use `deeplyclear_edit_map` for broad changes, `deeplyclear_elaborate_node` for one node, or fetch the map with `deeplyclear_get_map` and use the explicit node or edge tools for exact changes. Preserve unrelated content and visibility. Do not create a replacement unless requested.
- **Resume saved work:** use `deeplyclear_list_maps` to find the requested map, then `deeplyclear_get_map` to inspect it. Match the user's title or topic; ask a short clarification when several plausible maps remain. Do not assume the newest map is the intended one when the user names another.
- **Share:** distinguish a link the owner can open from access for other people. Use `deeplyclear_set_map_visibility` only when public or private access is explicitly requested. If the user says “share” without a clear audience or access choice, explain that a private map's link requires owner access and clarify before making it public. Public maps may appear in community discovery. Never promise unlisted or invitation-only sharing unless the tools support it.
For exact changes, use `deeplyclear_create_node`, `deeplyclear_update_node`, `deeplyclear_delete_node`, `deeplyclear_create_edge`, or `deeplyclear_delete_edge`. Each performs one action; use exact IDs from the latest map result. Deleting a node also removes its connected edges but keeps other nodes. Remove nodes or edges only when the user requests it.
Use tools available in the current client. If editing or retrieval tools are unavailable, say so and offer the existing editable link; do not create a duplicate as a workaround.
## Create and refine a useful map
1. Identify the main concepts, supporting details, and relationships from the source. For a repository, read relevant guidance such as `AGENTS.md` and inspect its entry points, systems, dependencies, and data flows.
2. Choose a clear hierarchy with concise labels. Preserve relationships across branches; do not collapse distinct ideas or code paths into one chain. Use a linear map only for a genuinely sequential source.
3. Supply the map's purpose, important concepts, hierarchy, and relationships in the creation prompt. For codebases, include representative data/control flows, external dependencies, and cross-cutting concerns. Keep maps private unless public access is explicitly requested.
4. Inspect the returned structure and preview for scope and meaningful branches. Make a focused correction if needed. Do not repeatedly regenerate a satisfactory map for minor stylistic preferences. If a successful result lacks a preview, use `deeplyclear_preview_map` when available.
Do not substitute Mermaid or a prose-only outline for a requested DeeplyClear map when its creation tool is available.
## Match the map to its purpose
Use the user's material and intent to shape the map; these are useful starting points, not a required questionnaire:
- **Project planning:** goals, milestones, tasks, risks, and open decisions. A useful follow-up is updating a milestone or developing a real risk branch.
- **Research synthesis:** themes, findings, sources, and open questions. Keep supplied source references, distinguish evidence from assumptions, and never invent citations. A useful follow-up is incorporating new notes into the existing map.
- **Studying:** concepts, relationships, examples, and practice questions appropriate to the user's level. A useful follow-up is adding examples or questions to a concept already in the map.
## Complete the handoff
- Show the preview and editable link. Prefer opening the interactive editor; offer the animated tour when relevant to presenting or exploring the map.
- Confirm that the map was saved only after a successful tool result. State the actual returned visibility; do not assume an existing map is private.
- After an edit, briefly say what changed and that it is the same saved map.
- When helpful, suggest one specific next refinement grounded in its content, using the actual branch label from the returned map. Prefer an undeveloped branch or a relevant next action for the map’s purpose. Make it an optional suggestion, not an automatic edit or a required question.
- Explain how to find this map again when the user asks. Use its title and saved link; do not promise that a future conversation remembers its ID.
## Recover without losing the task
If a tool requires authentication or reauthentication, use its returned connection link; otherwise offer [DeeplyClear in ChatGPT](https://chatgpt.com/plugins/plugin_asdk_app_6a571a2e0e7c819184208e1c2d6e8062). Briefly explain the connection step and retain the pending topic or edit and map ID in the current conversation. When the client makes the connection available, resume the pending task without requiring another confirmation or asking the user to repeat it. If this client cannot resume automatically, give one short, ready-to-send continuation prompt that retains the topic or saved map reference. If authentication fails again, explain the blocker instead of looping.
For an uncertain creation outcome, check available saved maps before retrying so a response failure does not create duplicates. Never claim a map was saved if the result does not establish that.
Referenced files: 1 — file references are metadata, not package contents.
