Hustlestats on Start AI Tools - Presented by Intent Solutions

New Year's Eve: A Go CLI From Scratch, a Security Fix, and Two Releases

Wed, 31 Dec 2025 10:00:00 -0600

Last day of 2025. Five projects touched. Twenty-five commits. One project built from nothing, one patched a security hole that should never have existed, and two shipped point releases to close out the year clean.

create-agent-skill: New Go CLI

Nine commits. Brand new project. A Go CLI tool for validating and scaffolding Claude Code agent skills. The problem it solves: skill definitions are YAML files with a specific schema, and getting the schema wrong means the skill silently fails to load or behaves unexpectedly at runtime.

Dream Gym Sprints, Email AI Stack, and 128 RSS Feeds

Mon, 29 Dec 2025 10:00:00 -0600

Four projects. Thirty-eight commits. Two of them are building real product features, one is growing into an intelligence platform, and one just needed a Dockerfile fix.

Dream Gym: Sprints 1 Through 3

Hustle’s Dream Gym module went from concept to working product in three sprints and fourteen commits.

Sprint 1: Workout Logging. The core data model is straightforward — exercises, sets, reps, weight, duration. But the UX question was whether to optimize for speed or detail. Speed won.

GWI v0.3.0, Hustle CI Goes Green, and Intent Mail Gets an AI Brain

Sat, 27 Dec 2025 10:00:00 -0600

December 27th was a convergence day. Three projects that had been grinding through separate backlogs all hit release-worthy milestones at the same time. Thirty-eight commits across git-with-intent, Hustle, and Intent Mail.

git-with-intent v0.3.0

The v0.3.0 release closed four epics: F1 feature hardening, monitoring infrastructure, forecasting pipeline, and infra upgrades. Twenty-three commits landed across the board.

F1 feature hardening cleaned up rough edges that accumulated during the v0.2.x cycle. Approval gate edge cases — empty diff handling, multi-commit squash detection, and branch protection rule conflicts — all got explicit handling instead of falling through to a generic error path. The kind of polish that doesn’t show up in a changelog but prevents support tickets.

PostgreSQL Decommission, Monitoring Stack, and HustleStats v1.0.0

Tue, 18 Nov 2025 10:00:00 -0600

31 commits in a single day. Not 31 features – 31 cleanup, hardening, and shipping tasks that turned a working prototype into a released product. The commit volume sounds dramatic. The reality is unglamorous. This was the grind that makes software real.

PostgreSQL Decommission

HustleStats started on PostgreSQL with Prisma as the ORM. The data layer migrated to Firestore months ago, but the Prisma dependency lingered – unused schema files, legacy route handlers, and a healthcheck endpoint that still pinged a Postgres connection string that no longer existed.

HustleStats Launch Sprint: From Firebase Auth to Production SaaS with Stripe Billing in One Day

Sun, 16 Nov 2025 10:00:00 -0600

The Starting Point

Yesterday ended with 7 dashboard pages running on Firebase Auth. The app could authenticate users and display their data. What it couldn’t do: charge money, enforce plan limits, or prevent free users from accessing paid features.

Today’s goal: ship a complete billing system. Not “billing someday” — billing today, with Stripe checkout, webhooks, plan enforcement, and a customer portal.

33 commits. Four phases.

Phase 4: Final Prisma Cleanup

Before adding anything new, the last traces of PostgreSQL needed to go.

HustleStats Firebase Auth Cutover: 7 Dashboard Pages, 3-Layer Defense, Zero Prisma

Sat, 15 Nov 2025 10:00:00 -0600

The Firebase migration (Days 2-7) gave HustleStats a new auth system and data layer. Today was the cutover — making every dashboard page actually use it.

Phase 1: Planning and Staging

Before touching code, I mapped every page that imported NextAuth or Prisma:

Dashboard home
Player list + detail
Game entry + detail
Stats overview
Settings/profile

Seven pages total. Each one imported getServerSession from NextAuth and made Prisma queries for data. Every page needed both the auth and data layer swapped.

HustleStats Firebase Migration Days 2-7: Schema, Auth Swap, Data Port, and the Cost Cliff

Tue, 11 Nov 2025 10:00:00 -0600

Six days. Four commits. The entire HustleStats backend moved from PostgreSQL + NextAuth to Firebase.

Day 2: Firestore Schema

The Firestore subcollection hierarchy follows the access pattern:

users/{uid}
 └── players/{pid}
 └── games/{gid}

Every query starts with a user. Players belong to a user. Games belong to a player. The hierarchy means security rules can enforce ownership at every level without extra lookups. A read to users/abc/players/xyz/games/123 already proves the caller owns the path.

HustleStats Firebase Migration: 5-Agent A2A Architecture on Day One

Mon, 10 Nov 2025 10:00:00 -0600

Four commits to kick off the HustleStats Firebase migration. The previous stack – Next.js on Cloud Run with Prisma and PostgreSQL – worked but cost $72/month for a youth sports app with minimal traffic. Firebase brings that down to an estimated $20/month. The tradeoff is a complete backend rewrite.

The 5-Agent A2A Architecture

HustleStats is a youth soccer statistics tracker. Parents log games, coaches review performance, kids see their highlights. The new backend uses Google’s Agent-to-Agent (A2A) protocol with five agents:

Deployment Secrets, Missing Columns, and Sitemap Hygiene

Wed, 22 Oct 2025 10:00:00 -0500

Three commits across two repos today. No theme, no arc – just the kind of maintenance work that keeps production systems from embarrassing you.

HustleStats: Email Configuration

Password reset was broken in production. Users clicking “Forgot Password” got nothing – no email, no error message on the frontend, just silence. The Resend API integration was wired up correctly in the application code, the email templates existed, and everything worked in local development. The problem was upstream in the deployment pipeline.