AIUNIFY PROS SUITE includes a dedicated Writing category containing eleven subscriber Tools:
The current Sidebar routes these Tools to /writer, /blog-post, /article-writer, /summary, /headline-generator, /content-improver, /story, /poem-generator, /grammar, /paraphraser, and /tone-converter.
The Writing category currently contains two different interface architectures.
These have their own dedicated controls:
These use the shared ToolPage interface documented in Chapter 12:
This distinction matters because controls available in one Writing Tool should not be assumed to exist in another.
Most Writing generation workflows use AIUNIFY's shared AI-generation infrastructure.
The shared stream retrieves the subscriber's:
and sends them to the AI stream request.
For Writing Tools that use useGeminiStream, the normal PROS SUITE Model selected through the Model controls described in Chapter 10 applies.
For Writing Tools using useGeminiStream, configured provider keys can be forwarded through the shared AI request headers.
Headline Generator is an important exception addressed later in this chapter.
The inspected Writing pages do not establish a centralized persistent:
Generated Writing content is generally maintained in the active browser page until copied, downloaded where supported, edited locally, regenerated, or the page is left/refreshed.
There is no universal Save button across the current Writing category.
Where you want to preserve content, use the Tool's available:
controls or manually preserve the result externally.
Navigate to:
Sidebar → Writing → Content Writer
Route:
/writer
The /writer Route checks authentication and redirects unauthenticated users to:
/login.
The specialized workspace is titled:
AI Content Writer.
The interface states:
“Generate high-quality content including blog posts, marketing copy, product descriptions, and more.”
The left Card is titled:
Content Settings.
Required field:
Topic/Subject *
with example:
“e.g., Benefits of Remote Work”.
The second required control is:
Content Type *.
Current choices are:
Content Writer requires both:
If either is missing:
Missing Information
with:
“Please provide a topic and select a content type.”
Optional field:
Keywords (Optional).
Placeholder:
“e.g., productivity, efficiency, work-life balance”.
If Keywords are entered, the current Prompt explicitly includes:
Keywords to include: [keywords].
Content Writer does not source-verify:
The subscriber supplies the Keywords.
Content Writer includes:
Tone (Optional).
Current choices:
If selected, the Prompt includes:
Tone: [tone].
The current Prompt asks the AI to make the result:
Its shared System Prompt identifies the AI as an expert:
and instructs it to create engaging, search-optimized content using persuasive copywriting, proper grammar, and style.
Primary action:
Generate Content.
While active:
Generating....
The result streams into the output area while generation is active.
After successful completion:
Content Generated!
with:
“Your content has been successfully created.”
If generation fails:
Error
with the returned Error or:
“Failed to generate content. Please try again.”
The right Card is titled:
Generated Content.
Select:
Preview
to view the generated content through AIUNIFY's Markdown renderer.
Select:
Edit
to open the generated result inside an editable Textarea.
While generation is still active, the Edit Textarea is read-only.
After generation finishes, edits made in Edit change the current local output state.
Once a completed output exists, Content Writer exposes an icon Button for:
Copy.
Current notification:
Copied!
with:
“Content copied to clipboard.”
Content Writer also provides a Download action.
The file is:
plain text (.txt).
The current pattern is:
[content-type]-[topic].txt
with Topic spaces replaced by hyphens and converted to lowercase.
A Blog Post about:
Benefits of Remote Work
would produce a filename based on:
blog-benefits-of-remote-work.txt
Content Writer does not currently establish Word/DOCX export.
No PDF export is source-verified.
The Edit tab does not expose manual:
toolbar controls.
It is a Textarea.
There is no dedicated:
Word Count
or:
Target Length
control in Content Writer.
If length matters, include it in the Topic/Subject wording or other supplied instructions.
Example:
“Write approximately 1,200 words about the benefits of remote work for small-business owners.”
Content Writer does not source-verify external web research or source citation retrieval.
Verify factual claims independently when accuracy matters.
The feature catalogue lists:
Content Writer — 20 Tokens.
Unlike Standard ToolPage Tools, this specialized Content Writer screen does not display a per-use Token badge beside the Generate button.
Content Writer sends:
writer
as its Tool ID through the shared stream.
This makes the 20-Token catalogue value relevant to the backend usage pathway, subject to current system configuration.
Navigate to:
Sidebar → Writing → Blog Post
Route:
/blog-post.
The actual Standard ToolPage title is:
Blog Post Generator.
“Generate SEO-optimized blog posts on any topic with engaging content.”
“Enter your blog topic, target keywords, and any specific points you want covered...”
The current examples are:
Therefore it includes:
The route and feature catalogue both identify:
25 Tokens
as the base Blog Post cost.
Because this is ToolPage, the displayed cost uses this hierarchy:
blog-postIf the selected Model is identified as OpenAI, ToolPage multiplies the base cost by:
1.5
and rounds upward.
A 25-Token base would therefore display 38 Tokens in that source-defined scenario unless system settings override the base.
“SEO-optimized” is an AI writing instruction.
This page does not source-verify:
Standard ToolPage downloads Blog output as:
blog-post-output.txt.
Navigate to:
Sidebar → Writing → Article Writer
Route:
/article-writer.
Article Writer.
“Create well-researched, informative articles on any subject.”
“Describe the article topic, length, and key points to cover...”
Current examples include:
Current base:
25 Tokens.
The page description calls the output well-researched, and its configured writing guidance asks for informative articles and citations where appropriate.
However, this Standard ToolPage does not independently browse the web or retrieve external research sources.
If an Article contains:
verify them before publication.
There is no dedicated length selector.
Specify desired length in the Prompt.
Standard output filename:
article-writer-output.txt.
Navigate to:
Sidebar → Writing → Summarizer
Route:
/summary.
The Summary Route redirects unauthenticated users to /login.
The actual page title is:
AI Document Summarizer.
“Quickly summarize long documents, articles, or text content while preserving key information.”
Despite:
the current page contains no actual file-input control.
Its operational workflow is:
Paste text into the Textarea → Summarize Text.
This current Summarizer page does not establish direct PDF upload.
No Word/DOCX file input exists.
Even plain-text files cannot currently be selected through a file picker on this page.
The Input Card is:
Input Text.
“Paste your text content below to get a comprehensive summary.”
“Paste your long text, article, or document content here...”
If submitted blank:
Error
with:
“Please enter some text to summarize.”
Primary action:
Summarize Text.
During generation:
Summarizing....
The page sends:
“Please summarize this text:”
followed by the supplied text.
The System Prompt asks the AI to create concise yet comprehensive summaries containing:
There is no:
control.
There is no dedicated:
selector.
The right Card is:
Summary
with:
“Your AI-generated summary will appear here.”
The Summary output supports:
Preview.
It also supports:
Edit.
The Edit Textarea is read-only while streaming.
Unlike Content Writer and Grammar Check, this current specialized Summarizer does not expose a dedicated Copy button in the inspected page.
The current Summarizer also does not expose Download.
To preserve an edited Summary, manually select/copy the output or use normal browser/OS text-selection methods.
The interface presents three feature descriptions:
“Extracts main ideas and important details”
“Handles long texts with intelligent compression”
“Clear, organized summaries”
No explicit maximum character or Token length is exposed to the subscriber in this component.
Actual Model/context limits may still apply.
The catalogue identifies:
Text Summarizer — 15 Tokens.
Summarizer sends:
summary
as its shared streaming Tool ID.
The specialized Summarizer page itself does not show a fixed 15-Token label beside the Button.
Navigate to:
Sidebar → Writing → Headlines
Route:
/headline-generator.
The page title is:
Headline Generator.
“Craft scroll-stopping titles that drive clicks. Perfect for blogs, newsletters, and social media.”
Main Prompt field:
“What is your content about? (e.g. 'productivity tips')”.
If blank:
Topic required
with:
“Please enter a topic to generate headlines for.”
Pressing Enter in the Topic field triggers generation.
Headline Generator has a dedicated Tone selector.
Current options:
Default:
Catchy & Viral.
Headline Generator includes a dedicated:
Quantity
Slider.
Current range:
1 to 10.
Default:
5 Headlines.
Primary Button:
Generate.
The current request instructs the AI:
Generate [quantity] [tone] headlines
for the Topic and return:
After generation, the client:
1. or 1).Because result lines are parsed and very short lines are filtered, the number displayed can theoretically differ from the selected Quantity.
Each result appears in its own Card.
Each Headline Card displays the current Tone identifier.
Each result also displays:
[number] chars.
Each Headline provides its own Copy Button.
Copied!
with:
“Headline copied to clipboard.”
No source-verified Copy All action exists.
This specialized Headline workspace does not provide a Download button.
Generated Headline sets are page state rather than a source-verified persistent library.
Before generation:
“Enter a topic above to start generating headlines”.
The interface explicitly says:
Uses 10 tokens.
The feature catalogue also identifies:
Headline Generator — 10 Tokens.
The request sends the currently selected PROS SUITE Model.
Headline Generator directly calls /api/ai/proxy with only:
Content-Type: application/json
and does not append the subscriber's normal provider API-Key headers.
Therefore:
Headline Generator uses the selected Model identifier, but the current client does not forward the subscriber's Chapter 11 BYOK provider keys through this specific request.
Selecting SEO Optimized changes the requested writing style.
It does not run live keyword/SERP research.
Navigate to:
Sidebar → Writing → Content Improver
Route:
/content-improver.
Content Improver.
“Enhance and polish your existing content for better clarity and impact.”
“Paste your content here to improve its clarity, flow, and engagement...”
Current examples include:
Current base:
15 Tokens.
This page does not provide separate controls for:
State those requirements directly in the Prompt.
The configured Content Improver guidance asks the AI to improve:
while maintaining original voice and intent.
Because Content Improver uses ToolPage, completed output supports:
.txt Downloadcontent-improver-output.txt.
Navigate to:
Sidebar → Writing → Story Writer
Route:
/story.
The Story Route redirects unauthenticated subscribers to /login.
AI Story Writer.
“Create compelling stories and scripts with AI assistance. Choose your genre, characters, and plot elements.”
The input Card is:
Story Details.
Visible optional field:
Story Title (Optional).
Although Story Title is stored in page state, the current generation Prompt does not include the title value.
Therefore:
Entering a Story Title does not currently source-verify that the Title affects the generated Story.
Required:
Genre *.
Current genres:
Generation cannot proceed without Genre.
Visible selector:
Format.
Current visible choices:
The selected length/Format state is never inserted into the Prompt submitted by handleGenerateStory().
This means the current screen may visually allow selection of:
Medium Story
or:
Script Format
without actually telling the AI that selection during generation.
Regardless of the visible Format selection, the current Prompt begins:
“Write a creative short story...”
and asks for a clear:
Until the Format control is wired into generation, put the requested format directly in:
Plot/Premise
or another submitted field.
For example:
“Write this as a screenplay-style script with dialogue and scene directions.”
Required:
Plot/Premise *.
“Describe your story's main plot, conflict, or premise...”
The current validation requires:
If missing:
Error
with:
“Please select a genre and provide a plot description.”
Story Writer includes:
Generate Random Prompt.
This does not call AI.
It randomly selects one of five hardcoded Premises and places it into the Plot field.
The source includes ideas involving:
Optional:
Main Characters (Optional).
If left empty, the Prompt instructs AI to:
Create interesting characters as needed.
Optional:
Setting (Optional).
If blank, the Prompt instructs AI to:
Choose an appropriate setting.
Optional:
Tone (Optional).
The subscriber enters a field labeled Tone, but the generation Prompt inserts it as:
Theme: [tone].
If Tone is blank:
“Match the genre appropriately”.
Primary Button:
Generate Story.
During generation:
Creating Story....
The custom System Prompt instructs AI to write:
The output Card is:
Generated Story.
Story Writer includes:
Preview.
It also includes:
Edit.
After generation, the Edit Textarea can be changed manually.
Inside the Edit view, once streaming has stopped:
Copy Story.
Current Toast:
Copied
with:
“Story copied to clipboard.”
No .txt, DOCX, PDF, EPUB, or screenplay export is provided on this page.
A separate Card is:
Popular Genres
with:
“Click on any genre to select it”.
Clicking a Genre Badge changes the current Genre field.
The feature catalogue identifies:
Story Generator — 25 Tokens.
Unlike Content Writer, Summarizer, and Grammar Check, Story Writer calls the shared stream without passing a story Tool ID.
Therefore:
25 Tokens is the current catalogue reference for Story Generator, but the inspected Story client does not identify the generation as story in its stream call. This chapter does not present 25 Tokens as a guaranteed live Story charge.Navigate to:
Sidebar → Writing → Poem Generator
Route:
/poem-generator.
Poem Generator.
“Create beautiful poems in various styles - sonnets, haikus, free verse, and more.”
“Describe the theme, emotion, or style of poem you want...”
Current examples:
Although the description mentions Sonnets, Haikus, and Free Verse, there is no dedicated style dropdown.
Specify the desired poetic form in the Prompt.
There is no separate:
control.
There are no numeric controls for:
Current base:
15 Tokens.
The Writing feature catalogue agrees at 15 Tokens.
The Sidebar correctly places Poem Generator under:
Writing.
However, the Poem ToolPage itself passes:
category="Creative".
Therefore, a subscriber may see a Creative Badge inside a Tool reached from the Writing Sidebar category.
Standard filename:
poem-generator-output.txt.
Navigate to:
Sidebar → Writing → Grammar Check
Route:
/grammar.
The Grammar Route checks authentication and redirects to /login when necessary.
AI Grammar Check.
“Improve grammar, style, and readability of your text while maintaining your voice.”
The left Card is:
Original Text.
“Paste your text below to check grammar and style.”
“Enter your text here...”.
If blank:
Error
with:
“Please enter some text to check.”
Grammar Check includes example text Buttons.
The exampleTexts array contains three sample sentences, but the page deliberately renders only:
exampleTexts.slice(0, 2).
Therefore only the first two are currently visible.
Primary action:
Check Grammar.
During processing:
Checking....
The Prompt asks AI to:
The AI is specifically asked to return:
CORRECTED TEXT:
followed by the corrected version, and:
IMPROVEMENTS:
followed by bullet-listed changes.
After generation, the client separates the response at:
IMPROVEMENTS:
and removes:
CORRECTED TEXT:
from the corrected-content portion.
Only lines beginning with a hyphen are converted into the structured Improvements list.
If the AI does not follow the requested structure exactly, the Improvements section may be incomplete or absent.
The right Card is:
Improved Text.
Grammar Check provides:
Preview.
Grammar Check provides:
Edit.
After streaming ends, the Edit Tab contains:
Copy Corrected Text.
Current notification:
Copied
with:
“Corrected text copied to clipboard.”
When parsed suggestions exist, a separate Card appears:
Improvements Made.
Each suggestion appears as a separate row with a check icon.
The interface highlights:
Fix grammar and spelling errors
Improve clarity and readability
Maintain your original tone
There is no current control for:
The current Grammar Check is configured specifically as an English Grammar and Style expert.
For translation, use Translation Hub instead.
Grammar Check does not expose a Download action.
The catalogue identifies:
Grammar Check — 10 Tokens.
The generation passes:
grammar
as its shared stream Tool ID.
The specialized Grammar page does not itself display the 10-Token catalogue amount.
Navigate to:
Sidebar → Writing → Paraphraser
Route:
/paraphraser.
Paraphraser.
“Rewrite any text in multiple styles while preserving the original meaning - academic, casual, concise, or creative.”
“Paste the text you want to paraphrase...”.
Examples include:
Although the description mentions multiple styles, no dedicated:
selector exists.
Specify the target style in your Prompt.
The Paraphraser page passes:
10 Tokens
to ToolPage.
However, the shared feature catalogue currently defines:
Paraphraser — 20 Tokens.
ToolPage calculates its base cost in this order:
settings.aiLimits[toolId]feature.tokenCosttokenCostTherefore:
Without a live aiLimits override, the current ToolPage should use the feature-catalogue value of 20 Tokens rather than the 10-Token route fallback.If AIUNIFY changes the live aiLimits value, that setting becomes authoritative for the displayed ToolPage cost.
ToolPage can further apply the 1.5 OpenAI multiplier after determining the base.
Completed output can be copied with the Standard ToolPage Copy action.
Filename:
paraphraser-output.txt.
Navigate to:
Sidebar → Writing → Tone Converter
Route:
/tone-converter.
Tone Converter.
“Transform the emotional tone of any text - switch between formal, casual, empathetic, assertive, humorous, and more.”
“Paste your text and specify the target tone (e.g., 'Convert to empathetic tone')...”
Current examples include:
Despite the Tool's purpose, there is no dedicated Tone dropdown.
The subscriber must specify the desired transformation in the Prompt.
There is no:
Slider.
Describe intensity in natural language.
Tone Converter passes:
10 Tokens
to ToolPage.
The feature catalogue currently defines:
Tone Converter — 20 Tokens.
Because ToolPage prioritizes the feature catalogue over the page-level fallback, the current default visible base should be:
20 Tokens
unless the current system aiLimits configuration specifies another value.
Filename:
tone-converter-output.txt.
The six current Writing-related ToolPage Tools are:
Their individual pages provide Tool-specific:
while sharing one common operating shell.
The shared Input Card displays:
Input
and:
“Describe what you want to generate”.
Submitting blank Input produces:
Input required
with:
“Please enter a prompt to continue.”
Primary Button:
Generate.
While streaming:
Generating....
Inside Standard ToolPage, pressing:
Ctrl + Enter
submits the Prompt.
The inspected handler specifically checks ctrlKey; it does not source-verify Command+Enter as an equivalent in this component.
The icon-only Reset button clears:
outputand focuses the Textarea.
As established in Chapter 12, the shared component does not explicitly clear the hook's streamedText inside handleReset().
Accordingly, Reset should not be treated as a Stop/Cancel mechanism for an active stream.
Standard ToolPage has no dedicated:
Stop Generation
button.
When examples exist:
Try these examples:
Each example Button displays only approximately the first 40 characters plus ....
Clicking it inserts the entire underlying Prompt.
The right Card is:
Output
with:
“Generated content will appear here”.
Generated text is displayed with the Markdown renderer.
The Standard output area has a maximum visible height of approximately:
500 px
before scrolling.
Completed or currently available stream text can be copied.
Copied!
with:
“Content copied to clipboard”.
Standard ToolPage provides Download whenever display content exists.
All Standard Writing ToolPage Downloads are:
plain text (.txt).
[toolId]-output.txt.
Unlike specialized Content Writer, Summarizer, Story Writer, and Grammar Check, Standard ToolPage does not contain a Preview/Edit tab system.
The generated Standard output is rendered through Markdown.
To revise it, you can:
No Save button.
No generation-history browser is present.
No Rename.
No persisted record exists in this workspace to Delete.
Standard ToolPage calculates:
settings.aiLimits → feature tokenCost → route tokenCost.
When the selected Model provider is OpenAI:
displayed cost = ceiling(base cost × 1.5).
| Writing ToolCurrent Base Reference | |
| Blog Post | 25 |
| Article Writer | 25 |
| Content Improver | 15 |
| Poem Generator | 15 |
| Paraphraser | 20* |
| Tone Converter | 20* |
*The Paraphraser and Tone Converter pages individually pass 10, but the current feature catalogue assigns 20, and ToolPage prioritizes the feature catalogue when no live aiLimits override exists.
| ToolCatalogue ReferenceVisible Fixed Cost on Specialized Page? | ||
| Content Writer | 20 | No |
| Summarizer | 15 | No |
| Headline Generator | 10 | Yes — “Uses 10 tokens” |
| Story Generator | 25 | No |
| Grammar Check | 10 | No |
Story's 25 is only a catalogue reference because its current stream invocation omits the story Tool ID.
The subscriber should treat displayed live ToolPage cost and current account behavior as authoritative over static manual examples when system configuration changes.
| ToolUses Selected Model?Shared BYOK Headers? | ||
| Content Writer | Yes | Yes |
| Blog Post | Yes | Yes |
| Article Writer | Yes | Yes |
| Summarizer | Yes | Yes |
| Headlines | Yes | No client-side BYOK forwarding in current request |
| Content Improver | Yes | Yes |
| Story Writer | Yes | Yes |
| Poem Generator | Yes | Yes |
| Grammar Check | Yes | Yes |
| Paraphraser | Yes | Yes |
| Tone Converter | Yes | Yes |
The shared-stream behavior is established in useGeminiStream; Headline Generator instead uses its own /api/ai/proxy request.
| ToolSpecialized Controls | |
| Content Writer | Content Type, Keywords, Tone |
| Summarizer | Paste Text |
| Headlines | Tone, Quantity |
| Story Writer | Genre, Format*, Plot, Characters, Setting, Tone |
| Grammar Check | Original Text + structured corrections |
| Standard ToolPage Tools | Prompt-only |
*Story Format is visible but currently not wired into generation.
| ToolBuilt-In Editable Output | |
| Content Writer | Yes |
| Blog Post | No |
| Article Writer | No |
| Summarizer | Yes |
| Headlines | No |
| Content Improver | No |
| Story Writer | Yes |
| Poem Generator | No |
| Grammar Check | Yes |
| Paraphraser | No |
| Tone Converter | No |
| ToolCopy Control | |
| Content Writer | Yes |
| Blog Post | Yes |
| Article Writer | Yes |
| Summarizer | No dedicated Copy |
| Headlines | Yes, per Headline |
| Content Improver | Yes |
| Story Writer | Yes, in Edit output |
| Poem Generator | Yes |
| Grammar Check | Yes, in Edit output |
| Paraphraser | Yes |
| Tone Converter | Yes |
| ToolDownload | |
| Content Writer | .txt |
| Blog Post | .txt |
| Article Writer | .txt |
| Summarizer | No |
| Headlines | No |
| Content Improver | .txt |
| Story Writer | No |
| Poem Generator | .txt |
| Grammar Check | No |
| Paraphraser | .txt |
| Tone Converter | .txt |
Instead of entering:
Artificial intelligence
use something such as:
“A 1,200-word educational article for insurance agency owners explaining how AI-powered lead follow-up reduces missed opportunities.”
Only enter Keywords you genuinely want included.
Overloading the field can make content unnatural.
For example:
Use the built-in Edit Tab to remove:
Example:
“Write for independent real estate brokerage owners with 10-50 agents.”
Request:
when that structure matters.
Do not publish unverified:
simply because the AI generated them.
These Writing pages do not themselves perform source-verified live web research.
For current facts, gather verified source material first and provide it as writing context.
Summarizer can only summarize what you provide in its current UI.
There is no actual file attachment on the current Summarizer page.
After summarization, compare:
against the original.
Use the Edit Tab to correct or refine the result before using it.
Use Quantity to produce several alternatives instead of accepting the first Headline.
Try the same Topic with:
and compare.
Use the displayed character count when a channel has headline/title-length limitations.
A strong Headline should accurately reflect the content it introduces.
Because the visible Format field is currently not wired into generation, repeat critical format requirements in a field that is actually submitted.
Because Story Title is not currently inserted into the generation Prompt, put the desired Title into the Plot/Premise instructions if the AI needs to use it.
Include:
when consistency matters.
Specify:
for stronger narrative consistency.
The Story's Edit Tab is useful for manually changing generated prose without running another AI generation.
Grammar correction can alter:
Review the result.
When the parser successfully extracts them, the Improvements Made list helps explain what changed.
If a business or technical phrase must remain unchanged, say so in the source text context where possible or restore it in Edit afterward.
Example:
“Paraphrase this in a concise professional tone. Preserve all numbers, product names, and legal terminology exactly.”
Always compare the paraphrase against the original when precision matters.
Example:
“Rewrite this in a confident but empathetic executive tone. Do not change any facts or pricing.”
This is particularly useful for:
Confirm:
Both are required.
Confirm the Keywords field contains the exact words you want emphasized.
AI instructions still do not guarantee every keyword appears.
There is no Target Length control.
Specify the approximate Word Count directly.
No persistent Save workflow is source-verified.
Use Copy/Download before leaving the page.
There is no actual file-upload control in the current Summarizer page.
Paste the document text into Input Text.
No Download Button exists on this specialized screen.
Copy the edited text manually.
No length control exists.
Regenerate with the important details emphasized in the supplied text/context, or manually edit the result.
Enter a non-empty Topic.
The page filters malformed/very short returned lines after generation.
No Download control exists.
Copy individual Headlines.
The Headline client sends the selected Model but does not forward normal provider-key headers in its /api/ai/proxy request.
The current Format selector is not inserted into the generation Prompt.
Place:
“Write this in script format”
inside the Plot/Premise.
The current length/Format state is not sent.
Write the desired Word Count directly into Plot/Premise.
Story Title is not currently included in the Prompt.
Repeat it within Plot/Premise when important.
No Download action is present.
Use Edit → Copy Story.
The AI response must contain parseable hyphen-prefixed lines after:
IMPROVEMENTS:.
If the response format varies, the Suggestions list can remain empty.
No Download action exists.
Use Edit → Copy Corrected Text.
This is expected in the current source even though the internal example array contains three entries.
Input must contain non-whitespace text.
The current handler explicitly checks Ctrl+Enter.
Use the Generate Button if necessary.
Standard ToolPage does not have an output editor.
Copy the result or move it to Content Improver/Tone Converter/Paraphraser.
No Save function exists.
Download the .txt file where supported.
This is consistent with current source precedence:
Feature catalogue 20 overrides page fallback 10 unless aiLimits provides another value.
The same current configuration applies to Tone Converter.
After generation:
For Blog Post, Article Writer, Content Improver, Poem Generator, Paraphraser, and Tone Converter:
The source verifies:
The current source does not establish a universal:
Several visible labels require qualification.
Called AI Document Summarizer, but current operation is pasted text only; no file-upload input is implemented.
Story Title is visible but not included in generation.
Short Story, Medium Story, Story Outline, Script Format are visible choices, but the selected Format is not included in the current generation Prompt.
Page fallback says 10 Tokens, while current feature catalogue says 20; ToolPage's precedence makes the feature value the stronger default unless system AI limits override it.
The same 10-vs-20 source discrepancy exists.
Located in the Sidebar's Writing category but currently displays a Creative ToolPage category Badge.
The strongest general operating method is:
Choose the Correct Writing Tool
→ Define the Audience
→ State the Exact Deliverable
→ Provide Source Facts and Required Details
→ Specify Tone, Length, Format, and Constraints
→ Generate
→ Review the Complete Result
→ Verify Facts, Numbers, Names, and Claims
→ Use Edit Where Available
→ Use Content Improver, Paraphraser, Tone Converter, or Grammar Check for Additional Refinement
→ Copy or Download the Approved Version
→ Preserve It Externally Before Regenerating or Leaving the Workspace
The AIUNIFY PROS SUITE Writing category currently contains eleven operational Tools spanning original content creation, summarization, headline generation, creative writing, editing, grammar correction, paraphrasing, and tone transformation.
The category is not built from one identical interface. Content Writer, Summarizer, Headline Generator, Story Writer, and Grammar Check use specialized workspaces, while Blog Post, Article Writer, Content Improver, Poem Generator, Paraphraser, and Tone Converter use AIUNIFY's shared Standard ToolPage.
Content Writer provides the richest structured business-writing interface. Subscribers choose a required Topic and Content Type, optionally supply Keywords and one of six Tones, generate streaming content, switch between Preview and Edit, Copy the completed output, and Download it as plain text. Its feature catalogue reference is 20 Tokens.
Blog Post Generator and Article Writer are Prompt-driven Standard ToolPage systems with current base references of 25 Tokens each. Their SEO/research-oriented descriptions guide AI writing, but the inspected pages do not perform live keyword research, SERP analysis, or external source retrieval.
Summarizer is currently a text-paste workflow. Despite the visible AI Document Summarizer title and Upload icon, the page does not contain a file picker. Subscribers paste text, select Summarize Text, then use Preview/Edit to refine the response. The current page provides neither a dedicated Copy nor Download action.
Headline Generator is a highly specialized workspace with five Tone modes, a Quantity Slider from 1 through 10, individual Headline Cards, character counts, and per-result Copy actions. It explicitly displays Uses 10 tokens. Its request sends the selected Model but does not forward the subscriber's normal BYOK provider headers.
Content Improver uses Standard ToolPage and currently references a 15-Token base. It has no separate improvement-style selectors, so instructions such as concise, persuasive, executive, simplified, or conversion-oriented should be placed directly in the Prompt.
Story Writer provides Genre, Plot, Characters, Setting, Tone, a Random Prompt generator, Preview/Edit output, and Copy Story. However, two visible controls are currently not wired into its generation Prompt: Story Title and Format. The Format selector visibly offers Short Story, Medium Story, Story Outline, and Script Format, but the current request still asks AI to write a creative short story without submitting the selected Format.
For that reason, subscribers should put critical length, Title, or Format instructions directly into Plot/Premise until those controls are connected to generation.
Poem Generator uses Standard ToolPage and has a 15-Token base reference. It supports poetic styles through natural-language Prompting rather than a dedicated Form/Style selector. It appears under Writing in the Sidebar even though the page currently identifies its internal category as Creative.
Grammar Check requests both corrected text and an itemized list of improvements, then parses those into an editable corrected version and separate Improvements Made section. Its catalogue reference is 10 Tokens.
Paraphraser and Tone Converter both use Standard ToolPage and require the subscriber to describe the desired Style or Tone in natural language. Each page contains a route-level 10-Token fallback, but each current feature-catalogue entry is 20 Tokens. Since ToolPage prioritizes system AI limits first, then feature-catalogue cost, then route fallback, the catalogue's 20-Token value is the stronger default unless current system configuration overrides it.
Across the Standard Writing Tools, ToolPage provides:
.txt Downloadbut does not provide persistent Save, History, layered editing, DOCX/PDF export, or a universal document-management system.
The recommended Writing workflow is:
Write or Supply the Core Information → Generate the First Draft → Improve Structure and Clarity → Paraphrase Where Necessary → Convert Tone for the Audience → Run Grammar Check → Verify All Facts → Copy or Download the Approved Version
This turns the Writing category into a practical multi-stage workflow rather than treating every Tool as an isolated generator.