CTRL-A · Vol. 01Toolkit 02
The Dev Toolkit · Part 01 The Craft

Tutorial hell to shipped, the gap is smaller than they tell you.

We teach the prompts, the workflow, and the tools that close it. Start here: the vault. Steal the exact prompts we run, then direct the output like a senior.

assemble your prompt
role
context
task
constraints
format
the prompt mixer
100/ 100

Sharp

  • A clear rolein
  • Concrete contextin
  • A specific taskin
  • Real constraintsin
  • An output formatin

Edit, reorder, or switch off any block. The score moves live. Miss a part and the model fills the gap with a guess.

your assembled prompt5 of 5 parts on
You are a senior product engineer who ships.

I am a solo creative, not a coder, building {a small web tool} for {my audience}. I care that it works and looks intentional, not that it is clever.

Build me {the thing}, end to end, in one file I can run.

No dependencies I have to install. Explain nothing unless I ask. If a choice is ambiguous, pick the simplest option that works and tell me in one line what you picked.

Full code first, then a three line how to run it at the bottom. No preamble.
Grab and go · freeSwap the braces, take what you need
The thinking partner
before anything gets built
Ruthless first draft
get to working, fast
The reviewer
before you ship
Explain it to me
understand what you got
Take the files

The prompt and skill library

The starter skill file and the prompt pack we actually build with. Drop your email and they open right here, plus you get every new drop.

  • A ready to use SKILL.md starter you can drop into any project
  • The full prompt pack, not just the grab and go samples
  • Every future drop, first
The thesis

AI is coming for development. It already did

The gap between an idea and a working thing has never been lower. Whole experiences that used to need a team are reachable right now, if you know how to work the tools.

Even senior engineers are not writing code line by line anymore. The skill moved up a level, from writing to directing the output, and catching it when it is wrong.

Where most people get it wrong

The trap is mistaking speed for progress

01

The noise

Agents, pipelines, systems that supposedly do everything for you. We have tried most of them, so you do not have to.

02

The cost

Tokens cost money, time costs more. Without intention, all that automation is just an expensive way to produce slop.

03

Faster is not better

An AI building the wrong thing faster is not progress. Speed without direction gets you to the wrong place sooner.

The foundation · prompt engineering

The real skill is saying exactly what you mean

Not the buzzword version. The actual skill of saying precisely what you want, with the right context and constraints, so the output is something you can use. It is the most transferable skill in this space right now. The vault at the top of this page is it, in practice.

The living course · Claude Code

The Claude Code crash course

Claude Code is the tool we actually build in. This is the crash course, the real moves from our sessions, not the version posted for engagement. It updates with every shift, and more lands every month.

01
Skill files
02
Slash commands
03
Subagents
04
Workflows
05
MCP tools
06
Efficiency patterns
Six chapters · plus models, systems, and token craftOpen the full course
Proof · what you can build

Beautiful things, no team required

This is the whole point. The stuff that used to need a developer, or a whole team, is reachable now. Here is the range, and the kind of thing you would ask for.

data visualization

turn a messy spreadsheet into a chart people actually read.

ask: chart this csv as clean bars, one accent color, label the axes.

content calendars

a month of posts, planned and laid out, in a single pass.

ask: build a month grid and drop these post ideas onto the right days.

interactive demos

a clickable prototype of the thing in your head, no team.

ask: make a one page demo of {idea}, in one file i can open.

+

your idea, whatever it is

a small tool for your one specific annoying problem.

ask: i need a tool that {does the annoying thing}. simplest version first.

The window is open

The creative who learns to build right now, even imperfectly, has an unfair advantage for the next several years.

The window is open. This is how we think about walking through it.

Part 02 · The ToolsNow the stack. The tools we build and ship client work on.

Development.

Our full development stack, from framework to deployment. These are the tools we build and ship with every day, chosen for speed, reliability, and developer experience.

8 Picks · Updated monthly
Industry Signals · what shifted lately
Featured · start here
nextjs.org
Preview
01Intermediate

Next.js

The React framework that turns a folder of files into a fast, production site.

FrameworkOpen
tailwindcss.com
Preview
02Beginner

Tailwind CSS

Style straight in your markup with small utility classes, no naming, no dead CSS.

StylingOpen
www.framer.com/motion
Preview
03Intermediate

Framer Motion

Spring-physics animation for React that looks expensive with very little code.

AnimationOpen
Also in the kit
Part 03 · The Cabinet

Skills we actually take.

Custom Claude Code skills we built for this exact repo. Funny name on the label, dead-serious job inside. The strength rating is the same headache scale the skills score with. Take as needed.

StrengthASPIRINADVILMIGRAINE
A history lesson

How building got cheap.

In one lifetime, building software went from a room full of specialists to a kid on a laptop at midnight. And more than once, the person who moved the whole world was just someone mildly annoyed who gave their fix away.

Enter
← PreviousMusicNext →Design