Prompt Library

30 ChatGPT Prompts for Hiking Routes, Packs and Trip Reports

30 copy-paste prompts

Paste your trail, pack and forecast notes. Get route cards, checklists and trip reports back. This is not medical advice. Check weather, closures and permits on official park or forest pages.

In short: This page contains 30 copy-paste ready prompts, organized into 6 categories with a description and pro tip for each. The first 5 prompts are free instantly, no signup needed. Drafted with AI writing assistance and checked against our editorial policy.

Louis Corneloup
By Louis Corneloup · Founder, Techpresso
Last updated ·Drafted with AI assistance (how we make prompts)

Route Planning

5 prompts

Two Day Hikes Compared

1/30

✨ What it does

Produces a six-row comparison of two day hikes plus an 80-word pick. Print the table and ink the real miles from your map into any blank cell.

Compare [TRAIL A] and [TRAIL B] as day hikes for my group of [GROUP SIZE] starting at [TRAILHEAD]. Notes I already have: [ROUTE NOTES]. Make a table with exactly 6 rows labelled Distance from my notes, Elevation gain from my notes, Water I named, Bailout I named, Car shuttle needed, and Best fit for this group. Then write 80 words picking one route and why it fits this group. Keep table cells under 12 words. Do not invent mileage, elevation gain, water reliability or closure status. If a cell has no number or name in my notes, write [VERIFY] and name the official map or ranger page I should check.

💡

Pro tip: Paste real mile and gain figures from your printed map, not a memory of last year.

Shuttle Car Six Step Plan

2/30

✨ What it does

Produces a 6-step car shuttle plan plus a 40-word risk line. Check drive times and gate hours on the park road page before you leave a car.

I need a numbered 6-step car shuttle plan for an end-to-end hike from [START TRAILHEAD] to [END TRAILHEAD]. Vehicles: [VEHICLE NOTES]. Timing I already know: [DRIVE TIMES]. Latest return: [LATEST RETURN TIME]. Cover who leaves which car, where keys live, the last phone check, and the latest return. Keep each step under 25 words. Output the 6 steps plus a 40-word risk line. Never invent road closures, gate hours or drive minutes. If I did not give a drive time or a cell-coverage note, tag it [VERIFY] and tell me to check the park road page myself.

💡

Pro tip: Write which pocket holds each key. Lost keys at a far trailhead wreck the day.

First Trail Five Questions

3/30

✨ What it does

Asks five questions first, then offers two trail types and a 100-word starter plan. If a trail name appears, open the land manager site and match it yourself.

Interview me before you plan. Context I already wrote: [SEASON AND REGION]. Ask exactly 5 questions, one at a time, then wait for each answer. Ask about: my current fitness in my own words, the longest hike I finished in the last year, the season and region I named, whether I need a loop from one car, and any permit or dog rule I already know. After I answer all five, pick the 2 trail types that fit from loop, out and back, or lollipop, and write a 100-word starter plan for the first type. Do not invent named trails, distances or permit rules. Any trail name or quota I did not type must read [VERIFY] with a pointer to the land manager site. No fitness or medical clearance advice. If I mention an injury, tell me to ask a doctor or physio.

💡

Pro tip: Answer with a real last hike, including how long you were on your feet.

Three Bailout Options

4/30

✨ What it does

Gives three bailout options in a table, then picks one in 60 words for your group. Trace the chosen exit on paper so a blank junction never surprises you.

Here is my planned route: [ROUTE DESCRIPTION]. Known exits: [KNOWN EXITS]. Group: [GROUP NOTES]. Give 3 bailout options as a table with columns Option, Where we leave the ridge or trail, Who this fits, and What I still must check. Then pick one option in 60 words and say why it fits this group. Keep the whole answer under 220 words. If an exit is not in my notes, write [VERIFY] instead of inventing a spur, road or ranger station. Do not invent trail junctions that I never named.

💡

Pro tip: Name every spur and road you already know, even rough ones. Empty notes make empty exits.

Day Hike Route Card

5/30

✨ What it does

Fills an eight-field route card from your notes, one line per field. Ink a map or ranger number into every blank before you leave the car.

