Building the Future with
AI-Native Workflows
Practical guides, real use cases, and daily learnings from deep Claude Code practice, from the Philippines, for businesses and builders worldwide. If you're solving real problems with AI tooling, this is for you.
Areas of Practice
Latest Tutorials
View all →
Caveman Mode: How I Cut Claude Code's Output Tokens by ~75%
A CLAUDE.md persona plus two hooks that make Claude respond terse-but-complete in every session. Same technical substance, a fraction of the tokens.
Make Claude Code Finish the Job: Session Goals with Stop Hooks
Claude Code stops when it thinks it's done, not when the work is done. A session-scoped Stop hook turns your goal into a contract it can't walk away from.
Getting Started with Claude Code: Your First AI-Native Workflow
Install Claude Code, run your first session, and build a workflow that saves you an hour a day. A practical beginner guide from real daily use.
Use Cases
View all →
Optimizing My Site for ChatGPT, Claude, and Perplexity in One Claude Code Session
Full GEO stack shipped in one session: auto-updating llms.txt and llms-full.txt endpoints, 15 AI crawlers explicitly allowed in robots.txt, Person/FAQPage/ProfessionalService schema on key pages, RSS feed with autodiscovery. Zero recurring maintenance, since the feeds rebuild themselves.
Finding Every Broken Link with a One-Liner Claude Code Wrote
Three broken URLs found and root-caused in minutes. Zero broken internal links after the fix, verified on every build. Custom 404 page now ships with the site.
Managing AI Voice Agents from the Terminal with Claude Code and MCP
Complete voice-agent stack (agent config, LLM prompts, phone numbers, call review) managed from Claude Code sessions. Dashboard visits dropped to zero; iteration on agent prompts happens at conversation speed.
Recent Posts
View all →
Claude 'Fixed' My Site Into 404s, and What That Taught Me About AI Guardrails
Claude Code saw duplicate content, applied the textbook fix, and broke every TIL post on this site. The bug wasn't the model. It was where I kept my decisions.
Cloudflare Workers static assets won't serve a 404 page unless you say so twice
Building 404.astro isn't enough. Without not_found_handling in wrangler.json, unknown URLs on a Workers site return a bare response instead of your page.
Building llms.txt as an Astro endpoint so it never goes stale
A static llms.txt is a list you forget to update. An endpoint that queries your content collections rebuilds the index on every deploy. One gotcha: a file in public/ silently shadows it.