Skip to content
groundwork
Read the docs

Start where the last project finished.

Agent skills, project context and a token contract, in your repo before the first line of code.

bunx @ja3dan/kit init next16-insforge
Browse components

Two halves

Take either one on its own. Most projects take both.

The agent kit

Read the loop

7 skills your agents run, and the context they read before they touch code.

skills/feature/SKILL.md
---name: featuredescription: Open and close the loop around a piece of work. `start` creates the branch, the feature folder and the spec; `finish` refuses to close while any "done when" criterion lacks evidence, then opens the PR. Use at the beginning and end of every feature.---A feature is a folder, a branch and a set of criteria that have to be shown to be met.This skill opens and closes that. Everything between the two halves — `/architect`, thebuild, `/review` — happens inside what `start` created.Two commands: `/feature start NN` and `/feature finish`.## Why a folderWork used to leave its traces in three places: a plan in chat, decisions in a growingtracker, evidence nowhere. The tracker reached 450 lines and stopped being read.One folder per feature fixes the location problem. The tracker goes back to being a statusblock and a checklist, because the detail has somewhere better to live.

The design system

Read the contract

43 tokens in one contract, and a lint rule that fails anything outside it.

app/page.tsx
Fails: <div className="bg-blue-500 p-4">`bg-blue-500` is a raw Tailwind palette colour. Use a token utility (see @ja3dan/tokens/TOKENS.md).Passes: <div className="bg-primary p-4">no problems

Every project you finishmakes the next onecheaper to start.

How a project starts

An empty repo, three steps, and every file each one leaves behind.

  1. Installs the skills, the house style and the design system into an empty repo, then locks what it installed.

    bunx @ja3dan/kit init next16-insforge

  2. Paste 3 prompts into any LLM chat, in order. Each answer feeds the next, and all of them land in context/.

    01-interview.md02-architecture.md03-build-plan.md

  3. The feature skill opens a branch and a folder, and writes the spec before any code.

    /feature start 01
your-project/
  • .claude/skills/
  • app/globals.css
  • context/
    • features/
      • 01-slug/
        • spec.md
      • README.md
    • architecture.md
    • build-plan.md
    • code-standards.md
    • library-docs.md
    • progress.md
    • project-overview.md
    • ui-registry.md
    • ui-rules.md
  • components.json
  • eslint.config.mjs
  • kit.lock.json
  • package.json
Use the arrow keys to move. Right expands a folder, left collapses it or climbs to its parent. Home and End jump to the ends, and typing a letter jumps to the next name starting with it.

Then every feature takes the same path

Most steps leave a file in the feature's folder. The last one will not close while a criterion lacks evidence.

A small sailboat on a glittering blue sea, a shaft of light falling from a dark sky

  1. Open the work

    spec.md

    /feature start NN

  2. Decide before building

    plan.md

    /architect

  3. Build it

    log.md

    the work

  4. Check it with fresh eyes

    review.md

    /review

  5. Close it, or don't

    opens the PR

    /feature finish
Read the loop

23 components, yours to edit

Copied in by shadcn and versioned, so a later update can merge with your edits.

  • context/features

    This repo, read at build time

    FeatureStatusLoop

    Docs refresh, starting with setup

    12-docs-setup

    		Built1/4

    Show, don't tell

    11-show-not-tell

    		Reviewed4/4

    imprint, and ui-registry.md with it

    10-imprint

    		Built1/4
    data-tableBlock
  • MergedIn reviewFailingDraft
    status-pillPrimitive
  • filter-chipPattern
  • buttonPrimitive
  • view-togglePrimitive

Primitives14

Patterns5

Blocks1

Hooks1

Libraries2

Start a project

The whole kit in one command, or the design system on its own.

  1. The whole kit

    Skills, context and the design system, installed and locked.

    bunx @ja3dan/kit init next16-insforge

  2. Only the design system

    The tokens, the theme and the lint rule, through shadcn.

    bunx shadcn@latest init https://gw.jaedan.me/r/setup.json
A sailboat trailing a wake of golden light under a starry sky and tall white clouds
Read the setup guide