Build a one-page route card by filling this template from my notes only. Notes: [ROUTE NOTES]. Template fields in this order: Trailhead, Planned start, Turnaround time, Planned return, Key junctions (max 5), Water stops I named, Emergency exit I named, Ranger phone I pasted. Output the filled card, one line per field. Missing fields must say [VERIFY], not a guess. Do not invent junctions, water, phone numbers or times. Closures stay blank until I paste an official alert.

💡

Pro tip: Put the turnaround time in 24-hour clock so nobody argues at the saddle.

Pack and Gear

5 prompts

Overnight Pack Table

6/30

✨ What it does

Builds a 10-row overnight pack table plus 3 leave-at-home lines from gear you already own. Weigh the pack yourself and confirm bear or fire rules on the official camping page.

Sort an overnight pack table for [TRIP LENGTH] on [TRAIL NAME] in [SEASON]. What I already own: [GEAR I OWN]. Constraints I set: [WEIGHT OR VOLUME LIMIT], [BEAR OR WATER RULE I KNOW]. Output a table of 10 packed rows with columns Item, Why it is on this trip, Packed in (pack body, lid or pocket). Then 3 lines of items from my list I leave at home, each with a reason. Mark a needed item I do not own as [VERIFY]. Use only items from my list. Do not invent pack weights, bear-canister rules or stove fuel amounts. Point fire and camping rules to the land manager page I must check.

💡

Pro tip: List pocket locations. A filter in the lid is faster to reach than one buried in the food bag.

Pack List Scored Rewrite

7/30

✨ What it does

Scores your pack list on layers, water and sleep, then rewrites it as 12 grouped bullets. Fill tagged specs from the tag on your own gear before you cut weight.

Read my pack list: [PACK LIST]. Trip: [TRIP NOTES]. Score the list out of 10 on three lines: weather layers I named, water carry I named, and night system I named. Then rewrite the list as 12 bullets grouped by wear, eat, sleep and emergency. Flag any weight, temperature rating or water volume I did not give as [VERIFY]. Do not invent gear specs, temperature ratings or items I never owned. This is gear organisation, not medical advice and not a treatment list. Leave first-aid contents as I wrote them.

💡

Pro tip: Paste the temperature rating printed on your bag tag, not a guess from a shop recap.

Tent Versus Tarp Night

8/30

✨ What it does

Compares two shelters in a four-row table, then picks one in 70 words. Read the camping page yourself if a site still needs a permit check.

Compare sleeping in [SHELTER A] versus [SHELTER B] for [NIGHT COUNT] on [ROUTE]. My notes: [WEATHER AND SITE NOTES]. Make a table with 4 rows: Packed size from my notes, Storm plan I described, Leave-no-trace notes I gave, and What I still need from the ranger. Then write 70 words on which shelter to take. Do not invent packed weights, wind ratings or campsite rules. If a site is permit-only and I did not confirm it, write [VERIFY] and name the official camping page I should read.

💡

Pro tip: Say whether you have tree anchors or only stakes. A tarp needs those details.

Water Carry Five Steps

9/30

✨ What it does

Turns logged springs into a 5-step water carry under 180 words. Call the ranger about any source tagged seasonal before you count on it.

I need a 5-step water plan for hiking with known sources: [WATER SOURCES I LOGGED]. Carry limit: [BOTTLE AND BLADDER VOLUME]. Treatment I already use: [TREATMENT METHOD]. Number the steps from fill at the trailhead to the last named source. Each step: where I fill, how much I carry, and a 10-word reminder. Keep the whole plan under 180 words. If a source is seasonal or I did not log it this year, write [VERIFY] and tell me to call the ranger station. Never invent a spring, cache or flow. Miles I did not type stay blank.

💡

Pro tip: Log each source with the month you last saw it flowing. Old trip reports lie in late summer.

Resupply Box Pack Partner

10/30

✨ What it does

Builds a 9-line resupply box list plus a 40-word car-leave note from food and fuel you already named. Confirm hold hours with the post office or ranger yourself.

Act as my hiking partner who only packs what I already listed. Resupply box for [DAY RANGE] on [ROUTE]: food I bought [FOOD LIST], fuel I have [FUEL NOTE], maps I have [MAP LIST]. Output a 9-line packing list for the box plus a 40-word note on what stays in the car. Do not invent calories, fuel burn or mail-drop rules. If a post office hold or ranger cache is not in my notes, tag it [VERIFY]. Keep each line under 18 words.

💡

Pro tip: Name the exact meals in the box. Vague food lists hide a night with nothing hot.

