BrokeIt - Trending Repos · All episodes: ↗

App Store compliance, diagram-design, last30days-skill updates

2026-11-22 · 7 min

Listen · Apple Podcasts Listen · Spotify

Stories covered

Transcript

Intro

Sam: Forty-five diagram types and zero Mermaid slop.

Kai: [beat] I'm Kai.

Sam: And I'm Sam.

Kai: And you're listening to Trending Repos for Sunday, November 22nd, 2026.

Sam: We've got a packed show for you.

Kai: First up, a new design system is declaring war on ugly, auto-generated diagrams.

Sam: Then, we have an AI agent that promises to research what the internet really thinks about a topic right now.

Kai: And we'll finish with an open-source playbook to keep your mobile app from getting bounced by Apple and Google's review gauntlets.

cathrynlavery/diagram-design

Kai: Alright, let's kick things off with diagrams. A repo from Cathryn Lavery called `diagram-design` is getting a ton of attention.

Sam: So, another diagramming tool? Does the world really need one more way to draw boxes and arrows?

Kai: Ah, but this isn't for making diagrams, it's for making them beautiful. The repo calls it 'Editorial diagram design'. It's for high-end docs and blogs about tools like GitHub Copilot, Claude, Pi... you name it.

Sam: The README has some fighting words. 'No shadows. No Mermaid slop.' I've seen some truly... [censor] Mermaid charts, so I appreciate the sentiment.

Kai: [laughs] Right? This is a curated set of 45 diagram types, all self-contained HTML and SVG. It's a design system for communicating complex ideas clearly, not just a generator.

Sam: Okay, so it’s for humans designing for humans, not for machines generating charts for humans. The 'editorial' part is key. I'm not piping my code into it.

Kai: Exactly. You're a writer or a developer advocate, and you want your technical deep-dive to look as good as something from a major tech publication. This gives you the assets to do that without hiring a designer.

Sam: I can see the appeal. Nothing kills a good technical article faster than a blurry, unreadable architecture diagram.

Kai: So if you're a developer who blogs, you can seriously level up your presentation. It makes your work look more professional, instantly.

Sam: Alright, I'll star it. But only because I hate ugly diagrams more than I hate new Javascript frameworks. Which is saying something.

mvanhorn/last30days-skill

Sam: Next up, a project called `last30days-skill` from user mvanhorn. It’s an AI agent skill that claims to research any topic and pull together a summary.

Kai: Ooh, the source list is spicy. It crawls Reddit, X, YouTube, Hacker News, the general web, and—get this—Polymarket.

Sam: It promises a 'grounded summary'. Grounded in what, exactly? The collective hallucination of Reddit and X? The prediction market odds?

Kai: [excited] But that's the whole point! It’s not just scraping docs, it's scraping the zeitgeist. When a new tool drops, that's where the real conversation happens. This just automates your doomscrolling.

Sam: The Polymarket integration is what gives me pause. You're mixing what passes for technical discussion with literal financial speculation. How do you separate the signal from the astroturfed noise?

Kai: It's a 'skill' for an agent, right? Not a standalone oracle. The developer using it still has to apply their own judgment. Think of it as a research assistant that brings you all the raw takes, good and bad.

Sam: I suppose. As a security researcher, I could ask it 'What's the chatter around this new CVE?' and get a quick brief on how it's being discussed across different communities. That could be a form of threat intelligence.

Kai: See? And for a builder, it's instant market research. Is the feature I just shipped being celebrated or trashed on Hacker News right now? You can find out in seconds.

Sam: Just... remember what you're getting. A summary of public opinion is not the same as a summary of facts. And public opinion can be bought.

mjmirza/app-store-compliance

Kai: For our last story, something every mobile dev will want to star immediately. It's `app-store-compliance` by mjmirza.

Sam: Let me guess, another long checklist of things to remember before you hit 'submit'?

Kai: It's way more than that. It's an open playbook and a pre-submission guard. It has 124 documented rejection patterns and the fixes for them.

Sam: Wait, it's a linter? It actually checks your project?

Kai: Yes! It has checks for the privacy manifest and data safety requirements, and it can identify over a hundred different third-party trackers.

Sam: One hundred and eleven trackers. [beat] That's... a lot. That feature alone is worth its weight in gold. Getting rejected for a simple metadata mistake is the worst.

Kai: It's always some tiny, obscure rule, isn't it? 'Your screenshot shows the wrong carrier name.' 'You didn't phrase the Sign In with Apple button correctly.' This repo is the missing manual.

Sam: So this is basically one developer's accumulated scar tissue, documented and automated for everyone else's benefit. This is the absolute best of open source. I love it.

Kai: For any mobile developer, this could save you weeks of back-and-forth with app reviewers. That's real time and real money you get back.

Sam: I have no notes. This is unambiguously useful. Starred, forked, and I might actually contribute. That's my highest praise.

Kai: Alright, to recap: First up was `diagram-design`, for creating beautiful, editorial-quality diagrams for your technical content.

Sam: Then we had `last30days-skill`, an AI agent skill for taking the internet's current temperature on any topic.

Kai: And finally, `app-store-compliance`, a pre-flight check to help your mobile app sail through the App Store and Google Play review process.

Sam: Before we go, a little piece of history. GitHub's blog is celebrating the anniversary of the first commit to the Linux kernel.

Kai: No way! It's incredible to think about the ripple effect from that one project. Android, most of the cloud... it all started with one person sharing their work.

Sam: A good reminder that giant, world-changing projects often start as a single, humble repo.

Kai: That's our show for today! Check the show notes for links to all the projects we talked about.

Sam: Thanks for tuning in to Trending Repos. We'll be back tomorrow. And Kai... try to avoid any diagram slop in the meantime.

This show is made with AI: the hosts’ voices are synthetic and the scripts are AI-assisted. Every story links to its original source.