For people who can't code and ship anyway

You don't need a developer.
You need a field kit.

Claude Code can build your website, your app, your automation. What it can't do is tell you how to be the client. This kit does: a field guide, 12 ready-made skills, 3 project templates and 50 prompts that turn a non-coder into someone who ships.

One-time payment · Instant download · 14-day refund · Windows, Mac and Linux

Day one is magic.
Day three is a mess.

Everyone's first hour with Claude Code feels like a superpower. Then the project grows, and three things happen to almost every non-coder.

PROBLEM 01

The loop of doom

Claude fixes one thing, breaks another, apologises, repeats. You paste errors you can't read and hope. Two hours disappear.

PROBLEM 02

No way back

It worked yesterday. Now it doesn't, and there is no save point to return to. So you start over. Again.

PROBLEM 03

It built too much

You asked for a form. You got a form, a dashboard and an admin area. Now there are forty files and you understand none of them.

None of these are coding problems. They are client problems: planning, slicing, checking, saving. That is a skill you can learn in a weekend, and most of it can be turned into buttons.

What's in
the kit

One zip file. Plain text you own and can edit. No course to sit through, no community to join, no subscription.

12

Ready-made skills

Slash commands that make Claude Code behave like a patient senior developer working for a non-technical client. Install once, use forever.

11

Chapter field guide

The whole method in about 35 minutes of reading: the mental model, the loop, the five-line brief, the stuck protocol, secrets, money and shipping.

50

Copy-paste prompts

Grouped by moment: starting, planning, building, checking, breaking, shipping.

3

Project memory templates

Fill-in-the-blank CLAUDE.md files for a website, a web app and an automation.

45

Words, translated

A plain-language glossary, plus the launch checklist the /ship-check skill runs.

Twelve buttons
for the moments
that matter

Each skill is a short instruction file. Type the slash command, or let Claude reach for it when the moment fits.

/plan-firstYou are about to ask for something new. Get a plan you can actually judge, before any code exists.
/scope-guardYour idea is big. Cut it to the smallest version worth shipping and park the rest.
/launch-pageFive questions in, one honest landing page out. No invented testimonials.
/explain-plainClaude said something you didn't follow. One sentence, one everyday comparison, what to do.
/save-pointA step works. Save it, with a description you'd understand in a month.
/undoIt was working ten minutes ago. Go back, without losing work by accident.
/stuckSame bug, two failed fixes. Stop fixing, start diagnosing: causes before cures.
/bug-report"It's broken" becomes a clear, reproducible description.
/secrets-checkFind exposed passwords and keys before strangers do.
/cost-checkEvery service that could bill you, and where to set the cap.
/ship-checkInspects the real project and sorts what's left into blocking, soon and later.
/handoffDone for the day. Tomorrow's session picks up without you re-explaining anything.
Look inside before you buy

This is a real skill from the kit

No mystery box. This is the actual /stuck skill, word for word. The other eleven are written the same way: short, strict, in plain language, and yours to edit.

If this page reads like something you'd use, the kit will too.

---
name: stuck
description: Break out of a loop of failed fixes with a calm,
  structured debugging protocol. Use when the same problem has
  survived two fix attempts...
---
# Stuck protocol

Stop fixing. Start diagnosing.

1. Stop. Do not attempt another fix yet. Say so.
2. Collect the facts. Ask the user for exactly three
   things: what they did, what they expected, what they saw.
3. Reproduce. Try to trigger the problem yourself.
4. List causes, not fixes. The three most likely causes,
   most likely first. For each: one plain sentence, and a
   test that confirms it without changing any project file.
5. Run the tests in order. One line per result.
6. Fix one thing. The smallest change that addresses
   the confirmed cause.
7. Verify by reproducing the original steps.
8. Still unknown? Go back to the last save point and
   try a simpler approach to the same goal.

Rules
- Never apply more than one change between checks.
- Never claim it is fixed without re-running the steps.
- No apologies, no filler. Facts and next step only.

The whole method
is four words

Almost every disaster story about AI-built software comes from skipping one of them.

01

Plan

A plan in plain language that fits on one screen. If you can't understand it, it isn't finished.

02

Build small

One step at a time. Small means you can check it in under two minutes.

03

Check

With your own eyes, like a customer. "Done" is a claim, not a fact.

04

Save

A save point after every working step. Problems become two-minute detours.

This is for you if
  • You have ideas and no developer.
  • You've tried Claude Code and got lost somewhere around day three.
  • You run a business, a side project or a consultancy and want to build your own tools.
  • You'd rather read 35 minutes than watch 12 hours of video.
Skip it if
  • You are an experienced developer. You know most of this already.
  • You want someone to build the thing for you.
  • You are looking for a prompt that makes money while you sleep. There isn't one.
  • You don't have access to Claude Code. It is not included.
One price. One file. Yours.

Less than one hour of a freelancer

And it saves that hour the first time you type /undo instead of starting over.

THE NON-CODER'S FIELD KIT
€29one-time
  • Field guide, 11 chapters (HTML + Markdown)
  • 12 Claude Code skills + one-step installer
  • 3 CLAUDE.md project templates
  • 50 copy-paste prompts
  • Launch checklist + 45-word glossary
Buy now · instant download
Checkout is being connected right now. Please check back shortly.
Secure checkout by Stripe · Cards, Apple Pay, Bancontact
14-day refund on request

Questions

Do I really need zero coding knowledge?

Yes. The kit assumes you have never written a line of code and don't plan to. You need to be comfortable installing an app and opening a folder.

What do I need besides the kit?

Access to Claude Code (through a paid Claude plan or API credits) and a computer. Claude Code is not included and prices for it are set by Anthropic.

How do the skills get installed?

They are plain folders with a text file inside. Run the included installer, or open Claude Code in the kit folder and ask it to copy them into your skills folder. Two minutes.

Will this still work when Claude Code updates?

The method does not depend on a version, and the skills are plain text you can edit. If a menu moves, the kit still applies.

Is this a course?

No. No videos, no modules, no community. It is a reference kit: a guide you read once and tools you keep using.

Can I get a refund?

Yes. If the kit isn't for you, email info@jimi.page within 14 days of buying and you get the full €29 back, to the payment method you used.

Is this made by Anthropic?

No. This is an independent product, not made, endorsed or sponsored by Anthropic. "Claude" and "Claude Code" are trademarks of Anthropic.

Plan → Build small → Check → Save

Ship the
thing.

Get the Field Kit · €29 →