Some would say I should get a better Sunday afternoon habit than AI and LinkedIn.
So I made a family card game.
My kid loves Dungeons & Dragons and was introduced to it at school by a teacher, which I think is fantastic. I love a good dungeon master meme as much as the next person.
But left to my own devices, I am more likely to scroll on my phone than pull out a game box.
Unless there is already a group.
Then I do like something that breaks the ice, gives people an easy way in, and has been pre-vetted enough that one or two people not wanting to play does not ruin the whole mood.
That was the starting point.
Could AI help make a simple conversation deck for after dinner?
- Fun enough for teenagers.
- Safe enough for mixed generations.
- Not so earnest that everyone suddenly needs to discuss their childhood.
- Not so chaotic that it becomes competitive family warfare.

We (Me, myself, & Codex) built the rough version end to end.
- 100 cards.
- Printable A4 sheets.
- Card fronts and backs.
- Icon categories.
- Box artwork.
- Mockups.
- A draft case study.
- A reusable Skill for creating other card-based interaction tools.
It is still a prototype. It needs testing, trimming, editing, and probably a few cards removed once real people get hold of it.
The jump from “this could be nice” to “this is nearly printable” was super fast, unreal at how comprehensive and considered it was with safeguards, limits, and ethics (I have to live with these people for many years to come).

And that is where my work brain kicked in.
Not every workplace problem needs to become a card game.
Please no!
Too many meetings can be bad enough before introducing mandatory corporate play-dates.
But card-based prompts can be a useful format when people need a safer way to practise judgement, explore trade-offs, talk through change, or make a vague topic more concrete.
Culture. Onboarding. Training. AI adoption. Change management. Team reflection.
The format is not really the point. The point is the interaction it creates.
I have put the draft files into a Git repo. You are welcome to adapt it, test it, pull it apart, or use it as a starting point.
If you make your own version, I would genuinely love to see where it ends up.