Documentation & Help
Install guides, usage docs, troubleshooting and FAQs for every PeaBox Lab project — from AI Workbench to local-first editors.
Open the docs →Guides, reusable prompts, researched product ideas and hands-on use cases — the four knowledge bases PeaBox Lab maintains alongside the code.
Install guides, usage docs, troubleshooting and FAQs for every PeaBox Lab project — from AI Workbench to local-first editors.
Open the docs →
1,000 structured, placeholder-driven AI prompts across 75 categories. Search, filter, open any prompt and copy it into your assistant.
Browse 1,000 prompts →
100 product-ready software ideas with problem framing, MVP scope, architecture — plus target audience, market worth, revenue and business models.
Explore 100 ideas →Fifty-four problems you hit at work, school or in your side project — and the exact repo that solves each one. Every card links to the project so you can start straight away.
You want chat-style help at your desk but you do not want your work files wandering into someone else’s cloud. The Workbench lets you run local models with Ollama and keep everything on the laptop you already own.
Read more →
Every team has that one question: which model is actually better for this job? Stop guessing and test it yourself.
Read more →
You close the laptop lid, reopen it, and the whole conversation thread is gone. That is annoying when you spent twenty minutes setting context.
Read more →
You record an hour-long client interview and now you need the one sentence about pricing. Scrubbing through audio is painful.
Read more →
You have a 40-page brief on your screen and two hours on the train. Your eyes are done but your voice assistant is not.
Read more →
Your training video exists but half your team learns in a second language. Captions are not optional.
Read more →
You sit in front of a blank chat box hoping something comes to mind. It rarely does.
Read more →
You want consistent reviews but every reviewer asks the same questions differently. Consistency is the win.
Read more →
Bookmarked chats are graveyards of good intentions. A catalog beats a folder of dead links.
Read more →
Your spreadsheet is forty columns wide and the question you have is nothing to do with SQL. You just want an answer.
Read more →
Sales has one file. Support has another. Nobody knows how they relate. You have a meeting in an hour.
Read more →
The exec summary keeps changing after the meeting because someone's pivot table moved. That is a trust problem.
Read more →
You need every page of a 90-page agreement to carry the same header and footer. Copy-paste is not a strategy.
Read more →
Drafts fly around with your logo missing or a previous client's name showing through. Small mistake, big awkwardness.
Read more →
The payroll file needs to go to finance. It should not be readable by everyone on the drive.
Read more →
Some of your projects live in folders on a network drive with no internet access. Browser IDEs do not help there.
Read more →
The model wrote 200 lines and they all look right. They are not always right.
Read more →
New hire opens a 3,000-line file and asks you why this function exists. You do not remember either.
Read more →
Product wants a demo Friday. Engineering has three months. The gap is the prototype.
Read more →
Your data got too big for pandas and stakeholders want the same dashboards in Fabric. Same code shape, new engine.
Read more →
You know exactly what you want to release, but remembering the right git incantations at 1am is a coin toss.
Read more →
Your build works locally, breaks in CI, and nobody can see which .env entry is missing or misspelled.
Read more →
A one-line indent change in the deploy manifest took the whole staging cluster offline last month. Never again.
Read more →
You have three months and no roadmap. The good opportunities are sitting in someone else's notebook.
Read more →
The client sends a ZIP with a 400-character folder name. Windows refuses to open it. Deadline is today.
Read more →
Notes apps come and go. Your research should not disappear with them.
Read more →
Your to-dos live in five different apps and none of them sync with each other.
Read more →
You shot 40 photos. You need 10 for Instagram, 4 for the story, 3 for the blog header.
Read more →
Your client says "the vibe is everywhere but the greens arent them" and hands you a picture as reference.
Read more →
Rename 500 files, parse a log, rename a folder of screenshots. Python is overkill for that.
Read more →
Students bounce off curly braces and semicolons before they learn to think like a programmer.
Read more →
Banking systems run on COBOL. Nobody on your team has read one in anger. Migration starts next quarter.
Read more →
The client wants a WCAG-AA report before the site goes live. You have two days and 200 pages.
Read more →
Your audit says "colour contrast is bad". That is not actionable. Engineers need exact element-level fixes.
Read more →
The model sounds confident. Half of what it says is made up. You need a way to check the claims, not just skim them.
Read more →
You save whitepapers and articles into a folder and forget them. Later you cannot find the one with the risk tables.
Read more →
Forty weeks of 1:1s, sprint reviews and vendor calls. You need the themes, and nobody on the team wants to read them.
Read more →
Episode goes live Friday. You need show notes with timestamps and three quotable lines before the host reviews it.
Read more →
You recorded every lecture. Now exams are three weeks away and the recordings are useless for revision.
Read more →
A whole folder of drafts went out without the CONFIDENTIAL banner. You catch it three days later.
Read more →
Your draft has your name, internal path, and three edits from last month in its metadata. The client does not need any of that.
Read more →
Your launch report says average response time is fine, but one 6-second outlier is quietly wrecking your SLA.
Read more →
Leadership wants a chart by lunch. Your BI platform needs three approvals and a ticket you do not want to file.
Read more →
There is a 200-character regex in the auth module that nobody wants to touch. The new hire inherited it.
Read more →
You refactored a hot path. Tests are green. You still do not trust yourself, and the reviewer feels the same way.
Read more →
The build fails on one runner, passes on three others, and the logs might as well be in another language.
Read more →
A config PR says 'just a version bump'. You know better by now — config drift is never just a bump.
Read more →
You pushed to the release branch instead of feature by accident. The release is tomorrow morning.
Read more →
You want to build something real this month but the launch is three idea-dumps away every time.
Read more →
The gallery wants prints by Thursday. You shot for JPEG social, not for a wall six feet wide.
Read more →
Your note app shut down with three years of research inside it. The export is a directory of .md files.
Read more →
The batch process runs at 3am and ops wants to know why. The answer lives in 12,000 lines of COBOL.
Read more →
QA fixed the contrast issues and closed the ticket. But did the fixes actually land? Nobody wants to crawl the site again by hand.
Read more →
You have five minutes and a completely blank prompt. Something needs to appear before the meeting.
Read more →