Agentic Workflows

Portfolio Refresh with Agents — Tagline, Projects, and Case Studies

How I used agent-assisted workflows to sync davidcole.cloud with shipped apps, new case studies, and an updated /now page in one session.

  • cursor
  • portfolio
  • astro
  • agents

The problem

The site still said “Design for clients. Build for agents.” while the actual work had moved: three shipped Tauri apps, an Apps Hub, Security Guard in development, and a Hostinger deploy path waiting on DNS.

Portfolio sites rot faster than codebases because marketing copy is scattered — hero taglines, MDX case studies, homepage bento cards, /now, résumé bullets, and open-source lists all drift independently.

The workflow

  1. Map first — WORKSPACE.md and FOLDER_MAP.md before grepping the monorepo
  2. Data layer second — apps.ts for product metadata; content collections for long-form case studies
  3. Homepage third — replace hard-coded DIY project cards with a priority slug list derived from getCollection('projects')
  4. Verify gate — npm run build must pass before calling it done

What changed

AreaUpdate
Hero taglineHigh-performance web for local businesses + autonomous AI workflows
New case studiesSlate, Webcanvas, Gnomad assistant, Security Guard
Homepage bentoApps Hub card + current project grid
/nowJune 2026 focus — Apps Hub, CRM, Security Guard, trading VPS agents
/projectsIntro copy reflects shipped apps and agency tooling

Featured case study on the homepage now resolves to Gnomad Slate (newest featured + pubDate).

Agent patterns that worked

  • Hub-and-spoke context — agents read apps.ts and release manifests, not entire Tauri repos
  • Artifact handoff — mirror script output (manifest.json) as proof downloads are real
  • Single verification command — Astro build catches broken MDX frontmatter and dead internal links early

Agent patterns to watch

  • .gitignore accidents — overwriting ignore files when adding staging dirs
  • Filename assumptions — Gnomad release assets named 0.2.0-1, not 0.2.0-beta.1
  • Duplicate portfolio entries — Technomancers Path vs COBOL Quest; pick one featured arc

What’s next

Hostinger deploy when SSH and DNS are ready, then RSS subscribers get these notes automatically. After that: GitHub Pages for Slate docs and a note on local orchestration lanes (Ollama doc hygiene on the Ryzen hub).