Pace and Timing

5 prompts

Six Block Day Clock

11/30

✨ What it does

Splits your day into six clock blocks whose rest minutes match the total you planned. Time any tagged split on a local walk before you trust it on the ridge.

Here is my day: start [START TIME] at [TRAILHEAD], goal [TURNAROUND POINT], latest safe turnaround [TURNAROUND TIME]. Pace notes: [PACE NOTES]. Break the day into 6 time blocks in a table with columns Clock time, Where I should be if my notes hold, Rest minutes, and Check. Total rest minutes across the table must equal [REST MINUTES I PLANNED] and no other number. Do not invent distances or split times. Missing splits get [VERIFY] and a note to time that section on a local walk first. This is not medical advice. If I mention pain or altitude illness, tell me to talk to a clinician and stop the plan.

💡

Pro tip: Use a 24-hour start time and a hard turnaround, not a wish to see the summit.

Overnight Pace Interview

12/30

✨ What it does

Asks five pace questions, then writes a 150-word overnight plan with start, lunch and camp windows. Look up sunset and camp miles on the park page, then set dinner from those numbers.

I need an overnight pace plan. Context already on the page: pack [PACK WEIGHT], group [GROUP], date [DATE], camp [CAMP]. Pose 5 questions one by one and wait after each: typical moving hours I can do, how that pack feels after two hours, whether anyone in the group is slower, how dark I expect that date, and whether that camp is booked or only planned. Then write a 150-word overnight pace plan with a start, a lunch sit, and a camp arrival window. Do not invent sunset times, camp mile markers or booking status. Sunset and camp distance I did not give must be [VERIFY] against the park page or a printed map. No fitness or medical clearance advice. If I mention an injury, tell me to ask a doctor or physio.

💡

Pro tip: Say who is slow in minutes per mile in your own words, not with a fitness label.

Turnaround Time Card

13/30

✨ What it does

Fills a 6-line turnaround card plus a 40-word group script. Set any missing clock time from official sunset or gate hours, not from the chat.

Fill this turnaround card from my notes: [DAY NOTES]. Fields: Latest time I leave [HIGH POINT], Reason (daylight, weather window I named, or group energy I named), Rally phrase I will say, Backup if we miss it, Who holds the watch, and Where we wait. Output the card as 6 short lines, then a 40-word script I can read to the group at the trailhead. Do not invent a clock time. If I omitted the time, write [VERIFY] and tell me to set it from the official sunset or gate hour I look up, not from a guess.

💡

Pro tip: Pick one person to hold the watch. A group with three clocks still argues.

Three Heat Pace Options

14/30

✨ What it does

Offers three heat-day pace options in a table and picks one in 50 words. Paste an official forecast before you treat any weather cell as real.

Give 3 pace options for hiking [ROUTE] when my forecast notes say [HEAT NOTES]. Group: [GROUP NOTES]. Layers I already own: [LAYER LIST]. Options table with columns Start time I could use, Break pattern, Clothing from my list, and Who this fits. Then pick one option in 50 words. Keep the whole answer under 200 words. Do not invent heat index numbers or cooling treatments. If I did not paste a forecast from an official source, tag the weather cells [VERIFY] and tell me to paste park or weather-service notes. This is not medical advice.

💡

Pro tip: Name the lightest shirt you actually own. The model cannot pack a shirt you do not have.

Pace Plan for Slower Partner

15/30

✨ What it does

Rewrites your pace plan in 120 words plus 5 cuts so a slower partner still hits the same turnaround. If a cut names a junction you did not, stay on the original line until you see it on the map.

Rewrite my pace plan for a partner who moves at [SLOWER PACE NOTES]. Original plan: [ORIGINAL PLAN]. Keep the same trail and the same [TURNAROUND TIME]. Output a 120-word version plus 5 bullets of what we drop or shorten. Do not invent a new mileage. Any cut that needs a junction I did not name gets [VERIFY]. No diagnosis of why they are slower. Stay on time, snacks I already packed, and route only.

💡

Pro tip: Give their pace in minutes per mile from a recent walk together, not a guess.

Like these prompts? There are full tutorials behind them.

Learn the workflows, not just the prompts. Easy-to-follow tutorials inside AI Academy, and the library keeps growing.

Try AI Academy Free

Weather and Conditions

5 prompts

