Structured Commits as Lesson Inputs
Commit messages with What/Why/Learned sections capture reusable insights at the moment of discovery, feeding downstream lesson extraction pipelines
Lessons Hub
Static website and build pipeline consolidating markdown lessons from multiple repositories into one searchable, AI-powered library.
24 lessons
Tags
Phases
Lessons
Dev Port Registry for Multi-Project Work
A centralized port assignment table in shared developer config prevents localhost collisions when running multiple projects simultaneously.
Public and Private Repo Harvesting
A multi-repo content pipeline must handle mixed visibility gracefully — token scope, clone failure semantics, and local fallbacks all need explicit design.
Tidy Skill for Repo Housekeeping
A structured, behavior-preserving housekeeping pass prevents repo entropy without the risk of accidental refactors.
Acceptance Testing with Playwright
Use BFS link crawling and smoke tests against live URLs to catch broken navigation and UI regressions before users do
Adding a Voice Reader to Lesson Pages
Integrating browser-native text-to-speech into a static site requires handling platform quirks, script timing, and progressive enhancement — the Web Speech API is powerful but fragile across browsers.
GitHub Pages Custom Domain Setup
Configuring a custom domain for GitHub Pages requires coordinating DNS, repo settings, build tool config, and deployment mode — each can silently break the others.
Live Infrastructure for Integration Testing
When local services are already running, skip mocks and test the real pipeline end-to-end
Mock vs Live Testing Trade-offs
A decision framework for when to mock dependencies and when to test against real infrastructure
Preflight Gates as Local CI
Run the same checks CI will run before pushing to prevent the most common build failure patterns
Skill-Driven Workflow Automation
Composable slash-command skills turn multi-step developer workflows into repeatable single-command operations that enforce guardrails automatically
Test Pyramid for Static Sites
Layer unit, integration, and acceptance tests so each catches what the others cannot in a static site with a backend API
Testing Cross-Repo Content Pipelines
Validate harvested content spanning multiple repositories with severity levels, slug uniqueness, schema enforcement, and link resolution
Adapter Pattern for Multi-Cloud Portability
Abstract base classes with minimal interfaces let the same RAG pipeline run on four different cloud providers without conditional logic in business code.
Code Review as Requirements Source
Systematic triage of code review findings produces a traceable requirements document — turning ad hoc observations into prioritized, implementable work.
Five-Stage Design-to-Execution Workflow
A repeatable workflow — Design, PDR, Plan, Execute, Commit — with table-driven task tracking and one-commit-per-phase discipline, applied across 18 project phases.
Lazy Imports for Optional Cloud Dependencies
Deferring cloud SDK imports to runtime lets the same codebase run with or without any given SDK installed, and enables testing without real dependencies.
Phased Multi-Cloud Infrastructure as Code
Three cloud stacks (AWS, Azure, GCP) built in separate phases with OIDC federation, avoiding cross-cloud coupling while sharing a common authentication pattern.
RAG Corpus Chunking Strategy
Splitting documents at H2 headings with stable IDs and content hashes produces predictable, debuggable chunks that support incremental re-indexing.
Rule-Based Gap Detection Without ML
Seven heuristic rules detect when a RAG corpus can't answer a query, without training data or a classifier — transparent and debuggable, with known trade-offs.
GitHub Pages Build Pipeline
Designing a GitHub Actions workflow that harvests, validates, builds, indexes, and deploys a static site.
Harvester Design Decisions
Key choices in building the lesson harvester — recursive scanning, path-based slugs, and integrated export generation.
Static Search with Pagefind
Integrating Pagefind for full-text search on a static site with no backend.
Validation Severity Model
Why the validator uses ERROR/WARNING/INFO levels and why warnings never fail the build.