12.1 Overview

A large portion of AIUNIFY PROS SUITE uses a shared Standard AI Generator Workspace.

Although each Tool performs a different business function, many share the same operating pattern:

Open Tool

Review Tool Name, Category, Description, Token Cost, and Balance

Enter Instructions in Input

Optional:

Use an Example Prompt

Generate

Watch the Result Stream into Output

Review

Copy or Download

Revise Prompt and Generate Again if Necessary

The current source contains 77 Tool pages using this shared ToolPage component, including tools across Writing, Marketing, Business, Development, Communication, Data & Analytics, Design & UX, AI Agents, and other categories.

This chapter explains the shared workspace itself so you do not need to relearn the same controls every time you open another standard generator.

12.2 What Is a Standard AI Generator?

A Standard AI Generator is a PROS SUITE Tool built around the shared interface containing:

  1. Tool Name
  2. Category
  3. Tool Description
  4. Token cost
  5. Current Token Balance
  6. Input
  7. Prompt field
  8. Generate
  9. Reset icon
  10. Optional Example Prompts
  11. Output
  12. Streaming result
  13. Copy
  14. Download

The shared component defines these common controls centrally.

12.3 Examples of Tools Using the Standard Workspace

Current source examples include:

  1. A/B Test Copy Generator
  2. Accessibility Checker
  3. API Documentation Generator
  4. Apology Drafter
  5. Article Writer
  6. Blog Post Generator
  7. Bug Fix Assistant
  8. Business Plan Generator
  9. Buyer Persona Creator
  10. Character Creator
  11. Code Agent
  12. Code Reviewer
  13. Color Palette Generator
  14. Competitor Analysis Generator
  15. Content Calendar Generator
  16. Content Improver
  17. Contract Generator
  18. Cron Expression Builder
  19. CSV Analyzer
  20. Data Visualizer

Many additional tools use the same component.

12.4 Not Every PROS SUITE Tool Uses This Workspace

This chapter does not mean every PROS SUITE Tool works this way.

Specialized applications can have completely different interfaces.

Examples include:

  1. Website Builder
  2. Pitch Deck
  3. Browser Control
  4. AI Voice Agent
  5. Music Generator
  6. Live Chat
  7. AI Meeting
  8. Game Developer
  9. AI Marketing Studio
  10. Image Generator
  11. Video Generator
  12. Reels Generator
  13. Avatar Studio
  14. Brochure Designer
  15. WhatsApp Agent
  16. Instagram Agent
  17. Trading Terminal

Those Tools are documented individually in their dedicated chapters.

12.5 Similar-Looking Tools Can Still Be Custom

A Tool can resemble the standard generator without actually using the shared ToolPage.

For example, the Grammar Tool has its own:

Original Text

area and its own workflow despite also presenting example inputs and AI-generation controls.

Therefore:

Use this chapter when the Tool presents the shared Input → Generate → Output workspace described below.

12.6 Authentication Is Required

The standard ToolPage checks whether the user is authenticated.

If authentication has not been established, the Tool redirects toward:

Login.

If a standard Tool unexpectedly sends you to Login:

  1. Sign in again.
  2. Complete Email Verification if necessary.
  3. Complete 2FA if enabled.
  4. Return to the Tool.

12.7 Standard Workspace Layout

On larger screens, the main workspace is arranged into two columns:

Left

Input

Right

Output

The shared layout uses a two-column arrangement at larger display sizes.

On narrower screens, the responsive layout can stack these areas vertically.

12.8 Tool Header

At the top of the page, the Tool displays:

  1. Tool icon
  2. Tool Name
  3. Category badge
  4. Description


Always review this area when opening a Tool so you know which specialized generator you are using.

12.9 Tool Name

The large heading identifies the current Tool.

Examples from current standard Tool pages include:

Business Plan Generator

Article Writer

Content Improver

Code Reviewer

Buyer Persona Creator

The exact Name changes by Tool, but the workspace remains familiar.

12.10 Category Badge

Beside the Tool Name is a Category badge.

Examples include:

  1. Writing
  2. Marketing
  3. Business
  4. Development
  5. Communication
  6. Design & UX
  7. Data & Analytics
  8. AI Agents

The shared ToolPage displays this Category directly beside the Tool heading.

12.11 Tool Description

Under the Tool Name is a short description explaining the purpose of that Tool.

