loom

10x

The habits that make a developer 10x, turned into protocol.

---

You've worked with a 10x developer. They aren't 10x because they type faster. They're 10x because they never chase the same ghost twice. Never rebuild a feature because someone forgot a requirement that was discussed three weeks ago. Never spend Monday mornings re-explaining decisions that were already made. They walk into a problem already knowing what was tried, what failed, and where the bodies are buried - because they wrote it down, and they left a trail.

Your AI agent does none of this. Every session starts cold. The reasoning, the dead ends, the tradeoffs you evaluated together - gone with the chat window. Your project forgets everything the agent learned, and next session you're back to chasing the same ghosts.

10x turns those defensive engineering habits into protocol. Your agent writes durable records into .10x/ as it works - not chat logs, not session transcripts, but typed engineering records that prevent the same conversations from happening again. Any future agent can pick up the trail and start working instead of asking you to re-explain the last three weeks.

Not agent memory. Project memory.

Read the protocol | Install

npx skills add z3z1ma/10x

What you get

Your repo grows a .10x/ directory. After a week it might look like this:

.10x/
├── decisions/   # why we chose Postgres over DynamoDB three weeks ago
├── research/    # the dead ends and failed spikes nobody should retry
├── tickets/     # bounded work with explicit scope and progress
├── evidence/    # observed facts: terminal output, test results, reproductions
├── specs/       # behavioral contracts, testably defined
├── reviews/     # adversarial critique before anything ships
└── knowledge/   # compounding team vocabulary and conventions

Here's what a decision record looks like:

Status: active
Created: 2025-06-12
Relates-To: .10x/research/2025-06-10-jwt-vs-sessions.md

## Context

API needs authentication. Two options evaluated: JWT with refresh
tokens, or session cookies backed by Redis.

## Decision

JWT with refresh tokens. Stateless, scales horizontally without a
session store, works for both browser and mobile clients.

## Alternatives

Session cookies: simpler auth flow, but requires shared Redis
instance and doesn't support mobile without workarounds.

## Consequences

Need a token rotation strategy. Rotation interval is an open
question tracked in the auth ticket.

Before and after

Without 10x: Monday morning. New session. "We decided on JWT with refresh tokens last week, remember?" It doesn't. You spend fifteen minutes digging through old chat history, chasing the ghost of a decision that was already made. Scattered across three conversations. You re-explain. Every. Single. Time.

With 10x: Monday morning. New session. The agent reads .10x/decisions/2025-06-12-auth-strategy.md. Finds the JWT decision, follows the Relates-To link to the research that evaluated both options, and picks up the open question about rotation intervals. Asks about that. Work starts in seconds, not after a twenty-minute archaeology expedition.

How it works

Records reference each other by file path. A ticket cites the spec it implements, evidence names the ticket it supports, a decision points to the research that informed it. Implicit graph. No database, no server. Just Markdown files with relative paths pointing at each other.

The protocol has strong opinions about process. Vague requirements get interrogated before anyone writes code. A passing test suite is an observation, not proof of correctness. Subagent output is a claim until evidence grounds it. If this sounds like how your most annoying (and most reliable) colleague operates, that's the point.

Research records are temporal. An investigation from March is still linkable in June, but the agent checks whether the conclusions have gone stale before trusting them. Knowledge records are the opposite: permanent, compounding. You define "tenant" once, precisely, and every future session inherits that definition without asking.