How to Build a Motorcycle Maintenance Log from a Parts List
Motorcycle logs invent 12 Nm and a $28 oil filter. The list named glazed brake pads and an air filter. Chain NOT IN INPUTS. Viscosity not added.
The matching generator is the Motorcycle Maintenance Log from a Parts List (No Invented Torque Specs or Prices) (Motorcycle Maintenance Log From A Parts List No Invented Torque Specs Or Prices) prompt. Browse related cards in the PromptDig library (Browse more prompts). When a filled run survives, share the version you actually use (Share a prompt).
Map each named part to KEEP
Build a motorcycle maintenance log from a parts list. No invented torque specs, prices, or service intervals. Start by filling Inputs, not by asking the model to remember last week's run. If a field is blank, write NONE or NOT IN INPUTS and leave it blank through Generate. The card is built so the model cannot honestly invent a number, owner, URL, or command that you did not paste.
Paste these fields before you hit run:
Parts list I lock (parts, conditions, miles I may quote): [Parts]
Bike I lock (or UNKNOWN): [Bike]
Interval units I lock (or UNKNOWN): [Units]
Words I must not use: [Banned]
What I must never invent (torque Nm, prices, extra parts, recalls, oil viscosity): [Never]
Output format: [Format]
Language: [Lang]
Last service date I lock (or UNKNOWN): [Last]
That inventory is the honesty ledger. Anything that does not appear there is forbidden in the draft. If you catch yourself adding a nice-to-have after the run, you are no longer using the card. You are ghostwriting. Put the extra fact in Inputs and run again.
One row per part in the list
Generate is numbered on purpose. Do not skip a step because the first paragraph looked done. The early steps exist to stop later prose from smuggling claims.
Walk the Generate list in order:
- Honesty ledger: Parts nouns, Bike, Units, Last, Lang. Forbidden: invented torque, prices, extra parts, recalls, oil viscosity.
- Part map: each Parts item to KEEP. Parts not listed stay leftover OTHER.
- Log: one row per Parts item. Condition quote or CONDITION UNKNOWN. Torque NOT IN INPUTS unless Parts named a number.
- Units: quote Units or write UNITS UNKNOWN. Do not mint a 3000 mile oil interval.
- Refuse list: bicycle chain logs, car oil-change calendars, shop quotes, NHTSA recalls, invented Nm values.
- Bike and Last: quote or write UNKNOWN.
- Never: do not write 12 Nm. Do not invent a $28 oil filter. Do not add a chain if Parts omitted it. Do not invent 10W-40.
- Compliance pass: quote Banned and Never hits. Cut them. Format as Format.
If a step asks for a version lock, quote the version from Inputs in the output. If a step asks for a refuse list, keep the refuse list in the published artifact, not in a sidebar you delete. Reviewers should see what the model was not allowed to do.
Refuse torque specs and bicycle chain dumps
Most failures are the same shape: a missing field gets a confident fill. A conversion rate appears. A Gradle task appears. A flash point appears. A caption appears on a job that asked for slide text only. Your review is to search the draft for numbers, names, and commands, then grep Inputs. No match means cut.
Honor the constraints as hard stops, not vibes:
- Motorcycle maintenance log from Parts only. Not a bicycle log and not a quote.
- Never invent torque specs, prices, or extra parts.
- Intervals only if pasted.
- No emojis.
When the card says not legal advice, not certification, not an exam dump, or not a caption engine, that sentence belongs at the top of the output. Deleting it to look more finished is how you inherit risk.
Leave intervals blank when the list omitted them
Finish with the compliance pass the prompt already asks for. Quote the banned-word hits. Cut them. Print character counts when the job has a cap. Print word counts when the job has a budget. List gaps as gaps. Five missing facts are more useful than one smooth paragraph.
Tags on the card (motorcycle maintenance log, parts list lock, no invented torque or prices) are a reminder of the job shape, not an invitation to wander into a neighboring cluster. If you need a different surface, open a different PromptDig card rather than stretching this one.
Fill the card, then run
Replace every bracket. Run on ChatGPT, Claude, or Gemini. Read the ledger first, then the artifact. If the model invents a commit, KPI, DOI, PEL, bid, or logo, discard the run. Tighten Inputs. Run again. Share the filled card that survived, not the first draft that sounded done.