For example, Business Plan Generator is currently described as:

“Create comprehensive business plans with executive summaries and financial projections.”

Use the description to confirm that the Tool matches the outcome you need.

12.12 Token Information

Below the Tool Header, the standard workspace displays:

[number] tokens per use

and:

Your balance: [number] tokens.

Review both before generating.

12.13 Tokens Per Use

The first Token indicator tells you the currently displayed cost for one standard generation:

[number] tokens per use.

The amount can vary from Tool to Tool.

12.14 Your Balance

Beside the per-use cost is:

Your balance: [number] tokens.

This is the current account Token Balance known to the user session.

Before generating, make sure the available balance is appropriate for the displayed operation.

12.15 How the Standard Cost Is Determined

The shared workspace calculates the base cost from:

  1. The current configured Tool cost when one exists.
  2. Otherwise, the Tool's feature-defined cost.
  3. Otherwise, the ToolPage's fallback Token cost.

The shared ToolPage's final fallback is currently 10 Tokens.

For user operation, however, the important number is the one displayed on the current Tool screen.

12.16 Model Selection Can Affect Cost

If the currently selected Model is recognized as an OpenAI-provider Model, the shared workspace currently displays:

Base Cost × 1.5

rounded upward.

Therefore:

Change Model → Recheck Token Cost → Generate

12.17 Input Section

The left side of the workspace is titled:

Input

with:

“Describe what you want to generate”.

This is where you provide instructions for the AI.

12.18 The Prompt Field

The large text area beneath Input is the Prompt field.

Its placeholder changes according to the Tool.

For example:

Business Plan Generator

“Describe your business idea, target market, and goals...”

Article Writer

“Describe the article topic, length, and key points to cover...”

Code Reviewer

“Paste your code for review. Include context about what it should do...”

CSV Analyzer

“Paste your CSV data here (include headers). The AI will analyze patterns, outliers, and key insights...”

12.19 The Placeholder Tells You What the Tool Needs

Do not ignore the Tool-specific placeholder.

It often tells you:

  1. What kind of information to enter
  2. What context is useful
  3. Whether existing content should be pasted
  4. Whether data should include headers
  5. Whether goals, audience, keywords, or constraints should be included

The same standard interface can therefore support very different tasks while preserving a common operating method.

12.20 Writing an Effective Prompt

A useful Prompt generally contains:

Objective

What do you want created?

Context

What should the AI know?

Audience

Who is the output for?

Requirements

What must be included?

Tone

How should it sound?

Format

How should the answer be organized?

Constraints

What should it avoid or limit?

The more relevant information you provide, the less likely you are to need repeated generations.

12.21 Example — Weak Prompt

For Business Plan Generator:

Make a business plan.

The Tool can respond, but the AI has little context.

12.22 Example — Stronger Prompt

A more useful Prompt might be:

Create a business plan for a B2B SaaS company serving real estate sales teams with 10–100 agents. Include an executive summary, target market, competitive positioning, subscription revenue model, sales strategy, three-year growth assumptions, major operating risks, and implementation milestones. Write for potential investors and strategic partners.

This gives the Tool far more usable direction.

12.23 Entering Existing Content

Some standard Tools are designed for content you already have.

Examples include:

  1. Content Improver
  2. Code Reviewer
  3. Bug Fix
  4. Accessibility Checker
  5. CSV Analyzer

In these cases, paste the existing text, code, or data into the Input area and add relevant context.

For example, Content Improver's current placeholder says:

“Paste your content here to improve its clarity, flow, and engagement...”

12.24 Input Can Contain Multiple Lines

The shared Input field is a large text area with a minimum height designed for substantial instructions.

You can organize your Prompt with:

  1. Paragraphs
  2. Bullet-style instructions
  3. Data
  4. Code
  5. Requirements
  6. Examples

when appropriate for the Tool.

12.25 Generate Button

Below the Input field is:

Generate.

Select it when your Prompt is ready.

12.26 Generate Is Disabled When Input Is Empty

The standard Generate button is disabled when the Prompt contains no meaningful text.

Therefore, you must enter an instruction before the button becomes available.

12.27 Input Required

The generation handler also verifies that Input is not empty.

If an empty Prompt reaches the submission workflow, PROS SUITE displays:

Input required

with:

“Please enter a prompt to continue.”