Pre-Hike Weather Tick List

16/30

✨ What it does

Builds a 10-item yes or no weather and closure checklist with a source blank on each line. Tick items only from park alerts and weather-service notes you pasted.

List a 10-item checklist of questions I should answer from official notes before I leave for [TRAIL] on [DATE]. My current notes: [FORECAST NOTES]. Each item is a yes or no I must tick, with a blank for the source (park alert, weather service, avalanche center, or ranger). Keep items under 15 words. Cover wind on the ridge, precipitation, thunderstorm timing, fire closure, and seasonal road status only as questions, not as facts. Do not invent alerts, fire closures, wind numbers or avalanche ratings. Any item I cannot tick from my paste gets [VERIFY] and the name of the official page type to open.

💡

Pro tip: Paste the park alert text, not a summary from a group chat.

Stream Crossing From Signs

17/30

✨ What it does

Turns what you see at a ford into 6 problem bullets and 80 words of wait, walk-around, and cross signs from your notes. You decide on the bank; the chat never says go.

My crossing at [CROSSING NAME] looks like this: [WHAT I SEE]. Time: [TIME]. Recent weather I logged: [WEATHER LOG]. Group: [GROUP]. Walk through likely problems with this ford in 6 bullets covering depth, speed, debris, time of day, group skill I described, and the far-bank exit I can see. Then in 80 words name the signs in my notes that argue for waiting or walking around, and the signs that argue for crossing. The call is mine, made on site. Never say go. Do not invent depth, flow or a mapped alternate. If I did not name an alternate, write [VERIFY] and tell me to check the ranger or a printed map. This is not medical advice. If someone is already in trouble, say to follow my trained plan, not this chat.

💡

Pro tip: Describe the far bank and the sound of the water. Vague 'looks high' notes are hard to use.

Two Forecast Pastes Compared

18/30

✨ What it does

Puts two forecast pastes in a five-row table and names what disagrees in 60 words. Where the two pastes disagree, keep both lines and look them up on the weather service.

Compare forecast paste A: [FORECAST A] with paste B: [FORECAST B] for [TRAIL] on [DATE]. Make a table with 5 rows: Precipitation, Wind at ridgeline if stated, Temperature window, Thunderstorm timing if stated, and What disagrees. Then write a 60-word note on what I should recheck with the park or weather service before I go. Do not invent a merged forecast. Disagreements and missing fields are [VERIFY], not a blend you smooth over.

💡

Pro tip: Paste the full text of both forecasts, including the issued time at the top.

Ridgeline Exposure Table

19/30

✨ What it does

Maps seven route segments into an exposure table from your own cover and wind notes. A blank tree-line cell means you stay off that saddle until the forest alert fills it.

Turn my map notes [MAP NOTES] into a 7-row table for [ROUTE] with columns Segment, Tree cover I described, Wind I expect from my notes, Lightning plan I already wrote, and Time I hope to be off it. Keep cells under 12 words. Order rows from the trailhead up to the highest saddle I named. Do not invent tree line elevation or storm timing. Missing tree line or a closure must read [VERIFY] for the park or forest alert page.

💡

Pro tip: Name each segment by a cairn, saddle or switchback you can see on the map.

Go No Go Notes Review

20/30

✨ What it does

Scores your go or no-go draft on four lines and rewrites a 100-word decision. Screenshot it only after you replace tagged claims with text from an official alert.

Read my go or no-go notes: [GO NO GO DRAFT]. Trip: [TRIP]. Score 1 to 5 on four lines: weather source named, closure source named, group readiness in my words, and bailout named. Then rewrite as a 100-word decision I can screenshot. Do not invent a closure or a weather number. Ungrounded claims become [VERIFY] with the official source type to check (park alert, forest order, avalanche center, or ranger).

💡

Pro tip: Name the exact alert you read, including the date on it.

Permits and Comms

5 prompts

Permit Ranger Worksheet

21/30

✨ What it does

Fills an 8-line permit worksheet plus two ranger questions from facts you already have. Call or open the land manager site for any quota line that is still blank.

Draft an 8-line permit worksheet for [PARK OR FOREST] on [TRIP DATES]. What I already know: [PERMIT NOTES]. Lines in this order: Permit name I was told, Quota or walk-up note I was told, Group size, Entry trailhead, Exit, Nights, Vehicle rule I was told, and Phone or portal I was given. Then add 50 words on the two questions I should still ask a ranger. Do not invent quotas, walk-up rules or portal names. Missing official facts are [VERIFY]. I will look them up on the land manager site, not in this chat.

