Flowix

Prompts

The core of docs + AI isn't "asking smarter questions" -- it's treating prompts as engineering documentation. This section gives you a reusable pattern.

1. Why not write them in the chat box

Me: "Help me polish this"
AI: (doesn't know what to polish or what style, makes blind changes)

Writing prompts in a document brings 4 natural benefits:

  • Readable -- multi-line, annotatable, with examples; the AI understands more accurately
  • Versionable -- save once per word changed, gradually approaching the optimum
  • Reusable -- save to the Prompts/ directory, invoke with /
  • Shareable -- colleagues can copy and use it immediately

2. The minimal structure of a prompt

A prompt file should contain at least 4 sections:

# Prompt: Write this week's weekly report

## Role
You are a senior engineer writing a weekly report.

## Input
I will paste a week of work logs (plain text, one entry per line, date at the start of each line).

## Output
- A ≤ 100-word summary of this week (use 3 bullets for highlights)
- A ≤ 80-word plan for next week
- Use English, restrained tone, no piling up words
- No pleasantries, no preamble

## Example
Input:
2026-07-06 Completed module a of X
2026-07-07 Fixed a Y bug
2026-07-08 Peer review
Output:
**This week**: Advanced module a of X, fixed a critical Y bug, completed team review.
**Next week**: Advance module b; sync API with Z.

Copy this entire block to the Flowix cursor position -> Cmd/Ctrl + L -> select Agent -> press Enter. The Agent will output according to the requirements above.

3. Template variables

Use `` placeholders; the Flowix AI panel input box will automatically render them as form fields:

# Prompt: Translate

Please translate the following  text into :

"""

"""

After invoking with Cmd/Ctrl + L, the panel shows 3 form fields (language, content); fill them in and submit.

This is using prompts as configuration -- reuse the same skeleton, change parameters to switch scenarios.

4. Review and iteration

AI responses are usually imperfect; three common follow-ups:

  • "Make it shorter"
  • "Add 2 more examples"
  • "For point 3, also list the opposing view"

Append these directly in the document as a conversation flow. Flowix passes the entire block as context to the next Agent round, so you don't lose any history.

Review timing -- If a particular prompt repeatedly gives you the same type of good answers, pin down its "output format" section, turn it into a template, and save it to the Prompts/ directory.

5. Anti-patterns

❌ Do not write in prompts:

  • "Please think carefully" -- useless; LLMs all "think"
  • "Explain like a 5-year-old" -- vague; rewrite as "use vocabulary at a 3rd-grade level, short sentences, no more than 50 words"
  • "High-quality answer" -- unobservable; rewrite as specific word count, paragraph count, bullet count

✅ What you should write:

  • Clear input/output format
  • One complete example (input + output)
  • Specify language, word count, style

6. Concrete applications

This structure is also the foundation for the next two sections: PPT generation skill and Flowchart generation skill are both prompts with a particularly specific "output format" section.