12.28 Ctrl + Enter Keyboard Shortcut

The standard Prompt field supports:

Ctrl + Enter

to submit the current Prompt.

This can be faster than moving the pointer to the Generate button.

12.29 Current Shortcut Is Specifically Ctrl + Enter

The current source specifically checks the Ctrl key with Enter.

Therefore, this chapter documents:

Ctrl + Enter

rather than promising that Command + Enter on macOS behaves identically.

This is different from Global Search, which explicitly supports both Command and Ctrl with K.

12.30 Generate Begins the AI Request

When you submit the Prompt, the standard Tool sends:

  1. The Tool's AI instructions
  2. Your Prompt
  3. Current selected Model
  4. Tool identity

through the shared AI streaming workflow.

You do not need to configure these internal values manually.

12.31 The Tool Knows Its Purpose

The shared ToolPage gives the AI context identifying the Tool's:

  1. Name
  2. Description

before sending your Prompt.

This is why the same general workspace can support specialized tools such as:

  1. Business Plan Generator
  2. Code Reviewer
  3. Apology Drafter
  4. Competitor Analysis

while preserving the same Input and Output controls.

12.32 Generating State

Once generation begins, the Generate button changes to:

Generating...

with a loading indicator.

This indicates that the AI response is currently being produced.

12.33 Generate Is Disabled While Streaming

While the current result is streaming, the Generate button is disabled.

This helps prevent the same standard Tool from immediately launching another generation through the button while the current response is still arriving.

12.34 Allow Generation to Finish

When you see:

Generating...

allow the response to complete.

Avoid repeatedly trying to submit the same request.

Once streaming finishes, Generate becomes available again.

12.35 Output Section

The right side of the shared workspace is titled:

Output

with:

“Generated content will appear here”.

Before any content exists, the Output area displays:

“Your generated content will appear here.”

12.36 Output Streams While It Is Generated

The standard AI workflow does not necessarily wait for the entire response before displaying it.

As response text arrives, PROS SUITE appends it to the streamed Output.

This allows you to watch content appear progressively.

12.37 Streaming Indicator

While content is still arriving, the Output area displays animated activity indicators beneath the generated text.

When those indicators stop and Generate becomes available again, the streaming operation has finished.

12.38 Output Can Be Scrolled

The standard Output container has a defined maximum height and becomes scrollable when the generated content is longer than the visible area.

Scroll through the Output to review the complete response.

12.39 Markdown Rendering

The Output is processed through PROS SUITE's Markdown Renderer.

Depending on the AI response, this can provide structured presentation such as:

  1. Headings
  2. Lists
  3. Emphasis
  4. Code-style formatting
  5. Other supported Markdown structures

The exact formatting depends on the generated content.

12.40 Review the Entire Output

Do not rely only on the first visible portion.

For longer results:

  1. Allow generation to finish.
  2. Scroll through the entire response.
  3. Check for accuracy.
  4. Check whether all requested sections were included.
  5. Review names, numbers, claims, dates, and specialized content.
  6. Decide whether the result can be used, edited, or needs another generation.

12.41 AI Output Should Be Reviewed

Generated content should be treated as AI-assisted work that may require human review.

This is particularly important for:

  1. Legal content
  2. Financial content
  3. Health-related content
  4. Technical code
  5. Data interpretations
  6. Business projections
  7. Claims about external facts
  8. Client-facing materials

The Standard Generator creates the content; the user remains responsible for deciding whether it is appropriate for its intended use.

12.42 Copy Control

Once generated content exists, the Output header displays a Copy icon.

Select it to copy the current generated content to your device clipboard.

12.43 Copy Confirmation

After Copy is selected, PROS SUITE displays:

Copied!

with:

“Content copied to clipboard”.

The Copy icon also temporarily changes to a checkmark.

12.44 Copy Does Not Generate Again

Copy operates on the content already produced.

It does not submit another AI generation request.

Therefore, if you already have a useful result:

Copy it

rather than regenerating the same content solely to move it somewhere else.

12.45 Download Control

When generated content exists, the Output header also displays a Download icon.

Select it to download the generated result.

12.46 Standard Download Format

The shared Standard Generator downloads Output as a:

.txt text file.

The filename follows:

[toolId]-output.txt

For example, conceptually:

business-plan-output.txt

or:

content-improver-output.txt

depending on the Tool ID.

