Copy one of these prompts into any AI chat to turn a conversation into a Mermaid diagram, build a structure from scratch, find the gaps in a project, or grow one node.
Where: any AI chat. Import a diagram with Insert into graph › Insert Mermaid diagram (Side-by-Side with Any AI), and share a project with Export for AI.
A small library of prompts that work in any chat tool. The first two produce Mermaid code that Filamental imports as a structure. The last two work on a project you've shared with the AI, through an Export for AI file or a live connection.
Append this to the end of any AI conversation to turn the discussion itself into a structure, with no need to describe it again.
Convert this conversation into a Mermaid flowchart I can import into a knowledge graph tool.
Rules:
- Opening line must be: flowchart TD
- Node IDs must use alphanumeric characters and hyphens only (e.g. payment-api not "Payment API")
- Node labels go inside brackets: nodeID[Label Here]
- Use [square brackets] for most nodes
- Use (round brackets) for processes or steps
- Use {curly brackets} for decisions or branch points
- Use ((double brackets)) for key goals or outcomes
- Connect nodes with --> for directed flow, --- for undirected, <--> for bidirectional
- Label edges where the relationship has a clear name: A -->|feeds into| B
- Aim for 10 to 20 nodes. Collapse minor details and keep the concepts that matter most
- Do not include subgraph, style, classDef, or click lines
Output only the Mermaid code block. No explanation before or after it.For a topic you haven't discussed yet. Nine times out of ten, just saying "turn this conversation into a mermaid chart code" is enough. For more control:
Generate a Mermaid flowchart of [describe your topic here].
Rules:
- Opening line must be: flowchart TD
- Node IDs must use alphanumeric characters and hyphens only (e.g. market-research not "Market Research")
- Node labels go inside brackets: nodeID[Label Here]
- Use [square brackets] for most nodes
- Use (round brackets) for processes or steps
- Use {curly brackets} for decisions or branch points
- Use ((double brackets)) for key goals or outcomes
- Connect nodes with --> for directed flow, --- for undirected, <--> for bidirectional
- Label edges where the relationship has a name: A -->|depends on| B
- Aim for 12 to 20 nodes. Focus on key concepts, not exhaustive detail
- Do not include subgraph, style, classDef, or click lines
Output only the Mermaid code block. No explanation before or after it.Replace the bracketed description with something specific, for example "the components of a SaaS startup's go-to-market strategy", or "how a payment transaction flows from customer to bank".
Ask what's missing, once the AI has your project.
Looking at the knowledge graph I have shared with you, please identify:
1. Important concepts that appear to be missing from the graph entirely
2. Nodes that seem underdeveloped: isolated with few connections, or lacking in related ideas
3. Connections that are implied by the existing structure but not explicitly drawn
4. Any areas where the graph feels unbalanced: too much detail in one area, too little in another
For each finding, suggest a concrete action: a node to add, a connection to draw, or a note to write.
Keep your response structured and specific to the nodes and connections in this graph. Do not make generic suggestions that could apply to any knowledge graph.Ask the AI to develop one node further.
Looking at the node "[node name]" in the knowledge graph I have shared:
1. Suggest 5 new nodes that would meaningfully extend or connect to this one
2. For each suggestion provide:
- A short node name suitable as a file name
- Which entity type it should be, using the types defined in my graph
- One sentence describing what it represents
- How it should connect to "[node name]": the connection type and direction
Focus on genuine gaps in the current graph. Do not suggest nodes that are already there or that are close variations of what exists.mermaid fence, Filamental accepts it as it is. Paste only the code, not any explanation around it.Use the first two when a conversation has done the thinking and you want it as something you can see and move around. Use the last two when a project has grown and you want a second pair of eyes on what's thin, missing or unbalanced.
Still stuck? Email [email protected].