The Showcase

A gallery,
not a feed.

One curator. Nine projects. Updated once a week, not once a second. Chosen for reasons, not for numbers.

Curated by Prof. Weining Zhang · Updated weekly · Last updated April 2026

What this isn't

No feed.
No numbers.

  • No likes.Nothing to compare your work against other people's.
  • No followers.No one is watching your count go up or down.
  • No comments.Nothing for a stranger to say to a child.
  • No trending.No algorithm deciding what you see.
  • No profiles.There are no accounts here. Nothing to sign up for.
What it is

A small room,
curated slowly.

  • One curator.I choose what goes in. I'm a real person you can email.
  • One reason per entry.Every project gets a note explaining why it's here.
  • Weekly changes.New work arrives about as fast as a magazine, not a social feed.
  • Nobody's ranked.Being in the gallery isn't a reward. It's a gift from one reader to another.
  • No pressure to be seen.Most projects at Kindling never show up here. That's fine.
★ Now Showing

The one I've been
thinking about all week.

★ The other half of the gallery

When the fire didn't catch.

Three honest near-misses. Each one is a kid who built something the AI was technically happy to make — and then realized, after the fact, that something was missing on the inside before they ever started typing. The missing thing has a name. It is one of the three things.

🔥 missing: passion

The Skill About Everything

Sam, 11 · Skills Workshop

Sam wanted to build a Claude Skill but couldn't pick a topic. So they let Claude pick one. The Skill that came out was a "general knowledge assistant" — and every answer it gave felt like Wikipedia read out loud.

What happened →

Sam spent four hours adding random facts to a Skill they didn't care about. They tested it on a question they'd just made up ("how do clouds form?") and Claude-with-the-Skill answered in exactly the same voice as Claude-without-the-Skill.

Then they opened Maya's Backyard Birds of Ohio Skill from the Showcase and ran the same kind of question on it. Maya's Skill answered with stories. Sam's answered with definitions. The difference was not the technical quality of the YAML. The difference was that Maya knew something nobody had taught her, and Sam had not stopped to ask whether they knew anything like that yet.

What the trait would have changed The Skill cannot supply the obsession. The obsession has to come into the room first. Otherwise the Skill is just Claude wearing a hat.

Sam took the Skill down. They spent the next month writing in a notebook every time they noticed they wanted to know more about something. The list was short for two weeks. Then one entry came back: old maps. They tried again, and this time the Skill had a voice.

💙 missing: empathy

The Compliment Generator

Jordan, 12 · Skills Workshop

Jordan built a Skill that produced personalized compliments. They gave it to a friend who'd had a bad week. The friend used it once and asked, gently, "is this from you, or is this from the robot?"

What happened →

Jordan had tested the compliment generator on themselves and felt good. The compliments were warm and specific-sounding. They thought: a friend going through something hard could really use this. They sent it.

The friend tried one compliment. Then said, very kindly: "this doesn't feel like you. it feels like a robot trying to make me feel better, which is almost worse than nothing." Jordan understood instantly. The thing the friend needed was not warm words. The thing the friend needed was the proof that Jordan had spent ten minutes thinking about her in particular. The Skill had skipped that step on purpose.

What the trait would have changed Empathy is the part of caring you can't outsource. The moment you outsource it, the caring vanishes — even if the words don't.

Jordan took the Skill down and wrote one specific note by hand, about one specific thing. The friend kept it. Jordan never built a compliment generator again, and they describe this as the most useful Skill they ever didn't ship.

✨ missing: taste

The Website with Everything On It

Riley, 13 · Code Club

Riley built a fan website for their favorite band. They asked Claude to help. They added every feature Claude suggested. The result was a single page with twelve sections, autoplay music, a quiz, three different navigation menus, and a chatbot.

What happened →

Riley showed the site to their best friend, who scrolled in silence for thirty seconds and then said: "this is a lot." Riley realized, on the spot, that they had not said no to a single one of Claude's suggestions. They had said yes to all of them. The site contained every feature any fan site anywhere had ever had.

The trouble wasn't that Claude had suggested too much. Claude will always suggest too much. The trouble was that there was no one in the loop with the willingness to delete things. Riley reread the page and counted the things they actually cared about. There were two: a paragraph about the third album, and one specific photo from a 2019 concert. Everything else was filler.

What the trait would have changed AI's first draft is plausible. Plausible is not the same as good. The willingness to throw plausible work away is the entire skill, and Claude cannot supply it for you.

Riley deleted the whole site and rebuilt it as one page: one paragraph, one photo, one sentence at the bottom. They sent it to the same friend. The friend kept the tab open for a week. Riley still keeps a screenshot of the original twelve- section monster on their desktop, as a reminder.

One more thing

There's no "Submit" button.
On purpose.

Kindling doesn't have accounts, uploads, or a submission form. If a kid makes something in one of the academies and their family wants it considered for the Showcase, a grown-up writes me a short email. I read every one.

Most projects I receive I don't include. Not because they aren't good — because the Showcase is only meaningful if it stays small. A few things a week. One person deciding. That's the whole idea.

Email the curator