12.47 Download Does Not Generate Again

Like Copy, Download uses the content that already exists.

It does not initiate a fresh AI request.

12.48 Standard Download Is Not DOCX or PDF

The shared ToolPage specifically creates a plain-text .txt download.

Therefore, do not expect every Standard Generator to automatically export:

  1. PDF
  2. Microsoft Word
  3. PowerPoint
  4. Spreadsheet
  5. HTML

unless a specialized Tool explicitly supports those formats.

12.49 Save Important Output

Because the standard workspace does not establish universal project persistence, it is a good practice to:

  1. Copy useful results.
  2. Download important results.
  3. Move them into your appropriate business records or workflow.

Do this before assuming the Standard Generator maintains a permanent user history.

12.50 Example Prompts

Many Standard Generators provide:

Try these examples:

These sample prompts demonstrate the type and structure of requests appropriate for that Tool.

12.51 Example Prompts Vary by Tool

For A/B Test Copy Generator, examples include requests for:

  1. Headline variants
  2. CTA variations
  3. Email subject-line variants


For Business Plan Generator, examples include:

  1. Food delivery startup
  2. Tech consulting firm
  3. Sustainable fashion brand


The examples are Tool-specific.

12.52 Selecting an Example Prompt

When you select an example, PROS SUITE places that full sample Prompt into the Input field.

It does not immediately generate the result.

You can therefore:

  1. Select the example.
  2. Review it.
  3. Modify it.
  4. Add your own details.
  5. Then select Generate.

12.53 Example Buttons Show Shortened Text

The current interface displays only approximately the first 40 characters of each Example Prompt on its button followed by ....

Selecting the button loads the full underlying Prompt into Input.

12.54 Use Examples as Templates, Not Final Instructions

Example Prompts are most valuable as starting structures.

Instead of using:

Business plan for a food delivery startup

unchanged, customize it with:

  1. Business Name
  2. Market
  3. Geography
  4. Customer segment
  5. Business model
  6. Goals
  7. Differentiators
  8. Required sections

This usually produces a more relevant result.

12.55 Some Standard Tools May Have No Example Prompts

The shared workspace only displays Try these examples: when the Tool provides one or more Example Prompts.

If no examples appear, this does not indicate an error.

Enter your own Prompt normally.

12.56 Reset Control

Beside Generate is a Reset icon represented by a circular arrow.

The current Reset handler:

  1. Clears the Input state.
  2. Clears the separate local Output state.
  3. Returns keyboard focus to the Prompt field.


However, there is an important current-version behavior to understand.

12.57 Important Current Reset Behavior

The visible generated result in this Standard Generator is primarily displayed from a separate streamed result state.

The current Reset handler clears Input and the separate local Output value, but it does not clear that streamed result state.

Therefore, in the current source version:

Selecting Reset can clear the Prompt while the previously generated result remains visible in Output.

This is the actual behavior supported by the current source and is important to document accurately.

12.58 When the Previous Streamed Result Clears

At the beginning of a new AI streaming request, the shared streaming workflow explicitly clears its previous streamed text.

Therefore, the practical current workflow is:

Reset

→ Input clears

→ Previous Output may remain visible

Then:

Enter New Prompt → Generate

→ Previous streamed result clears

→ New result begins streaming

12.59 Do Not Use Reset as an Output-Erase Function

Because of the current behavior described above, do not rely on Reset to remove the last visible generated result from the screen.

Use Reset primarily to:

  1. Clear the current Prompt.
  2. Return focus to Input.
  3. Prepare for another request.

The next generation will replace the streamed Output.

12.60 Reset Does Not Cancel an Active Generation

The current shared ToolPage does not establish a Stop/Cancel generation function tied to the Reset control.

Reset changes the Input and local Output states; it does not cancel the active streaming request.

Therefore:

Do not use Reset as a Stop button while a response is generating.

Allow the current stream to finish.

12.61 No Universal Stop Generation Button

The current Standard Generator does not expose a user-facing:

Stop Generating

or:

Cancel Generation

button.

Once a standard generation has begun, allow it to complete.

Specialized Tools may have different controls.

12.62 Copy and Download Can Appear During Streaming

The Copy and Download controls become visible whenever some display content exists.

Because streamed content begins appearing before the generation completes, those controls can become available while the response is still being generated.

