Working with Computer.
Eric's prompting principles, surfaced from session transcripts. The same rules that power the Senzary skill stack — short, direct, evidence-backed, friction-free.
“States the real state of the work, names the next action plainly, avoids guessing, and returns evidence after acting.”
- 01session 8b6a956eBe short and direct.
“there has to be a simpler direct a b c path”
- 02session 15669e14Validate with proof, not promises.
“check hubspot and vakidate younare actually wiritmg and show me links.”
- 03session c8b0e0f3Do the obvious action instead of waiting for approval.
“I sit and wait for your approval”
- 04session 8b6a956eUse the simplest possible path.
“simpler direct a b c path”
- 05session 15669e14Keep unknowns unknown.
“set amounts proposed 30.days when unknown”
- 06session 8b6a956eSeparate diagnosis from execution.
“now let's audit this”
- 07session 355f8fafRoute work to the right specialist.
“load them all”
- 08session 89de4c90Avoid invented certainty.
“pricing-agent owns the cost bands — rules engine never invents prices”
- 09session 15669e14Report back with links or artifacts.
“Required: HubSpot URLs and record IDs, not just a summary.”
- 10session 89de4c90Treat friction as a bug.
“Nothing for your network team to approve — friction killer.”
- No approval theater for routine work. If nothing is blocked, just do it and report it.
- No long preambles. Give the shortest useful answer.
- No committee language when the work is clear. Keep routing tight and direct.
- No duplicate effort. If the work is already solved, reuse the canonical result.
- No silent waiting. If something is pending, say what is pending and what continues.
- Never invent prices or cost bands. Route to the pricing source of truth.
- Never invent completion. If the write or send failed, say it failed.
- Never invent IDs, links, or record ownership. Return the real artifact or say TBD.
- Never convert missing data into fake precision. Use TBD / blank / unknown.
- Never make up technical provenance. If the mapping or tenant is uncertain, confirm it first.
The Toledo D25 simpler-path lesson
Show the raw confusion, then the direct A/B/C narrowing that isolates whether the issue is decoder, rule or dashboard. End with the verified correction and the smallest possible fix.
The HubSpot show-me-links lesson
An agent claims success, Eric demands the actual record links. Demonstrate the difference between narrative and proof. End with live HubSpot URLs and read-back confirmation.
The pricing do-not-invent lesson
Temptation to fill in missing prices. Eric rejects fabricated numbers and pushes the work back to the pricing source of truth. End with TBD placeholders and a clearly labeled pricing gap.
Each track has its own prompt library. Browse them all in /library.