Skip to content

Three public repos · two machines · one tool

Claude Code Ecosystem

I use Claude Code every day. These three repos are what came out of taking it seriously: how I configure it, how I split the work between two computers, and how I study it to get certified. Each one stands on its own; together they are how I work.

  1. 0

    Use it every day

    Writing, reviewing and shipping code with Claude Code in the terminal, on real projects. Everything below exists because that daily use hit its limits.

  2. 1

    Configure it well

    Rules that load in every session, hooks that save state, agents per type of task and a status line that says how much context, quota and cache are left.

    Claude Kit →
  3. 2

    Split it across two machines

    The PC writes a task; a Mac mini runs it in a clean worktree inside tmux, with a dollar budget, and hands it back as a git branch to review before merging.

    enjambre →
  4. 3

    Study it in depth

    Original questions per exam domain, spaced review and hands-on labs, all in the browser, to sit the developer and architect certifications.

    Cert Studio →

The three repos

Live · Usable

Agents & AI automation

enjambre

I spread Claude Code jobs across my PC and a Mac mini; each one returns as a branch I review, with a live dashboard of the machines.

Live · Usable

Agents & AI automation

Claude Kit

The Claude Code setup I built this portfolio with: rules, agents, hooks and a status line that does not lie, the same on every machine.

Live · Usable

Agents & AI automation

Cert Studio

I prepare for the Claude Code certifications with my own practice app: 240 original questions, mocks by domain weight and every trap explained.

Academy routes

Architecture

Three repos around one tool: claude-kit configures it, enjambre splits the work between a PC and a Mac mini, and Cert Studio is where it gets studied.

  • PC Windows
  • Mac mini
  • GitHub
  • Hostinger
  • Visitor's browser
reglas · hooks · barraenjambre run · TASKssh · worktree · tmuxcollect · rama mac/<id>corre importadoresgit pushpush a main → builddist/ al docrootdocroot propioHTTPS GET · leccióndrill en el navegadormismas reglas en la Macrepo · configuraciónclaude-kitreglas · hooks · agentes · barrade estadopc windows · sesión de trabajoSesión de Claude Codeterminal · git · editorrepo · enrutadorenjambrerouter · cola · ledger · collectmac mini · nodo de trabajoWorkerworktree limpio · tmux · Playwright ·Lighthousescripts · pythonImportadores de la Academyimport-academia ·import-arquitecturasexterno · gitGitHub3 repos públicos · 2 fuentesprivadashostinger · build y docrootsHostingerbuild Node.js · un docroot porsubdominiopersona · navegadorVisitantereclutador · estudiante ·curiosorepo · astro estáticoLanding + Academyfichas · rutas · lecciones ·glosariorepo · html estáticoCert Studiopreguntas originales · repasoespaciado · laboratoriosC4 · nivel 2 (contenedores) · tráfico ambiente = llamadas reales · clic en una caja para el detallelínea continua = HTTP/SQL · punteada = adaptador elegido por configuración · caja punteada = existe fuera del proyecto
open in a new tab ↗

Flows you can replay

  1. Una sesión arranca
  2. Un trabajo pesado viaja a la Mac
  3. Estudiar lo que uso
  4. Publicar una pieza