1. Home
  2. /
  3. KnowledgeFlow Docs
  4. /
  5. KnowledgeFlow Key Feature...
  6. /
  7. Images, Charts & Gra...

Images, Charts & Graphs

Images

Summary

Create images by describing what you want to see, how it should look (style), and any key constraints (layout, colours, size). You can also upload an image and ask for specific edits.

Key steps

  • Say you want an image (photo, illustration, icon, infographic).
  • Describe the subject, setting, and must-have details (colours, mood, objects).
  • Specify style (for example photorealistic, flat vector) and dimensions/aspect ratio.
  • If editing, upload the image and describe the changes.

Example prompts

  • “Generate a photorealistic image of a modern office reception, bright natural light, minimal décor, 16:9.”
  • “Create a clean flat-vector icon set of: search, upload, settings, security. Blue and grey, transparent background.”
  • “Edit this uploaded image: remove the background, keep the product centred, add a soft shadow, white backdrop.”

Best practices

  • Be specific about style and quality.
  • Provide dimensions/aspect ratio and any non-negotiables (brand colours, background).
  • For infographics, list the sections and labels you want.

Common mistakes to avoid (and fixes)

  • Too vague (“make it nice”) → add subject, style, lighting, composition.
  • Wrong output type → explicitly say “photorealistic image” or “vector illustration”.
  • Poor edit results → upload a clear image and describe edits precisely.

Output options

  • Upload and edit supports PNG, JPG, WebP up to 50MB.

Graphs/Charts

Summary

Create charts by stating the chart type and providing clean, labelled data (categories and numbers, or time series). The clearer your data and labels, the better the chart.

Key steps

  • Ask for a chart type (bar, line, pie, etc.).
  • Provide the data values in a simple list.
  • Add labels: title, axes, units, and series names.
  • Confirm any preferences (sorting, colours, show data labels).

Example prompts

  • “Create a bar chart of tickets by priority: P1 12, P2 34, P3 57, P4 21. Title: ‘Tickets by Priority’.”
  • “Show a line chart of monthly revenue (£k): Jan 120, Feb 135, Mar 128, Apr 150, May 165, Jun 172.”
  • “Create a pie chart of spend: Sales 40%, Marketing 30%, Operations 20%, Other 10%.”

Best practices

  • Always include numbers and specify the chart type.
  • Use consistent units and clear category names.
  • Keep legends readable with short series names.

Common mistakes to avoid (and fixes)

  • No numbers → add a simple category:value list.
  • Missing labels → specify title, axis names, and units.
  • Too many categories → ask for top N or group small items into “Other”.

Output options

  • Charts are interactive (hover tooltips, clickable legends, responsive).
  • Charts can be included in PDF export as captured images.

Flowcharts

Summary

Create flowcharts by listing the steps in order and calling out decision points (yes/no) and outcomes. Keep one process per diagram for clarity.

Key steps

  • Ask for a flowchart (or process diagram).
  • List the steps from start to end.
  • Add decision points with explicit Yes/No paths.
  • Include key actors/systems (User, Admin, System) and error paths if relevant.

Example prompts

  • “Create a flowchart for user sign-up: Start → Enter email → Verify email → Create password → Account created → End.”
  • “Draw a flowchart for document upload: Select file → Validate type/size → Upload → Process/OCR (if needed) → Index → Ready to search. Include an error path for invalid file type.”
  • “Create a flowchart for approvals: Submit request → Manager review (approve/reject) → If approved, schedule work → If rejected, notify requester.”

Best practices

  • Use clear step names and include exception paths.
  • If it’s complex, split into smaller diagrams (happy path vs exceptions).
  • Label who does what (User/System/Admin) to avoid ambiguity.

Common mistakes to avoid (and fixes)

  • Missing decision outcomes → specify what happens on Yes vs No.
  • Too much in one diagram → break into multiple diagrams.
  • Unclear responsibilities → label the actor per step.

Output options

  • Diagrams render inline and can be exported (for example via PDF export handling).