# Astro Projects at AI Tinkerers

> Canonical HTML: https://aitinkerers.org/technologies/astro
> Markdown URL: https://aitinkerers.org/technologies/astro.md
> Technology record last updated: 2026-09-18T15:13:42Z
> Generated: 2026-09-21T19:44:51Z

Astro is a web framework engineered for content-driven websites, utilizing a unique islands architecture to deliver zero-client-side JavaScript by default.

Astro optimizes performance by shifting the heavy lifting to the server. Its core feature, Astro Islands, allows developers to build interactive UI components using React, Vue, or Svelte while only shipping the necessary JavaScript to the browser. This approach results in faster Time to Interactive (TTI) and superior SEO outcomes for sites like The Guardian and Nordstrom. Version 4.0 introduced the Dev Toolbar and enhanced View Transitions, further streamlining the developer experience for high-traffic documentation and marketing platforms.

- Official technology site: https://astro.build
- Public AI Tinkerers demos and talks: 3
- Result page: 1 of 1

## Recent Public Talks and Demos

### [I made my own slide deck engine](https://tokyo.aitinkerers.org/talks/rsvp_lE7fweh6jg0)

A presentation engine for UX design interviews: I designed slides in Figma, then ported them to web with 1) GSAP transitions, 2) live prototypes embedded in the slides, 3) a gallery/slide/fullscreen view, 4) a presenter popup with speaker notes, 5) and a cat-paw cursor 🐾. I'll show the tools: the Figma initialization, the in-product control panel where every slide-pair transition is a one-line row I can toggle live from a panel. I'll also show the motion lab I built first: a GSAP sandbox.

- Event context: AI Tinkerers Tokyo — October 5 Meetup — 2026-10-05 — Tokyo
- Public talk page: https://tokyo.aitinkerers.org/talks/rsvp_lE7fweh6jg0

### [Making local elections more transparent with AI](https://la.aitinkerers.org/talks/rsvp__2-l-YlpnxM)

Local elections decide a lot and almost nobody covers them. California city races are nonpartisan by law, so the ballot doesn't share a candidate's party, and local coverage of city hall has thinned to almost nothing. The records are public but unusable: filings as PDFs, a county voter file behind a paywall, endorsements scattered across a dozen sites. Torrance Watch is the public reference that could not exist before LLMs. Every contested race, every candidate covered the same way: background, where they stand, who endorsed them, and who is funding them, split into direct contributions, independent PAC spending, and how many donors actually live in Torrance. Every claim is footnoted to a filing you can open, and equal treatment is a compile gate, so a race covered unevenly fails to build. About 26,000 people used it, and roughly a quarter million saw the findings across Facebook groups, Reddit and Nextdoor. The busiest day was June 8, mid-count, not election night. It forecast the count and called four races itself, for a city of 145,000, because no wire service covers a city election. And it put a number on the money: $148,000 from Orange County real estate PACs across the five races, seven times what Torrance public-safety unions spent. Claude Code built it: 423 merged pull requests, one person, April to August. Six pipelines work the review queues, matching 2,543 donors against 6.4 million voter registrations, checking endorsements against their sources, and drafting candidate profiles. A deterministic scorer runs first and settles what it can. What it cannot resolve goes to LLM judges working under rules written before the run, and every decision records who made it. For the hardest cases three models judge separately, blind to the matcher's own pick, and the label only counts if all three agree. Nothing about it is specific to Torrance. The same pipeline would work for any city.

- Event context: AI Tinkerers LA — August 6: Builder Meetup & Live Demos — 2026-08-07 — Los Angeles
- Public talk page: https://la.aitinkerers.org/talks/rsvp__2-l-YlpnxM

### [Pull-architecture agents: how I forced myself to do growth work](https://valencia.aitinkerers.org/talks/rsvp_-p7b50BEZW0)

A multi-agent system that manufactures pull for the growth work — writing, conference follow-up, CRM hygiene, responding to news — that I'd otherwise skip when product and ops eat my week. Seven agents across five repos, two APIs, and two websites (one fully autonomous), all driven from the only two surfaces I actually live in: my terminal and Mattermost. The demo walks a live pass through the rig: a LinkedIn contact lands in our self-hosted CRM, an article draft gets pushed to a website, a post-conference follow-up gets queued — every action is a curl command an agent emits, with circuit breakers I can tighten in the moment or across the long arc.

- Event context: AI Tinkerers Valencia May Meetup — 2026-05-26 — Valencia
- Public talk page: https://valencia.aitinkerers.org/talks/rsvp_-p7b50BEZW0

## Related Technologies

- [Claude Code](https://aitinkerers.org/technologies/claude-code) ([Markdown](https://aitinkerers.org/technologies/claude-code.md)) — 215 public demos
- [Agent](https://aitinkerers.org/technologies/agent) ([Markdown](https://aitinkerers.org/technologies/agent.md)) — 12 public demos
- [APIs](https://aitinkerers.org/technologies/apis) ([Markdown](https://aitinkerers.org/technologies/apis.md)) — 19 public demos
- [Claude (Anthropic)](https://aitinkerers.org/technologies/claude-anthropic) ([Markdown](https://aitinkerers.org/technologies/claude-anthropic.md)) — 2 public demos
- [Cloudflare](https://aitinkerers.org/technologies/cloudflare) ([Markdown](https://aitinkerers.org/technologies/cloudflare.md)) — 17 public demos
- [Figma MCP](https://aitinkerers.org/technologies/figma-mcp) ([Markdown](https://aitinkerers.org/technologies/figma-mcp.md)) — 2 public demos
- [GSAP](https://aitinkerers.org/technologies/gsap) ([Markdown](https://aitinkerers.org/technologies/gsap.md)) — 4 public demos
- [Mattermost](https://aitinkerers.org/technologies/mattermost) ([Markdown](https://aitinkerers.org/technologies/mattermost.md)) — 1 public demo
- [Node](https://aitinkerers.org/technologies/node) ([Markdown](https://aitinkerers.org/technologies/node.md)) — 99 public demos
- [Playwright](https://aitinkerers.org/technologies/playwright) ([Markdown](https://aitinkerers.org/technologies/playwright.md)) — 32 public demos
- [Postgres](https://aitinkerers.org/technologies/postgres) ([Markdown](https://aitinkerers.org/technologies/postgres.md)) — 12 public demos
- [PostgreSQL](https://aitinkerers.org/technologies/postgresql) ([Markdown](https://aitinkerers.org/technologies/postgresql.md)) — 106 public demos
- [PyMuPDF](https://aitinkerers.org/technologies/pymupdf) ([Markdown](https://aitinkerers.org/technologies/pymupdf.md)) — 2 public demos
- [Runtime](https://aitinkerers.org/technologies/runtime) ([Markdown](https://aitinkerers.org/technologies/runtime.md)) — 10 public demos
- [Svelte](https://aitinkerers.org/technologies/svelte) ([Markdown](https://aitinkerers.org/technologies/svelte.md)) — 5 public demos
- [Zod](https://aitinkerers.org/technologies/zod) ([Markdown](https://aitinkerers.org/technologies/zod.md)) — 2 public demos