How to Build a Day-Hike Packing List from Trail Facts
Packing lists invent rain gear. Items only from trail facts and Own.
The matching generator is the Day-Hike Packing List from Trail Facts (No Invented Weather or Permits) (Day Hike Packing List From Trail Facts No Invented Weather Or Permits) 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 distance, water, and permit lines first
Build a day-hike packing list from pasted trail facts. Never invent weather, permits, distances, or water sources. 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:
Trail facts (name, distance if any, elevation if any, water notes, permit notes): [Facts]
Party size I lock (or UNKNOWN): [Party]
Gear I already own (exact list or NONE): [Own]
Words I must not use: [Banned]
What I must never invent: [Never]
Output format: [Format]
Language: [Lang]
Max items: [Max]
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.
Do not require rain gear when weather is blank
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: Facts items, Party status, Own status, Lang, Max. Forbidden: invented weather, permits, mileage.
- Fact map: distance/elevation/water/permit present or NOT IN INPUTS.
- Pack list: up to Max items. Each item tagged worn/carried and mapped to a Fact or Own. If weather NOT IN INPUTS, do not add rain gear as required.
- Water note: quote Facts; if none, water source NOT IN INPUTS.
- Refuse list: invented NOAA forecast, invented permit numbers, invented mileage, invented prices.
- Diff notes: Banned/Never cuts.
- Not-advice banner: not medical advice; not a permit office; not a weather forecast.
- Compliance pass: Banned/Never hits. Item count vs Max. Gaps list of five. 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 invented mileage and springs
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:
- Packing list from Facts + Own only. Not a shop and not a forecast.
- Never invent weather, permits, distances, or water sources.
- Stay at or under Max items.
- 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.
Keep the not-a-forecast banner
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 (day hike packing list, no invented weather, trail facts packing) 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.