FelizAnniv, and Letting Claude Plan a Trip

A new app, and a different way of using AI to plan travel.

These posts are becoming more and more AI-focused. That wasn’t the plan going in, but here we are.

FelizAnniv

My second project built entirely with AI: a birthday reminder app, with enough extra features that it stopped being a toy somewhere along the way.

Yes, “FelizAnniv” is a slightly awkward abbreviation of “Feliz Aniversário,” Portuguese for “happy birthday,” and no, I don’t have a good excuse for stopping halfway through the word. It is what it is.

Core app:

• Auth (signup/login, JWT) with profile editing — display name, your own birthday, theme
• People CRUD — add/edit/delete birthdays (name, month/day, optional year, notes)
• CSV import with a flexible parser that handles both spreadsheet and month-grid layouts, with a preview before saving
• Today view and Calendar view (month grid + jump-to-next-birthday)
• Light/dark/system theme

API and third-party access:

• API keys — create, list, revoke from Settings
• REST API (people CRUD, /today, /upcoming) usable via JWT or API key
• Interactive OpenAPI docs at /docs
• Per-identity rate limiting
• Usage stats page — daily request chart, status breakdown, by-key and top-endpoint tables

Because it has a proper API, hooking it up to Hermes took no extra work. Now I get a morning notification telling me whose birthday it is, and I can ask Hermes whose birthdays are coming up. Same pattern as the notes-api integration: build a small, well-scoped API, let Hermes consume it, get an agent that quietly does one more useful thing.

Links:

• Code: github.com/ajvcorreia/FelizAnniv
• Frontend image: hub.docker.com/repository/docker/ajvcorreia/felizanniv-frontend
• Backend image: hub.docker.com/repository/docker/ajvcorreia/felizanniv-backend

I can’t guarantee there are no fatal security vulnerabilities in the code. For a local, self-hosted app, I’m comfortable with that — I wouldn’t expose this to the open internet without a proper audit first.

Letting Claude plan a trip

We’re planning a trip to Hokkaido, Japan. The last few trips we’ve used AI to build a rough plan and suggest points of interest. This time, I let Claude plan the whole thing.

I gave it the flight timings and the hotel we ended up choosing — it had initially suggested other hotels, so this was after a round of back-and-forth. From there it planned the full trip. Once the plan was in place, I asked for a document with a timeline view: time of day and duration for each place of interest, laid out so we can actually follow it day by day.

Past trips, AI gave us a starting point and we filled in the rest ourselves. This time it handled logistics — timing, sequencing, duration — not just recommendations. The difference between “here are some places to see” and “here’s your day, hour by hour.”

I’ll let you know how the trip actually went.

This article was drafted with the assistance of AI. Originally published on LinkedIn.