How to Build a Seasonal Home Maintenance Checklist from Climate Zone
Checklists rot when they invent IRC cites and carbon monoxide ppm as law. Zone and Systems were enough. Leave codes out.
The matching generator is the Home Maintenance Seasonal Checklist from Climate Zone (No Invented Codes) 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).
Name every system before a season column
Build a seasonal home maintenance checklist from a climate zone and systems list. No invented building codes or contractor licenses. 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:
Climate zone or region label I may use: [Zone]
Home systems and ages I can prove: [Systems]
Seasons or months to cover: [Seasons]
Tools I already own (or NONE): [Tools]
Pro tasks I already scheduled (or NONE): [Pros]
Words I must not use: [Banned]
What I must never invent: [Never]
Priority hazards I care about (user-stated only): [Hazards]
Output format: [Format]
Skip list: [Skip]
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.
DIY only when Tools cover it
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: Zone, Systems, Seasons, Tools, Pros, Hazards, Skip. Forbidden: codes, permits, licenses not in Inputs.
- Season grid: one column per Seasons entry.
- Task list tied to Systems only. If a system is missing, skip that task.
- DIY vs pro: DIY only if Tools cover it; else mark hire and only name Pros if given.
- Hazard emphasis only for Hazards the user stated.
- Banner: not an inspection, not code advice, not a permit guide.
- Gaps: systems ages missing, unknown filters.
- Compliance pass: cut Banned and Never. 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.
Hazard emphasis only for user-stated risks
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:
- Seasonal checklist from Zone and Systems. Not a code inspection.
- Never invent building codes, permits, or licenses.
- Do not invent HVAC model numbers.
- Honor Skip.
- 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.
Not an inspection and not permit advice
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 (seasonal home maintenance checklist, climate zone home checklist, no invented building codes) 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.