💡

Pro tip: Copy the permit name exactly as the park wrote it, including the wilderness name.

Two Minute Trailhead Brief

22/30

✨ What it does

Writes a 260-word trailhead briefing you can read in about two minutes. Insert tagged ranger numbers from the park page before you gather the group.

Act as the trip leader for a day hike. Group: [GROUP LIST]. Route: [ROUTE]. Known rules: [RULES I KNOW]. Water and food: [WATER AND FOOD PLAN]. Weather: [WEATHER NOTES]. Turnaround: [TURNAROUND TIME]. Write a trailhead briefing of about 260 words (about two minutes spoken) in this order: names and jobs taken only from [GROUP LIST], route and [TURNAROUND TIME], water and food from my plan, weather from my notes, and how we call for help with [EMERGENCY PLAN]. Do not invent ranger numbers, cell coverage or closure status. Missing official facts get [VERIFY]. This is not medical advice. Do not add first-aid treatment steps I did not already write.

💡

Pro tip: Assign jobs by first name from your list: maps, sweep, and timekeeper.

Plan for a Non Hiker Contact

23/30

✨ What it does

Rewrites your plan into 120 words plus a 6-line card a non-hiker can follow. Fill tagged phone and gate fields from your own contacts and the park page.

Rewrite my hike plan so a non-hiker [EMERGENCY CONTACT ROLE] can use it. Plan: [PLAN]. Include car location, type only (for example trailhead lot): [CAR LOCATION TYPE], latest check-in time, who to call if I miss it ([WHO TO CALL]), and what not to do. Output 120 words plus a 6-line leave-behind card. Do not invent a phone number, a gate hour or a street. Missing numbers are [VERIFY]. No medical instructions. Do not tell them to diagnose me if I am late.

💡

Pro tip: Use a trailhead name, not a street, unless you want that street on the leave-behind card.

Group Gear Share Split

24/30

✨ What it does

Splits shared group gear into a table of owner, proposed carrier and spare, up to 8 items. Confirm each owner against who packed the item, then agree the carrier.

Build a gear-share split for [TRIP]. People: [GROUP LIST]. Shared items with owner if known: [SHARED GEAR LIST AND OWNERS]. Weight notes: [WEIGHT NOTES]. Output a table with columns Item, Owner from my list, Proposed carrier from [GROUP LIST], Spare carrier. One row per shared item, up to 8 rows. Then 4 bullets naming which gear types each person keeps personal, taken only from [WEIGHT NOTES], else [VERIFY]. Do not invent who owns a stove, filter or map. If an item has no owner in my list, write [VERIFY] and ask me who packed it. Keep cells under 10 words. Names come only from [GROUP LIST].

💡

Pro tip: Name the stove, filter and map as separate lines. One lump called group kit hides who is overloaded.

Three Camp Picks From My List

25/30

✨ What it does

Picks among three camps you already named, with a table and a 60-word choice. Confirm tagged permit or bear rules on the official camping page before you hike to a site.

Here are camps I am allowed to consider from my notes: [CAMP OPTIONS]. Water I logged: [WATER]. Permit status I know: [PERMIT STATUS]. Group: [GROUP]. Give 3 options in a table with columns Camp, Walk from last water, Wind or tree cover I described, and Fit for this group. Then pick one in 60 words. Do not invent a site, a quota or a bear rule. Unknown permit status is [VERIFY] on the official camping page. Stay inside the list I gave.

💡

Pro tip: Only list camps the park already allows. Extra named sites in the chat are still not legal.

Go from copy-pasting to actually mastering AI.

AI Academy: hands-on tutorials on ChatGPT, Claude, Midjourney, and many other tools. New tutorials are added regularly.

Start Your Free Trial

After the Hike

5 prompts

Club Trip Report From Notes

26/30

✨ What it does

Turns field notes into a 180-word club trip report plus 5 missing-fact bullets. Add miles only from your own track log, then send.

