Prompt Workshop: Better Inputs, Better Outputs, Less Robot Fog
Welcome to AI Tools → Prompts — the Fyrbloc place for sharing useful prompts, improving messy prompts, testing AI workflows, comparing outputs, and turning vague instructions into something that does not come back sounding like a robot trapped inside a business seminar.
Prompts are not magic spells.
Although, to be fair, some of them do look like:
You are an expert world-class strategic innovation assistant...
Please sit down, wizard.
A good prompt is simply a clear instruction with enough context, limits, examples, and purpose.
Better input usually means better output.
Bad input usually means the AI confidently produces a shiny bowl of fog.
What belongs here?
Use AI Tools → Prompts for topics like:
- Useful prompts
- Prompt templates
- Prompt testing
- Prompt improvement
- Writing prompts
- Coding prompts
- Design prompts
- Research prompts
- Marketing prompts
- SEO prompts
- Image prompts
- Video prompts
- Music prompts
- Game dev prompts
- Business idea prompts
- Debugging prompts
- Workflow prompts
- Prompt comparisons
- “Why did the AI answer like a confused brochure?” problems
If the main topic is how to ask AI for better output, it belongs here.
If the main topic is a specific AI app, use the closest AI tool tag too.
If the prompt controls a real workflow, mention the tool, model, purpose, and what you tested.
Prompt sharing template
Copy this when sharing a prompt:
Prompt name:
What it is for:
Tool/model used:
The prompt:
Example input:
Example output summary:
What worked well:
What needs improving:
Best used for:
Warnings/limits:
Example:
Prompt name:
Clear Bug Report Builder
What it is for:
Turning messy bug notes into a clean support post.
Tool/model used:
ChatGPT / Claude / Gemini / other
The prompt:
Turn my messy notes into a clear bug report using this format:
What I am trying to do:
What happened:
What I expected:
Error message:
What I already tried:
What I need help with:
Example input:
My Laravel form saves sometimes but not always and I think validation is weird.
Example output summary:
The AI turned it into a structured bug report with clearer sections.
What worked well:
It made the issue easier to explain.
What needs improving:
It still needed exact errors and code added manually.
Best used for:
Quick Help, Support, Web Dev posts.
Warnings/limits:
It cannot guess missing logs, version numbers, or real error messages.
That is a useful prompt post.
It shows the prompt, the use case, and the limits.
No mystery smoke.
What makes a good prompt?
A good prompt usually includes:
Role
Goal
Context
Output format
Constraints
Examples
Tone/style
What to avoid
What to ask if unclear
Example:
Role:
Act as a practical web development helper.
Goal:
Help me diagnose a Flarum error.
Context:
I use CloudPanel, PHP 8.4, Flarum 2.x, and Nginx.
Output format:
Give me likely causes, checks, and commands.
Constraints:
Do not suggest reinstalling first.
Do not expose private info.
Ask for logs if needed.
My error:
[paste error here]
That gives the AI a proper job.
Not just:
Fix my site.
That prompt is a tiny panic note.
The AI may still try.
But it will be guessing in a helmet.
The simple prompt formula
Use this:
I want you to help me with:
[task]
Context:
[project, tool, audience, platform, problem]
Output I want:
[format]
Rules:
[limits, style, what to avoid]
Here is the input:
[paste text/code/idea]
Example:
I want you to help me with:
Writing a website launch post.
Context:
The site is a builder community for people creating websites, apps, tools, games, scripts, brands, and AI workflows.
Output I want:
A forum post with title, intro, template, checklist, and fun tone.
Rules:
Keep it clear, useful, and not too corporate.
Use markdown.
Do not make fake claims.
Here is the input:
Fyrbloc.com is live and I want feedback.
That will usually work better than:
Write launch thing.
Although “write launch thing” has a certain exhausted charm.
Prompt types welcome here
Writing prompts
Good for:
Forum posts
Product descriptions
Landing page copy
FAQs
Emails
Policies
Guides
Tutorials
Community posts
Example prompt:
Rewrite this post so it is clearer, friendlier, and easier to scan.
Keep the meaning.
Use headings and short sections.
Do not make it sound corporate.
Useful.
Simple.
No giant wizard paragraph needed.
Coding prompts
Good for:
Debugging
Explaining code
Refactoring
Writing small snippets
Creating checklists
Understanding errors
Comparing approaches
Example prompt:
Explain this error like I am a beginner, then give me the safest next checks.
Do not suggest destructive commands.
Ask me for missing version numbers or logs if needed.
Error:
[paste error]
Important: AI-generated code must be checked.
The terminal does not care that the prompt had confidence.
Design prompts
Good for:
Logo directions
UI ideas
Colour palettes
Landing page layout
Brand tone
Image prompts
Thumbnail ideas
Mockup descriptions
Example prompt:
Give me 5 distinct visual directions for a builder community website.
Each direction should include mood, colours, typography, layout style, and what kind of audience it fits.
Avoid generic SaaS design language.
Good design prompts ask for directions, not just “make it nice.”
“Nice” is not a design brief.
It is a wish with shoes.
Research prompts
Good for:
Comparing tools
Planning content
Creating checklists
Learning topics
Summarising notes
Finding pros/cons
Building decision tables
Example prompt:
Compare these tools for a beginner building a forum.
Create a table with price, difficulty, strengths, weaknesses, and best use case.
If facts may be current, tell me what needs checking online.
Good research prompts should request caution.
AI can sound certain while being wrong.
Very stylishly wrong.
Bad prompts vs better prompts
Bad
Make my website better.
Better
Review this homepage copy for a builder community.
Focus on:
- clarity
- target audience
- main call-to-action
- what feels confusing
- what to improve first
Do not rewrite everything unless needed.
Homepage copy:
[paste copy]
Bad
Write SEO.
Better
Create an SEO title, meta description, H1, and 5 FAQ questions for this page.
Audience:
Indie builders and creators.
Page topic:
Useful free tools for launching websites.
Rules:
Keep title under 60 characters.
Keep meta description under 155 characters.
Avoid keyword stuffing.
Bad
Fix code.
Better
Help me debug this JavaScript.
Explain the likely issue first.
Then show a corrected version.
Do not change unrelated parts.
Expected:
Menu opens when button is clicked.
Actual:
Console says "Cannot read properties of null".
Code:
[paste code]
Better prompts give the AI a target.
Bad prompts hand it a fog machine and hope for architecture.
Prompt improvement request
Use this when your prompt is not working:
Prompt I used:
Tool/model:
What I wanted:
What output I got:
What was wrong with the output:
What I want changed:
Any limits:
Example:
Prompt I used:
Write a product description for my app.
Tool/model:
ChatGPT
What I wanted:
Clear, simple copy for a small launch page.
What output I got:
Very corporate and full of buzzwords.
What was wrong with the output:
It sounded fake and too polished.
What I want changed:
Make it more direct, human, and practical.
Any limits:
No fake claims. No “revolutionary” wording.
That helps people improve the prompt instead of guessing.
Prompt debugging is still debugging.
Just with fewer semicolons and more emotional branding problems.
Useful prompt blocks
Add these to prompts when needed.
Ask for questions first
If important information is missing, ask me up to 5 questions before giving the final answer.
Keep it practical
Give practical steps, not theory.
Avoid fake claims
Do not invent facts, results, testimonials, prices, or proof.
Make it scannable
Use headings, short paragraphs, and clear bullet points.
Keep code safe
Do not suggest destructive commands unless you explain the risk and provide a safer alternative.
Preserve meaning
Improve the wording but keep the original meaning, tone, and intent.
Make options distinct
Give 5 options that are genuinely different from each other, not small variations of the same idea.
That last one is important.
AI loves giving five versions of the same sentence wearing different hats.
Prompt safety rules
Do not share prompts that encourage:
Spam
Scams
Phishing
Malware
Fake reviews
Fake testimonials
Impersonation
Private data extraction
Credential theft
Bypassing security
Copyright copying
Harassment
Misleading marketplace claims
AI is a tool.
Do not use it to make the forum worse, louder, faker, or more suspicious.
Fyrbloc likes useful AI.
Fyrbloc does not like robot-powered nonsense.
The forge is for building.
Not manufacturing spam goblins.
AI output still needs checking
Before using AI output, check:
Is it accurate?
Is it current?
Is it safe?
Is it too generic?
Is it too confident?
Does it fit the audience?
Does it invent facts?
Does it need sources?
Does it preserve the meaning?
Does it sound like you?
AI can draft.
You still decide.
Do not let AI publish something you would not stand behind.
Especially technical commands.
A wrong sentence is annoying.
A wrong terminal command can become a full afternoon.
Possibly a full evening.
Possibly tea and regret.
Good prompt post titles
Use clear titles like:
Prompt: Turn Messy Bug Notes Into a Clean Help Request
Prompt: Generate Better Landing Page Feedback Questions
Prompt: Create Daily Build Log Updates From Rough Notes
Prompt: Improve Product Descriptions Without Sounding Corporate
Prompt: Explain Composer Errors for Beginners
Avoid:
Best prompt ever
Use this
AI prompt
Secret prompt
If it is truly a good prompt, explain what it does.
No mystery cloak required.
Good replies in prompt threads
Helpful replies:
This works better if you add the target audience.
Add an output format so the response is easier to use.
The prompt is good, but it should warn the AI not to invent facts.
I tested this with a bug report and it gave a cleaner result.
Try adding an example input and example output.
Less useful replies:
AI is bad.
This prompt is magic.
Guaranteed results.
Just use my secret method.
No.
Explain.
Test.
Improve.
No wizard smoke.
Prompt checklist
Before posting a prompt, check:
Did I explain what the prompt is for?
Did I include the actual prompt?
Did I include the tool/model if relevant?
Did I show example input if useful?
Did I explain what output it gives?
Did I mention limits or warnings?
Did I remove private information?
Did I avoid fake claims?
Did I test it or say it is untested?
That is enough.
A useful prompt post should help other builders actually use it.
Not just admire it from a distance like a strange digital sculpture.
Quick prompt starter format
Use this:
Prompt name:
Use case:
Prompt:
Best for:
Tested with:
Result:
Limit:
Example:
Prompt name:
Build Log Cleaner
Use case:
Turning rough daily notes into a readable build log post.
Prompt:
Rewrite these rough notes into a clear build log update.
Use this format:
Project:
What changed:
What broke:
What I learned:
Next step:
Keep the tone practical and slightly fun.
Do not invent progress.
Best for:
Daily progress posts.
Tested with:
Messy project notes.
Result:
Made the update easier to read.
Limit:
Needs real details from the builder.
Clean.
Useful.
Very postable.
Final note
Prompts are not about tricking AI.
They are about giving clear direction.
The better you explain the task, context, limits, and desired output, the better the result usually gets.
Share prompts that save time.
Improve prompts that produce fog.
Test outputs before trusting them.
Do not post spammy “secret formula” nonsense.
Good prompt in.
Better output out.
Usually.
Build. Prompt. Check. Edit. Ship.
