King Aguirre

Render settings

Look
Motion
IndexKing Aguirre

Render settings

Look
Motion
Start a projecte.kingaguirre@gmail.com

A00 AI

AI is the tool. The thinking is mine.

I use AI the way I use an editor or a compiler: it speeds up the typing. The problem, the architecture, the logic and the decision to ship stay with me. Meet Kami, this site's assistant, first.
See Kai, the voice coach

A01 Two jobs

Kept apart.

A coding tool is fast and confident, and it does not know what the product is for. So the work is split by what each side is good at.

The engineer

What I do

  • Frame the problem and what the person using it needs to do
  • Design the architecture, the data model and the boundaries between packages
  • Write the domain logic and decide the edge cases: money, carts, tickets, permissions
  • Read and review every change before it goes in
  • Decide what ships, and when

The tool

What the tool does

  • Draft boilerplate and repetitive code from a design I have already made
  • Suggest options that I compare and often reject
  • Write a first pass of tests that I then tighten
  • Explain unfamiliar code or a library I have not used
  • Speed up refactors whose shape I have already chosen

A02 How the work runs

My process, with the tool in it.

Every step has an owner. The tool appears in one of them. The brief, the spec, the architecture, the checks and the sign-off are mine.
  1. 01
    Context and goalme

    Who it is for, what they need to do, what done looks like. Written down before any code.

    Rendering
  2. 02
    Spec and acceptance criteriame

    A plan file, a DESIGN.md and an agent guide in the repository, so every session starts from the same truth.

    Queued
  3. 03
    Architectureme

    Apps, packages and boundaries. Domain logic in plain TypeScript packages, secrets kept on the server.

    Queued
  4. 04
    Agent-assisted buildme + agent

    Coding agents (Claude Code, Codex) implement against the spec in small slices while I review the diffs.

    Queued
  5. 05
    Typecheck and testschecks

    Strict TypeScript, Vitest unit tests, Playwright journeys and, where AI is involved, evals.

    Queued
  6. 06
    Human review and sign-offme

    Nothing risky ships on an agent's say-so. In the VibeBox Agent Console, risky stories wait for an explicit approval.

    Queued
  7. 07
    Release and observeme

    Deploy, check the live build, write down what changed and what is left.

    Queued

Scroll to run the queue. The release step waits for you.

Scroll to run the queue. The release step waits for you.

A03 Inside the products

Where a model earns a place.

When AI is part of a product I design the chain myself: what goes in, the one narrow job the model does, and what comes out. Each chain is read from the project's own README.

Fitness and nutrition

Kai

Turns a spoken set or a plate photo into a logged entry, with a spoken reply.

  1. 01Voice
  2. 02Speech to text
  3. 03Set grammar or model
  4. 04Tool calls
  5. 05Database
  6. 06Spoken reply

Personal finance

Kaban

Tala previews money insights only after the user opts in to sharing data with AI.

  1. 01Consent
  2. 02Typed request
  3. 03AI gateway
  4. 04Typed preview
  5. 05User decides

Retail point of sale

Kaha

Turns a spoken order into a cart through an intent parser and an agent loop with tool schemas.

  1. 01Voice
  2. 02Intent parser
  3. 03Agent loop
  4. 04Tool schemas
  5. 05Cart
  6. 06Receipt

Digital media

Uy Trending

Collects trends, clusters stories and drafts research packages that an editor reviews.

  1. 01Feeds and searches
  2. 02Clustering
  3. 03Trend score
  4. 04Research draft
  5. 05Editor

A04 Principles

Four rules that repeat.

Not slogans: each one is a pattern you can find in the repositories.

  1. wire pass

    Specs before code

    Each repository carries its plan, its design system and an agent guide, so the next session (human or agent) starts from the same facts.

    AGENTS.md, DESIGN.md and PLAN.md files across the studio's repositories

  2. clay pass

    Logic outside the UI

    Money, carts, tickets and payouts live in plain TypeScript packages with their own tests, not inside components.

    packages/core in Kaha, packages/ticketing in TicketBoxPH, packages/domain in Kaban

  3. lookdev pass

    Every change is read

    Nothing a coding tool writes goes in unread. I review each diff, run the type checks and tests, and rewrite whatever does not fit the design I set.

    Strict TypeScript, Vitest and Playwright gates in the repositories

  4. final pass

    A person approves what ships

    Agents draft and implement. Payments, releases and risky changes need a human to look first.

    VibeBox Agent Console approvals; Barty Bakes payment attestation

A05 How Kami works

Grounded, or quiet.

Kami answers from 33 entries built from the same data this site renders. With a model key configured, a server route asks Claude with those facts and a strict prompt; without one, a local engine answers. Keys never reach the browser, requests are rate-limited, and when Kami doesn't know, it says so and points to King.
  1. 01Your question
  2. 02Retrieve site facts
  3. 03Claude, or the local engine
  4. 04Answer and cards
  5. 05Contact when unsure