When to use
- The user asks to "write a document", "create a report"
- An article, post, or letter is needed
- Instructions, regulations, or a description are required
- Any structured text
Work process
1. Clarify the details
Before creating, ask:
- Type: What is this? (article, letter, report, instructions)
- Audience: Who will read it?
- Tone: Formal, friendly, neutral?
- Length: Approximate size?
- Format: Is formatting needed? (headings, lists)
2. Choose the format
| Format | When to use |
|---|---|
| text | Plain text without formatting |
| markdown | With headings, lists, emphasis |
3. Call the tool
createDocument({ type: 'markdown', title: 'Document title', content: '... document text ...' })
Structures by document type
Article / Post
- Title (catchy)
- Introduction (what it is about and why)
- Main part (break into sections)
- Conclusion (takeaways, call to action)
Business letter
- Greeting
- The essence of the matter (first paragraph)
- Details (if needed)
- Request / Proposal
- Signature
Instructions
- Goal (what we will get as a result)
- Requirements (what is needed to start)
- Steps (numbered)
- Common mistakes (optional)
- Contacts for questions
Report
- Summary (the main points in 2-3 sentences)
- Context (what was done and why)
- Results (with numbers)
- Problems (if there were any)
- Next steps
Rules for good documents
Do
- Start with the main point
- Short paragraphs (3-5 sentences)
- Subheadings for navigation
- Lists instead of enumerations in the text
Don't
- Long introductions "about nothing"
- Walls of text without breaks
- Officialese and clichés
- Repetition of the same thing