For a complete result, wait until generation finishes before Copying or Downloading.

12.63 Copying During Generation Can Copy a Partial Result

Because Copy uses the current streamed content, selecting Copy before generation completes can copy only the portion produced so far.

Recommended:

Wait for streaming to finish → Copy

12.64 Downloading During Generation Can Save a Partial Result

For the same reason, downloading while the AI is still streaming can save only the text available at that moment.

Recommended:

Wait for generation completion → Download

12.65 What Happens When You Generate Again

Submitting another Prompt causes the shared streaming system to:

  1. Enter streaming state.
  2. Clear the previous streamed text.
  3. Send the new request.
  4. Display the new result progressively.


Therefore, preserve a previous result before regenerating if you may need it later.

12.66 Save Before Regenerating

Before generating another version:

  1. Review the existing Output.
  2. Copy it if useful.
  3. Download it if important.
  4. Modify your Prompt.
  5. Generate again.

This is particularly important because the Standard Generator does not establish a universal prior-generation history panel.

12.67 No Universal Save Button

The shared Standard Generator does not provide a universal:

Save

button.

The verified standard Output actions are:

  1. Copy
  2. Download

Do not assume generated content is automatically added to a Saved Projects collection.

12.68 No Universal Generation History

The shared ToolPage does not establish a universal:

History

or:

Previous Generations

panel.

Some specialized PROS SUITE applications have histories, galleries, or projects, but those features are Tool-specific.

12.69 No Universal Duplicate Function

The Standard Generator does not provide:

Duplicate

for generated Output.

If you want another copy of the same result:

  1. Copy it.
  2. Download it.
  3. Store it externally.

Do not expect a universal Duplicate action.

12.70 No Universal Delete Function

There is also no general:

Delete Output

control in the shared workspace.

The Reset icon should not be described as a true stored-content Delete operation.

12.71 No Universal File Upload

The shared ToolPage itself contains a text-area Input and does not establish a universal file-upload control.

Some specialized Tools support:

  1. Images
  2. Files
  3. References
  4. CSV uploads
  5. Other media

but that is not a universal Standard Generator capability.

12.72 Text-Based Input Is the Standard Pattern

For the shared workspace, the core user input is text.

Depending on the Tool, you may paste:

  1. Instructions
  2. Existing prose
  3. Code
  4. Data
  5. CSV text
  6. Requirements
  7. Business information

into the Prompt field.

12.73 No Universal Rich-Text Editor

The standard Input is a Textarea rather than a full document editor.

Therefore, do not expect universal editing controls such as:

  1. Font selection
  2. Font size
  3. Bold toolbar
  4. Alignment
  5. Tables
  6. Page layout

inside the Input area.

The AI output can display structured Markdown, but the Prompt field itself remains a text-entry area.

12.74 Output Is Not an In-Place Document Editor

The standard Output is rendered for review.

The current shared workspace does not establish direct in-place editing of the generated result.

If you want the AI to change the result:

  1. Modify or replace the Input Prompt.
  2. Describe the desired revision.
  3. Generate again.

Alternatively, Copy or Download the result and edit it in another appropriate application.

12.75 Generation Error

If the standard Tool cannot complete the request, it displays:

Error

and either the specific returned error or:

“Failed to generate content. Please try again.”

Read the specific error before deciding what to change.

12.76 Shared AI Request Failure

If the AI request itself returns an error, the shared streaming system can report the specific service error or fall back to:

Failed to generate response.

Possible causes can include:

  1. Model problem
  2. Provider/API Key problem
  3. Token/balance issue
  4. Connection failure
  5. Application/service error

Use the specific message when available.

12.77 Browser Streaming Support

The current shared generator expects browser support for streamed responses.

If no readable response stream is available, the source can produce:

“ReadableStream not yet supported in this browser.”

If you encounter this:

  1. Update your browser.
  2. Try a current mainstream browser.
  3. Reload PROS SUITE.
  4. Retry the Tool.

12.78 User Balance Refresh After Generation

When the shared streaming workflow finishes—successfully or after an error—it requests a refresh of the user account state.

This allows the current Token Balance to be updated in the interface after supported operations.

12.79 Wait for Balance Refresh

After generation finishes, the Token Balance may update shortly afterward.

If you are performing multiple higher-cost generations:

  1. Wait for the current request to complete.
  2. Review the updated balance.
  3. Confirm you still have sufficient Tokens.
  4. Then generate again.

