Skip to main content
process

My work process

How I go from problem to production. Git strategy, testing philosophy, and yes — AI as a tool, with intention.

git

Git workflow

Branching strategy I use to keep a clean and collaborative history in my projects.

git log --oneline --graph
*   948568b (HEAD → main, tag: v1.2.0) feat: UI/UX pass — home, header fixes
|\
| * 0be2f3e (develop) feat: constellation bg + parallax sections
| * b610f9a           feat: copywriting + nav active state fix
| |
| |\
| | * 5c1d27a (feature/seo) feat: SEO — sitemap, JSON-LD, robots
| | * 55e29a3              feat: add Google Search Console meta tag
| |/
| * 4269c7f fix: resolve ESLint warnings
|/
*   edb189e (tag: v1.1.0) fix: logo theme switching + hero subheading

Atomic commits

Each commit represents a complete logical change. I use `git commit --amend` to keep the history clean before push.

Branch strategy

Short feature branches (max 2-3 days). Merge to develop with squash. Release branches for QA.

Code review

Every merge to develop goes through PR with at least one review. I use conventional commits for automatic changelogs.

ai

How I integrate AI into my workflow

Tools and techniques I use to increase my productivity without compromising code quality.

Gentle AI

tool I use

Ecosystem configurator for AI coding agents. One command installs and syncs Claude Code, OpenCode and more with persistent memory, spec-driven development and per-phase model assignment.

View on GitHub

Prompt engineering for architecture

I use language models to explore architectural trade-offs, generate initial database schemas, and document technical decisions (ADRs).

AI ecosystem configuration

I use Gentle AI to configure Claude Code with persistent memory (Engram), SDD workflow and per-phase model assignment — one command, any project.

Review and refactoring

Code analysis to detect code smells, refactoring suggestions, and unit test generation as a starting point.

sdd_session.log
# balanceados-pos — useCheckout-refactor
/sdd-explore "useCheckout God Hook — 226 lines, 30 props"

  → Reading src/hooks/useCheckout.ts
  → 5 architectural issues identified
  ✓  Exploration saved to Engram

/sdd-spec "Decompose into domain hooks"

  Requirements: 4  ·  Scenarios: 9
  ✓  Spec saved → sdd/useCheckout-refactor/spec

/sdd-apply

  → useCheckoutPayment   8 props  payment method + amounts
  → useCheckoutCustomer  8 props  search + debt warning
  → useCheckoutSplit     6 props  split toggle + validation
  → useCheckoutConfirm   3 props  stock check + sale creation

  ✓  commit af55b80 · PASS

Real session from balanceados-pos — God Hook decomposed spec-first in 4 domain hooks

Work Process — Joel May