# Ten complete visual prompts

Copy one full prompt, including its official source. The labels are format cues, not installed commands. The included graphics are reviewed examples, not guaranteed one-shot outputs.

## 1. Visual cheat sheet

```text
/visualcheatsheet

Create a visual cheat sheet for California halibut and striped bass in the San Francisco Bay District using the CDFW source below. Preserve daily bag versus possession wording, minimum total length, geographic scope, the striped-bass gear restriction, and the source update date. Keep the two halibut species distinct. Limit this example to these two species; do not label it a complete fishing guide or invent an identification drawing. Include a visible reminder to check current location, gear, licensing, protected-area and advisory rules.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://wildlife.ca.gov/Fishing/Ocean/Regulations/Fishing-Map/sf-bay
Audience: Residents and public-facing information teams
```

## 2. Decision tree

```text
/decisiontree

Create a decision tree from TSA's liquids rule. Route medication or infant/child nourishment and potentially qualifying inbound duty-free purchases to their official exception guidance first. For ordinary liquids, distinguish containers up to 3.4 oz / 100 mL from larger containers, and show the quart-size bag requirement. Do not call a small container automatically approved: other item restrictions and security screening still apply. Do not invent exception eligibility or substitute a volume remaining in the bottle for the container limit.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.tsa.gov/travel/security-screening/liquids-aerosols-gels-rule
Audience: Travelers and staff explaining public instructions
```

## 3. Process map

```text
/processmap

Create a process map of the USAJOBS application journey using the current OPM help article. Group steps into six readable stages, but preserve the handoff from USAJOBS to the hiring agency's application system and the need to check receipt. Distinguish applicant actions from later agency review and possible interview/selection. Do not imply searching requires an account, autosaving equals submission, or an interview/offer is guaranteed. Do not invent hiring durations.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://usajobshelp.opm.gov/hc/en-us/articles/52846644688019-How-does-the-application-process-work
Audience: Federal applicants and staff explaining application steps
```

## 4. Comparison cards

```text
/comparisoncards

Create three comparison cards explaining NWS watch, advisory and warning definitions. Compare what the term means and what kind of response the official description calls for. Preserve the uncertainty in a watch and the fact that advisory conditions can still be dangerous. Do not depict a mandatory watch-to-advisory-to-warning progression, reuse one hazard's numerical thresholds for others, or produce a live forecast. Use labels and distinct icons as well as color.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.weather.gov/sjt/WatchWarningAdvisoryExplained
Audience: Residents, communications teams and facility staff
```

## 5. Timeline

```text
/timelineview

Create a vertical timeline from California DOF's general budget timetable with five landmarks: January 10, May 14, June 15, late June, and July 1. Use the source's meaning for each. Distinguish a specified deadline from an approximate publication window and from the fiscal-year start. Mark spacing as schematic, not to scale. Do not invent a universal June 30 signing deadline, imply actual completion in a particular year, or omit the need to consult the full timetable.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://dof.ca.gov/budget/general-budget-timetable/
Audience: State staff, program managers and interested residents
```

## 6. Mind map

```text
/mindmap

Create a mind map of selected Ready.gov emergency kit items using six editorial categories: water/food, light/power, information, health, hygiene and household needs. Label the categories as your organization, not FEMA's official taxonomy. Preserve the water quantity and duration wording. Include a family/pet-needs branch and a reminder to consult the complete list and maintain the kit. Do not claim a small selection is a complete kit or add medical dosages or utility-shutoff instructions.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.ready.gov/kit
Audience: Households and preparedness communicators
```

## 7. Annotated system diagram

```text
/annotateddiagram

Create an annotated conceptual diagram of the common drinking-water treatment stages described by CDC: coagulation, flocculation, sedimentation, filtration and disinfection. Give each a short role label and a distinct simple schematic. Clearly state that actual treatment differs by source water and community. Do not invent plant equipment, dimensions, chemical quantities, engineering accuracy, or guarantees that these stages remove every contaminant. Label the drawing conceptual and not to scale.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.cdc.gov/drinking-water/about/how-water-treatment-works.html
Audience: Public works educators and curious residents
```

## 8. Instructional storyboard

```text
/storyboard

Create a three-panel educational storyboard showing Drop, Cover and Hold On for an indoor person able to get under a desk/table, grounded in the USGS source. Show the person under the desk/table and holding it, not running outside. Keep the scope label visible and include the source warning about windows/heavy furniture and rushing outside/downstairs during shaking. Do not generalize this scenario to driving, outdoors, coastal hazards or every access need. Use simple schematic figures rather than falsely precise safety equipment drawings.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.usgs.gov/faqs/what-should-i-do-during-earthquake
Audience: Preparedness trainers and public information teams
```

## 9. Swimlane diagram

```text
/swimlane

Create a swimlane diagram of FDA's general notice-and-comment route with lanes for FDA, the public, and publication/submission channels. Distinguish Federal Register publication from Regulations.gov commenting. Show proposal, public input, agency review and the possible outcomes: final rule, new proposal or ending the process. Do not invent a fixed comment period, promise a particular outcome, imply every comment receives an individual reply, or describe every type of rulemaking as identical.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.fda.gov/regulatory-information/fda-rules-and-regulations
Audience: Policy staff, community groups and public-facing teams
```

## 10. Visual glossary

```text
/visualglossary

Create a visual glossary of hypocenter, epicenter, magnitude and intensity using the USGS explanation. Use a schematic cross-section showing the hypocenter underground and the epicenter directly above it on the surface. Separate earthquake size from location-specific shaking. Do not put the hypocenter on the surface, label intensity as a single value for the entire event, add an unverified risk map, or imply an earthquake prediction. Include a text equivalent for the diagram.

Read the official source below before designing. If you cannot open it, ask me to paste the relevant text; do not guess. Show the page date if available and your retrieval date. Use only supported facts and clearly label scope, exceptions, uncertainty and editorial groupings. Treat the slash label as a format request, not an assumed built-in command. Use a clean fine-line editorial style, readable type, ample spacing and labels that do not rely on color alone. Produce the actual visual if your tools support it; otherwise provide an explicitly labeled layout specification. Include the official link, concise alt text, a complete text equivalent and a fact-check list. Do not invent an agency seal, endorsement or product screenshot.

Official source: https://www.usgs.gov/programs/earthquake-hazards/science-earthquakes
Audience: Science communicators, educators and residents
```