Your writing style is more specific than “friendly and professional.” It shows up in how you open a piece, explain a point, use examples, and ask the reader to act.
OGAD (Off Grid AI Desktop) can help you inspect your own writing samples with a local model and turn the patterns into a reusable guide. Check each proposed rule against the examples, then test the guide on a fresh draft. After setup, the work can stay on your computer.
Download OGAD | Desktop releases
What would you like to do with Off Grid AI?
Have a feature or use case you would like us to support? Tell us what you want to do and which device you use.
Write to support@offgridmobileai.co, join our Slack community, or talk to us on Reddit.
The useful result is a set of instructions that help you edit consistently. It should describe choices you want to repeat, not freeze every habit from an old article into a permanent rule.
Which writing samples should you choose?
Choose work that represents the voice you want now. Use a few pieces for the same audience or purpose before mixing personal essays, support messages, and technical articles into one guide.
Suppose you write practical articles for small business owners. You prefer direct openings, concrete examples, and a short next step. Three strong articles can give you enough material to examine those choices.
| Sample quality | Why it matters |
|---|---|
| Written or approved by you | The guide reflects choices you own |
| Relevant audience | Style depends on who is reading |
| Finished work | Rough drafts may contain habits you would normally remove |
| Varied examples | A rule should survive more than one topic |
| Clear source labels | You can check where a pattern came from |
Keep one additional piece aside for testing. A guide that only describes the samples used to create it may not help with new work.
What do you need in OGAD?
Install the app and download a local text model. Save the samples as readable TXT, Markdown, DOCX, or text PDFs. Complete downloads while connected before working offline.
The procedure uses free core desktop chat on supported Mac and Windows computers. Linux packages are available in 0.0.54-beta.108 as a beta.
Remove private details that are not needed for style analysis. The model can examine sentence structure and organisation without retaining a real client's confidential facts in the reusable guide.
Keep the samples and the resulting guide separate. The guide should contain useful rules and brief examples, not a large copy of every source article.
How do you identify the patterns?
Attach the samples to a new chat and ask for observations with evidence. Distinguish patterns that appear repeatedly from a choice used only once.
- Select a downloaded local model in Models > Text.
- Open a new chat and choose + > Attach files.
- Add a manageable set of samples.
- Inspect the extracted text to confirm it is readable.
- Ask for a source-backed style analysis.
The file-processing path supplies source text. It does not know which stylistic choices you value unless you review and select them.
Try:
Analyse these writing samples for practical style choices. Cover openings, sentence structure, paragraph length, examples, headings, evidence, and endings. Give a short source example for each observation. Separate repeated patterns from one-off choices. Do not claim that a style choice caused traffic or sales.
How do you turn observations into useful rules?
Write rules a person or model can apply to a draft. “Be engaging” is too broad. “Open with the reader's concrete problem, then explain the useful result” gives the editor something to check.
Review each proposed rule and ask whether it describes your intended voice. You may decide that an old habit, such as long introductions, should not be carried forward.
Ask:
Turn these approved observations into an editing guide. For each rule, explain what to do, why it helps this audience, and a short before-and-after example using invented neutral content. Keep exceptions where a different choice may be useful.
Check that the examples do not add factual claims or copy private details from the samples. They should demonstrate wording, not become evidence about your business.
What should the guide include?
Keep it short enough to use during a real edit. A clear description of audience, purpose, voice, and evidence standards is more useful than dozens of rigid word-count rules.
A practical guide can contain:
- The reader and the job the writing should help them do.
- Opening and structure preferences.
- Sentence and paragraph guidance.
- How to use examples and sources.
- Words or habits to avoid.
- What a useful ending asks the reader to do.
- A small set of approved examples.
Keep factual standards separate from style preferences. A lively tone does not justify invented proof, customer quotes, or results.
How do you test the guide on a new draft?
Use the sample you held aside or write a fresh paragraph on a related topic. Ask the local model to edit with the guide and explain the changes.
Edit this draft using the attached style guide. Preserve its facts and meaning. After the revision, list the most important changes and the rule behind each. Flag any instruction that is unclear or conflicts with the task.
Compare the revision with what you would write yourself. If the model makes every sentence the same length or removes useful nuance, revise the guide rather than forcing the draft to fit it.
The goal is consistency with judgement. A reusable guide should leave room for the subject and reader.
How can you reuse it in OGAD?
Save the approved guide as a local document and attach it when editing. For repeated work, create a project with Projects > New project and add the guide through Knowledge & settings > Knowledge base > Add files.
You can also put a short version of the core instructions in the project's System prompt field and click Save. The project settings support persistent project instructions.
Keep the full guide available for review. Project retrieval is limited and instructions do not guarantee perfect compliance. Check whether the final draft actually follows the rules that matter.
How do you keep the guide from becoming stale?
Update it when you repeatedly reject the same kind of edit. Add a clear example of the choice you prefer, and remove rules that cause awkward or repetitive writing.
| Problem | Useful change |
|---|---|
| Every introduction sounds identical | Describe the purpose of an opening, not one mandatory sentence |
| The model adds hype | Add a concrete rule against unsupported claims |
| Important context disappears | State what must be preserved during shortening |
| The guide is too long to apply | Keep the core rules and move examples below them |
| One audience gets the wrong tone | Create a separate guide for that audience |
Do not infer that a rule caused your best article's performance merely because it appears there. Use reader feedback and actual results as separate evidence when deciding what to keep.
Build a guide you can edit with tomorrow
Download OGAD and choose a few strong samples of your own work. Extract the patterns, approve the useful rules, and test them on a new draft.
Keep the model local for processing after setup. Sharing or publishing the edited work is separate. The useful result is a practical guide that helps the writing sound more like your considered choices.
Top comments (0)