12.80 Selected Model Is Used by the Shared Generator

The shared streaming workflow sends the currently selected Model with the AI request.

Therefore, the Header's Model selection can affect Standard Generator behavior.

12.81 Provider API Keys Can Also Be Used

When user-configured provider credentials are available, the shared streaming workflow includes them with the supported AI request.

If the selected Model requires a credential and none is available, resolve that through:

Settings → API Keys

as explained in Chapter 11.

12.82 Recommended First Generation Workflow

For any Standard Generator:

Step 1

Open the Tool.

Step 2

Confirm its Name and Category.

Step 3

Read its Description.

Step 4

Review:

tokens per use

Step 5

Review:

Your balance

Step 6

Confirm the appropriate AI Model.

Step 7

Read the Prompt placeholder.

Step 8

Review Try these examples: if available.

Step 9

Enter a complete Prompt.

Step 10

Select Generate or press Ctrl + Enter.

Step 11

Wait for streaming to finish.

Step 12

Review the full Output.

Step 13

Copy or Download important content.

12.83 Recommended Revision Workflow

If the result is close but not correct:

  1. Save the current result if useful.
  2. Identify exactly what needs to change.
  3. Revise the Prompt with specific instructions.
  4. Keep useful context from the first request.
  5. Generate again.
  6. Compare the new Output.

Avoid vague instructions such as:

Make it better.

Prefer:

Rewrite this for a CFO audience, reduce it to 500 words, preserve the financial assumptions, add a five-point risk section, and make the tone more analytical.

12.84 Using the Standard Generator Efficiently

A strong operating sequence is:

Specific Tool


Specific Prompt


Appropriate Model


Enough Tokens

=

Higher Probability of Useful First Output

This reduces unnecessary generation cycles.

12.85 Example — Business Plan Generator

Navigate to:

Business → Business Plan

The Standard Generator currently identifies itself as:

Business Plan Generator

with:

“Create comprehensive business plans with executive summaries and financial projections.”

Its example Prompts currently include business-plan requests for a food-delivery startup, tech consulting firm, and sustainable fashion brand.

The operating method remains:

Input → Generate → Output → Copy/Download

12.86 Example — Code Reviewer

Navigate to:

Development → Code Review

The Tool's shared workspace asks the user to:

“Paste your code for review. Include context about what it should do...”

A useful Prompt could contain:

  1. The code
  2. Programming language
  3. Intended behavior
  4. Known issue
  5. Security concerns
  6. Performance concerns

Then generate the review.

12.87 Example — CSV Analyzer

Navigate to:

Data & Analytics → CSV Analyzer

The standard Tool currently instructs the user to paste CSV data and include headers.

A useful workflow is:

  1. Copy the relevant CSV data.
  2. Include the header row.
  3. Paste it into Input.
  4. Add the analytical question.
  5. Generate.
  6. Review the statistical/trend interpretation.

12.88 Example — Content Improver

Navigate to:

Writing → Content Improver

Paste existing content into Input and explain what should improve.

Its current examples include:

  1. Improving a paragraph
  2. Making an Email more professional
  3. Enhancing product description conversion copy


12.89 Example — A/B Test Copy

The current A/B Test Copy Generator provides examples for creating multiple:

  1. Headlines
  2. CTA buttons
  3. Email subject lines


Use the Prompt to identify:

  1. Current copy
  2. Audience
  3. Objective
  4. Number of variants
  5. What variable you are testing

12.90 Troubleshooting — Generate Button Is Disabled

Check whether:

  1. Input is empty.
  2. Generation is already streaming.

The button is disabled under either condition.

12.91 Troubleshooting — Input Required

If you receive:

Input required

“Please enter a prompt to continue.”

enter meaningful text into Input before submitting.

12.92 Troubleshooting — Ctrl + Enter Does Nothing as Expected

The current shared Tool specifically checks:

Ctrl + Enter.

If the shortcut is unavailable in your browser/environment:

Use the Generate button directly.

12.93 Troubleshooting — Previous Output Is Still Visible After Reset

This is explained by the current Reset implementation.

Reset clears the Prompt and local Output state, but the visible result is sourced from the separate streaming state, which Reset does not clear.

To begin new work:

  1. Enter the new Prompt.
  2. Generate.
  3. The streaming workflow clears the previous streamed result at the start of the new request.

