My Mac said “Storage Full.”
Finder showed me… nothing useful. 🤦♂️
So I built DiskPilot —
a visual tool that shows exactly what’s eating your space.
Free & open source. Try it 👇
https://t.co/B8wHcV0XD4
#buildinpublic#opensource#indiehackers#macos#productivity
❤️🔥 Claude Fable 5 is so back!
Just Recorded a 16 min Tutorial on How to use Claude Fable 5 to Build Cinematic $50k Websites (step-by-step)
Anyone can now build stunning sites fully with AI
Before Fable 5 goes live again, you need to read this.
Anthropic recently published its full guide to prompting Fable 5 for the best outputs.
Most people have no clue it exists, but it's a game-changer.
When Fable was originally launched, these are the principles I used:
Vibe coders are getting sued.
People are shipping apps with real users and skipping the boring stuff that kills them.
A 20+ year dev shared the pre-launch checklist every AI builder needs.
I added what I learned after shipping 60+ apps at the agency.
Don't skip this:
1. Protect yourself, not just your app. The moment you collect user data you're in legal territory (GDPR, CCPA). Have a privacy policy. Know where user data lives.
2. Row Level Security. Without RLS, anyone can open DevTools and read your entire database. Supabase → Auth → Policies. Zero policies means your app is naked. 5 min to fix.
3. Test the failure path, not just the happy path. Wrong password 5x. Reset for an email that doesn't exist. Verification link clicked twice. Signup with an existing email. Catches 80% of auth bugs.
4. Security baseline in 2 min. Prompt your AI: "Review my app as a security specialist and make sure I have strong security headers and a solid baseline security posture."
5. OWASP. Prompt: "Review my app against OWASP standards and highlight vulnerabilities." This is where SQL injection, XSS and auth bugs actually get caught.
6. Client-side validation is UX, not security. Attackers disable JS and hit your API directly. Validate again on the server. Every time.
7. AI code leaks data in 3 spots: .env values in the frontend, API responses returning too much, secrets in logs. Prompt: "Check my app for credential or sensitive data leaks in frontend or API routes."
8. API keys in the frontend means game over. If it's in the browser, assume it's already taken. Move it server-side or proxy it.
9. Rate limits before someone burns your API bill. Cap every endpoint hitting a paid API. I've watched a Supabase bill jump from $20 to $200 in a day.
10. CAPTCHA on public forms (Cloudflare Turnstile is free) plus CORS locked to your domain. 10 min, kills bot floods.
11. Error messages that don't leak. "User not found", not "SELECT * FROM users failed". Log full errors server-side, show users generic messages.
Build fast. Just don't ship naked.
(full breakdown in my article below)
How I build with Claude Fable 5 👇
1. WebGL = liquid glass typography rendered live
2 Three.js transmission shaders = text looks like blown glass
3. Sky video loop behind glass = depth flat backgrounds lack
4. GSAP ScrollTrigger = liquid letters morph on scroll
5. CSS backdrop-filter = fake glass UI in one line zero WebGL
6. Particle drift = soft floating bubbles feel alive and airy
Save this ☁️
This is my loop
I built a SaaS that posts to Instagram + TikTok 24/7
I don't write the captions. I don't pick the music. I don't touch it
The stack that runs it while I sleep:
> PHP 8.3, no framework
> Caddy web server
> SQLite in WAL mode
> Cloudflare R2 for video storage
> Cloudflare Tunnel, no open ports
> Stripe for billing
> OpenAI writes every caption
> ffmpeg muxes the music
> Zernio publishes to IG + TikTok
> Vanilla JS + CSS on the front
> one cron job that loops forever
No Next.js. No Kubernetes. No VC
Claude Fable 5 built a 3D product website with Claude Code
Generate an image of a product with the Magnific MCP, and convert it into a 3D model.
Download that model and give it to Fable 5 to develop an interactive page with.
Here's the final result + prompts:
Annnimate v3 is live today.
Adrian and I almost shelved it in March. v2 wasn't the right product, so we threw it out and rebuilt the whole thing.
It's the version we wanted from the start.
-> Link in profile
Anthropic's in trouble, again!
They spent years building what's now fully open-source.
What made Claude feel different from a normal app is that the agent could act inside the interface instead of only talking in a chat box.
For instance, Claude Artifacts let an agent render real UI, charts, dashboards, and interactive components that assemble live inside the response.
Every major AI product tried to replicate it.
But the problem was that unlike reasoning, planning, tool-calling, etc., none of it shipped natively with LangGraph, CrewAI, or Google ADK.
So teams started building an owned version that required engineering the entire interface layer from scratch.
Most teams, however, just settled for shipping the agent as a backend API in a chat box since rendering the UI is only one piece of it.
To actually make it work, the interface layer also needed real-time streaming, state kept in sync between agent and UI, conversations that persist across sessions, and reconnection when a user refreshes mid-run.
@CopilotKit is now the only open-source framework that actually lets you build your own full-stack Claude-like apps.
It decouples the agent from the interface, talking over AG-UI (an open protocol for agent-to-user communication).
Being a standard protocol, the frontend never needs to know whether it is talking to a LangGraph or a CrewAI agent. You can change the backend anytime and the UI will never notice.
In practice, CopilotKit's interface layer gives several pre-implemented React building blocks that wire the agent directly into the app, like:
- generative UI, so the agent renders real components instead of text
- chat windows, sidebars, and popups, or a fully headless setup
- shared state, so the agent and app stay in sync
- human-in-the-loop approvals, where the agent waits before acting
- persistent threads that store the whole session, including the agent-user interactions and generated UI, not just text
And because that full history is captured, those interactions can feed a self-learning layer that also improves the agent from real usage over time.
The interface layer that Anthropic spent years engineering in-house is now literally available to any developer/team.
CopilotKit is open-source with 30k+ GitHub stars, and AG-UI, the protocol underneath, is already supported across every major agent framework: LangGraph, CrewAI, Mastra, Google ADK, and more.
CopilotKit GitHub repo → https://t.co/wkQ1taF0rM
(don't forget to star it ⭐ )
If you want to go deeper, I found a detailed breakdown by Shubham Saboo recently on the three Generative UI patterns, with implementation.
Read it below.
I just spent roughly 15 hours on this navigation component so you don’t have to.
and just dropped into the vault 🎉
one thing i really like about this one is the morphing motion, but also something people often overlook: accessibility.
it’s fully responsive, keyboard accessible, and built so everyone can actually use it.
also, no dependencies. Just vanilla HTML, CSS and JavaScript.
you can test and play around with it, link in the comments ↓