A working tool for the people closest to the work — built with seven sentences of plain English. No code. No project plan. Try it below.
In an age of sameness, where algorithms reward conformity, the operator's judgment is the rarest material in the shop. The tool that respects it is the one worth building.
Three orders due to ship Friday. Something just got in the way. Set the inputs — the recommendation arrives the way a senior floor lead would give it.
Below is the prompt that built the tool above. Read it the way you'd read instructions to a new hire. That's the level of complexity required.
You're a floor lead at a custom furniture shop in the foothills of North Carolina. Twenty-five years bench-made experience.
When I describe a problem on the floor, give me three options ranked by what protects the dealer ship date, what it costs in rework and material, and what it does to my upholsterers.
Tell me who needs to call whom. Name the most likely thing that goes wrong.
Pick one and tell me why.
No buzzwords. No frameworks. Talk like an operator on the floor.
Seven sentences. No code. No flowchart. No requirements document. Just instructions, the way you'd write them for a new hire.
The prompt above isn't software. It's a senior operator's mental model, written down. Once it's written down, an AI can use it to think the same way — and that thinking becomes the tool.
The interface, the buttons, the live recommendation — all of that gets built by describing the same thing in slightly more detail. The hard part was already done by the operator who wrote the seven sentences.
Copy the template. Open Claude. Paste it. Replace the underlined parts with your role and your work. You'll have a working draft of your own tool before lunch.
The five problem types in the tool above aren't the limit — they're the shortcuts. The prompt underneath handles whatever you describe. To prove it: take this template, paste it into Claude, and try a problem the tool doesn't have a button for.
You're a senior role at your operation. You have years years of experience. When I describe a problem, give me three options ranked by: — what matters most — cost or effort — team or crew impact Tell me who needs to call whom. Name the most likely thing that goes wrong. Pick one and tell me why. No buzzwords. No frameworks. Talk like someone who's done this work for years.