12.94 Troubleshooting — Reset Did Not Stop Generation

Reset is not a Stop control.

The current Standard Generator does not expose a universal Stop-generation button.

Allow the active generation to finish.

12.95 Troubleshooting — Copied Output Is Incomplete

You may have selected Copy while generation was still streaming.

Wait until:

Generating...

finishes and the streaming indicator disappears.

Then select Copy again.

12.96 Troubleshooting — Downloaded File Is Incomplete

If Download was selected while the response was still being produced, the .txt file can contain only the content available at that moment.

Wait for completion and Download again.

12.97 Troubleshooting — Downloaded File Is Plain Text

This is expected.

The shared Standard Generator creates:

[toolId]-output.txt.

A .txt file is the standard shared export.

Specialized Tools can provide other formats.

12.98 Troubleshooting — Cannot Find a Saved Generation

The Standard Generator does not provide a universal Saved Generations area.

If you did not:

  1. Copy the result
  2. Download the result

or otherwise preserve it, do not assume it exists in a central project history.

Use Copy/Download for important Standard Generator outputs.

12.99 Troubleshooting — Model Not Available

If generation depends on a Model requiring provider credentials, use:

Settings → API Keys

and follow Chapter 11.

Do not repeatedly submit the Prompt without resolving the Model issue.

12.100 Troubleshooting — Insufficient Tokens

If the operation reports insufficient Tokens:

  1. Review Your balance.
  2. Review tokens per use.
  3. Check Monthly Tokens in the Sidebar.
  4. Resolve the balance before retrying.

Tool access, Model access, and Token availability are separate requirements.

12.101 Troubleshooting — Output Is Not What You Expected

Do not immediately assume the Tool failed.

Review your Prompt.

Ask:

  1. Did I state the objective?
  2. Did I identify the audience?
  3. Did I provide sufficient context?
  4. Did I specify format?
  5. Did I state constraints?
  6. Did I paste all necessary source information?
  7. Did I select the right Tool?

Then revise the Prompt and generate again if needed.

12.102 Troubleshooting — Result Stops During Streaming

If the stream terminates unexpectedly:

  1. Check your connection.
  2. Review any displayed error.
  3. Preserve whatever useful partial result exists.
  4. Confirm Token Balance.
  5. Confirm Model availability.
  6. Retry if appropriate.

If repeated failures occur across multiple Tools, use the appropriate AIUNIFY support process.

12.103 Best Practice — Choose the Most Specialized Standard Tool

Instead of using a general Tool for everything:

Business Plan

→ Business Plan Generator

Contract

→ Contract Generator

Competitor Research

→ Competitor Analysis

LinkedIn Content

→ LinkedIn Tool

Code Review

→ Code Reviewer

Using the specialized Tool provides the AI with more task-specific context.

12.104 Best Practice — Read the Placeholder

The Tool-specific placeholder often tells you exactly what input will improve the result.

Before typing, read it.

This small step can significantly improve Prompt quality.

12.105 Best Practice — Customize Example Prompts

Do not treat an Example Prompt as finished business input.

Select it and add:

  1. Your Name/company
  2. Customer segment
  3. Product
  4. Geography
  5. Desired tone
  6. Required length
  7. Required deliverables
  8. Constraints

Then Generate.

12.106 Best Practice — Save Good Results Before Regenerating

Because there is no universal generation history:

Good Output → Copy or Download → Then Regenerate

This is safer than assuming you can recover the old version later.

12.107 Best Practice — Wait Before Copying or Downloading

For complete results:

Generating...

Streaming finishes

Review

Copy / Download

This avoids preserving partial content.

12.108 Best Practice — Use Tokens Intentionally

Before another generation, decide whether you actually need:

  1. A completely different result
  2. A revised Prompt
  3. A manual edit
  4. A specialized Tool

Repeatedly generating without changing the instructions wastes usage without necessarily improving the output.

12.109 Best Practice — Verify High-Stakes Output

AI-generated content can sound authoritative even when it requires correction.

Before consequential use, verify:

  1. Legal language
  2. Financial assumptions
  3. Health information
  4. Technical configuration
  5. Numerical calculations
  6. External facts
  7. Compliance claims

Use qualified professional review where appropriate.

12.110 Best Practice — Keep Sensitive Information Appropriate

