Building a family road trip packing list is always difficult — you need to cover everything for your stay, plus everything to keep the kids occupied on the drive. You always end up forgetting something; you hope it's not the stuffy the baby needs to sleep.

With kids of different age groups, you have to pack different things; a 2-year-old and a 6-year-old need different clothes, toys, snacks, and you know the rest. There are tons of packing lists out there for any place you want to go, for any time of the year. The difference is that these lists aren't geared toward your family. They don't know if your kids have allergies or what kind of car you have.

Claude Projects can give you access to a "memory" of what you have, what medications you need to take with you, and what kind of car you have, so that you can pack appropriately. You'll add some basic instructions, and Claude Projects will use them every time you need to plan a road trip.

What you'll need

Step 1 – Create your Road Trip Planner Project

Download the Claude Desktop app, and go to Cowork. We'll need to create a new project; we'll start from scratch. Then name your project something like "Family Trip Planner." That's the basic setup for the entire project.

The key here is knowing that every time you start a chat session with Claude in this project folder, it will follow the instructions you've given it. This way, you update the instructions to reflect how your family changes or who is going on the trip, with specific details.

Step 2 – Write Your Family's Instructions

You should see a sidebar item called instructions. This is where we will write the instructions on how the project plans a trip. Here are a few things I've included in my instructions:

Kids' Ages: The age difference between a 2-year-old and a 6-year-old isn't just a few items. The 2-year-old still uses sleepers and needs a sound machine, while the 6-year-old goes through clothes so fast because they love to play in the mud.

Allergies or Medications: You never want to forget your medication or that you left the Allegra on the table counter while the windows are open during pollen season. These have their own category, so you can never forget them.

Your Car: Packing a sedan vs an SUV is two totally different things. If you have a roof rack, that opens up a ton more possibilities for what you can bring with you.

Your Gear: This category ropes in the stuff you already have. For each trip, you might need to purchase something specific for the destination you're going to. It's helpful if Claude already knows what you own, so it doesn't suggest purchases you should make.

Where You Stay: Do you typically camp? Maybe you have a cabin, or you're staying with a friend when you're going somewhere else. Maybe you stay in hotels or Airbnbs. Depending on where you stay, you need different things.

Output Format: How do you want Claude to format the list? Do you need different headers, or would you like to group things in a specific way?

Here is a template you can use:

You are a family road trip packing assistant. Here is our family's permanent context:

Kids: [age] and [age]

Allergies/medications: [list, or "none"]

Car: [type — e.g. Honda Pilot SUV, roof rack yes/no]

Gear we already own: [e.g., Yeti cooler, kids' Fire tablets, Hatch sound machine, Osprey toddler carrier, road trip game kit]

We usually stay in: [Airbnbs / hotels/campsites — pick the most common]

When I describe a trip, generate a packing list with:

- A "Don't Forget" section at the top for medications and allergy items

- Sections: Clothes (broken down per person), Car Kit, Entertainment, Snacks, First Aid, Hiking/Activity Gear, Documents

- Checkbox format throughout

- Flag any item I'd need to buy with ★ (assume I own everything listed in my gear above)

- Assume mountain nights are cold unless I say otherwise

Fill in your family's details and paste them into the project instructions. You're done with setup. The more details, the better. Giving Claude more context around your family helps plan these trips better.

Step 3 – Generate the packing list

Start a new conversation inside the project and send one message describing your trip. That's all Claude needs.

Here is the conversation I started for our recent camping trip.

4 day trip to Traverse city Michigan in late april, camping

Here's what came back for our family (kids 2, Van with roof rack):

That took about fifteen seconds. The list is specific to two kids at those ages and accounts for April temperatures.

Common Mistakes to Avoid

Leave out the accommodation type, and you get hotel assumptions. If your system prompt says "we usually stay in Airbnbs," but you're going camping, Claude will skip sleeping bags, camp chairs, and anything that assumes no kitchen. Add it to your trip message: "4 nights, Acadia, August, tent camping."

Leave out the season, and the clothing guidance becomes useless. Yellowstone in July and Yellowstone in October are completely different packing problems. The mountain July nights are one thing — but fall means serious layers and a much higher chance of rain. Claude won't guess. Tell it the month.

Vague duration without a per-person breakdown gets vague results. "Pack for 4 nights" without the per-person detail means Claude might write "enough clothes for each person" — which helps nobody. The format instruction in the system prompt fixes this: "broken down per person" makes it explicit.

No gear inventory means the list reads like a shopping cart. The first time I ran this without listing owned gear, the output included "Yeti cooler ($350)" and "kids' tablets" as if I were buying them new. Once the inventory is in the system prompt, flagged buy items are actually things you'd need to buy — not things sitting in your garage.

Leaving out kids' ages collapses the list to one-size-fits-all. Without ages, Claude produces a single children's section with suggestions that land nowhere — too old for the toddler, too young for the school-age kid. Ages aren't just about what to pack, they're about how much to pack (toddlers need backup sets; seven-year-olds don't spill as often).

Setup takes about ten minutes — most of it is writing out your gear inventory and thinking about how you actually travel. After that, every trip is one message.

The practical gain isn't just time (though dropping from twenty minutes of editing a generic list to fifteen seconds is real). It's that the list is actually built for your family. The 2-year-old's backup outfit count is right. The sound machine isn't on the list because Claude knows you own one. The cold-night layers are there because you told us you're going in April.

The other thing worth noting is that the project gets better the more you use it. After a trip where you realize you forgot something, add it to your gear inventory or your system prompt. Over time, it becomes a genuine record of how your family travels — not a list someone else wrote.

The same Projects approach works for other recurring tasks — like automating email follow-ups in Gmail or running a weekly cleaning schedule on autopilot with Apple Shortcuts.

Keep Reading