Turn my field notes into a 180-word trip report others on my club list can use. Notes: [FIELD NOTES]. Party label: [PARTY LABEL]. Structure: When and where, Conditions I saw, Water I found or did not, Wildlife I noted without exact locations of nests, and What I would repeat. Then add 5 bullets of facts still missing. Do not invent miles, dates or animal counts. Gaps are [VERIFY]. Do not name other people beyond the party label I gave.

💡

Pro tip: Leave nest sites vague. Exact wildlife pins do not belong on a club list.

Trip Report Privacy Edit

27/30

✨ What it does

Scores your trip report on usefulness and privacy, then rewrites 150 words with private details removed. Confirm tagged miles on your track before you post.

Score my trip report draft, then rewrite it. Draft: [REPORT DRAFT]. Score 1 to 5 on three lines: condition facts a future hiker can use, honest gaps, and leftover private details (names, plates, exact camps of others). Then rewrite in 150 words with private details removed. Do not invent a condition I did not write. Unsourced miles or dates become [VERIFY]. Keep my tone, just strip what should stay off a public list.

💡

Pro tip: Search the draft for first names and plate fragments before you paste it here.

Next Season Condition Log

28/30

✨ What it does

Builds a six-row next-season log with what you saw, the month, and a source to recheck. Open that source next year before you pack for snow or bugs.

Build a 6-row condition log I can reuse next [SEASON] for [TRAIL]. My notes this time: [THIS TRIP NOTES]. Rows: Snow or mud, Water, Bugs, Crowds, Trail surface, Closures or wildlife. Columns: What I saw, Month, Source to recheck. One row per theme, not per mile. Do not invent a snow line or a flow. Empty cells are [VERIFY] for next year's check on the park alert page.

💡

Pro tip: Write the month you hiked. Bug and snow notes without a month mislead you next year.

After Action Five Questions

29/30

✨ What it does

Asks five after-hike questions, then writes a 140-word memo with 6 changes for next time. Change next year's route only after the printed map agrees with each blank.

Walk me through [TRIP] after we are home. Ask 5 questions, pausing after each: what felt too long, what gear I never used, a junction that confused me, a weather surprise, and who I would take next time. Then write a 140-word change-next-time memo with 6 bullets. Do not invent gear I did not mention or a trail fact I did not confirm. Missing map facts are [VERIFY]. Keep names to first names I typed.

💡

Pro tip: Name the one item you carried and never touched. That is the first cut next time.

Six Weekend Approach Walks

30/30

✨ What it does

Lays out six weekend walks from trails you already named, using your time, pack weight and weekly-increase numbers. Read any blank distance from your own track, then walk it.

Plan six weekend walks that only use trails I already named: [LOCAL TRAILS I USE, WITH DISTANCES IF KNOWN], building toward [GOAL HIKE] with goal stats I supplied: [GOAL STATS]. Numbers I set: longest walk now [CURRENT LONGEST WALK TIME], pack now [PACK WEIGHT NOW], goal pack [GOAL PACK WEIGHT], max weekly increase I use [MAX WEEKLY INCREASE IN TIME AND PACK WEIGHT]. Arrange my numbers into a 6-week ramp, never above my maximum. Output a table with columns Week (1 to 6), Walk I pick from my list, Time on feet from my numbers, Pack weight from my numbers, Distance from my track, else [VERIFY]. After the table, add a 40-word note. Do not invent distances. If a walk's distance is missing, write [VERIFY] and tell me to read it from my own past track or a printed map. This is not medical advice. I decide if a walk is too much.

💡

Pro tip: Give the goal hike's miles and gain from your map. Empty goal stats make an empty table.

Free tool

Prompt Optimizer

Turn a rough idea into a structured, professional AI prompt.

Try it free →

Frequently Asked Questions

No. Paste park or forest alerts you already copied. Most prompts tag missing closure and permit facts so you check the land manager page, not a chat.
No. They are not medical advice. They help you organise gear and timing from your notes. Injury, altitude and clearance questions belong with a doctor or physio.
Use first names or initials for your own party. Leave out full names, plates and street addresses.
Only trust miles and gain you typed. Anything marked for checking should be confirmed on a printed map or the park page before you go.
Yes. Paste each person's pace in their own words and a shared turnaround time. Do not ask the model to judge fitness or health.

Prompts are the starting line. Tutorials are the finish.

A growing library of hands-on tutorials on ChatGPT, Claude, Midjourney, and many other AI tools. New tutorials are added regularly.

7-day free trial. Cancel anytime.