Do not paste secrets into a Standard Generator unless the business workflow explicitly requires and authorizes that handling.

Avoid unnecessary inclusion of:

  1. Passwords
  2. API Keys
  3. Private access credentials
  4. Highly sensitive personal information

Give the AI only the context necessary for the task.

12.111 Standard Generator Operating Checklist

Before generation:

  1. I am signed in.
  2. I opened the correct Tool.
  3. I confirmed the Tool Name.
  4. I reviewed its Category.
  5. I read the Tool Description.
  6. I reviewed tokens per use.
  7. I reviewed Your balance.
  8. I confirmed the appropriate Model.
  9. I read the Tool-specific placeholder.
  10. I reviewed Example Prompts if available.
  11. I entered a complete Prompt.
  12. I am ready to consume the applicable Tokens.

During generation:

  1. I see Generating...
  2. I understand the Output is streaming.
  3. I am not repeatedly clicking Generate.
  4. I am waiting for the response to finish.
  5. I understand Copy/Download during streaming may capture partial content.

After generation:

  1. I reviewed the entire Output.
  2. I checked factual or high-stakes content where necessary.
  3. I copied important content.
  4. I downloaded important content when appropriate.
  5. I saved useful content before regenerating.
  6. I checked Token Balance before repeated usage.

12.112 What Is Universal in the Standard Workspace

For Tools actually using the shared ToolPage, the source establishes these common elements:

Header

  1. Tool Name
  2. Category
  3. Description

Usage

  1. Tokens per use
  2. Your balance

Input

  1. Prompt Textarea
  2. Generate
  3. Ctrl + Enter
  4. Reset
  5. Optional Example Prompts

Output

  1. Streaming content
  2. Markdown rendering
  3. Copy
  4. Download as .txt

Errors

  1. Input required
  2. Generation errors

12.113 What Is Not Universal

The standard ToolPage does not establish universal:

  1. Saved Projects
  2. Generation History
  3. Save
  4. Duplicate
  5. Delete
  6. File uploads
  7. Rich-text editing
  8. DOCX export
  9. PDF export
  10. PowerPoint export
  11. Direct in-place Output editing
  12. Stop Generation
  13. Version history
  14. Shared folders
  15. Team collaboration

Do not expect these functions merely because another specialized PROS SUITE Tool provides them.

12.114 Standard Generator at a Glance

The shared workspace can be understood as:

TOOL HEADER

Tool Name

Category

Description

USAGE

Tokens Per Use

Current Balance

INPUT

Describe What You Want to Generate

Optional:

Try These Examples

GENERATE

or:

Ctrl + Enter

GENERATING...

STREAMED OUTPUT

REVIEW

Choose:

COPY

or:

DOWNLOAD .TXT

If revision needed:

MODIFY PROMPT → GENERATE AGAIN

12.115 Chapter Summary

The Standard AI Generator Workspace is one of the most reusable operating patterns in AIUNIFY PROS SUITE.

The current source contains 77 pages invoking the shared ToolPage component, demonstrating its use across many functional categories.

Each shared ToolPage presents:

  1. Tool Name
  2. Category
  3. Description
  4. Current Token cost
  5. Token Balance
  6. Input
  7. Tool-specific Prompt placeholder
  8. Generate
  9. Ctrl + Enter submission
  10. Reset
  11. Optional Example Prompts
  12. Output
  13. Streaming AI response
  14. Copy
  15. .txt Download

Generation requires meaningful Input. If an empty request reaches submission, PROS SUITE displays:

Input required

“Please enter a prompt to continue.”

While a response is being generated, the button displays:

Generating...

and the AI text streams progressively into Output.

Generated content can be copied or downloaded as:

[toolId]-output.txt.

One important current-version behavior is that the Reset action clears Input and the component's local Output value but does not clear the separate streamed result that controls the visible AI Output. As a result, the last generated result can remain visible after Reset until another generation begins. The next streaming request clears the previous streamed text before producing the new response.

The most effective operating sequence is:

Choose the Correct Tool → Review Cost and Balance → Select the Appropriate Model → Give Complete Instructions → Generate → Wait for Streaming to Finish → Review → Copy/Download Important Output → Revise Only When Necessary

Once this workflow is understood, dozens of AIUNIFY PROS SUITE generators can be operated using the same familiar process.

Write Your Comment