open source — Apache-2.0

Claude Code starts blank.
Yours doesn’t have to.

One command composes the whole disciplined setup onto your project. You own every file.

  1. identity-agents-md@1.0.0
    pending
  2. docs-architecture@1.0.0
    pending
  3. structure-agents-nodes@1.0.0
    pending
  4. discipline-gates@1.0.1
    pending
  5. discipline-roles@1.0.0
    pending
  6. quality-onboarding-check@1.0.0
    pending

real registry blocks — this is what composes onto your repo

How it works

  1. Describe it

    Tell the composer what you are building. Plain words.

  2. Confirm the blocks

    The agent proposes the setup. You see every block and confirm.

  3. Open Claude Code

    Fully set up, disciplined from the first prompt.

This is the composer

The real tool, running locally. The agent proposes, you confirm, it builds.

The Slipway composer: a board of setup blocks proposed by the agent, awaiting confirmation

What you get

The live registry — every block versioned, recorded, yours.

discipline

Rules that cannot be skipped.

  • Pre-commit gates + hooks@1.0.1
  • Role cards + role.ps1 launcher@1.0.0
  • Fresh-agent onboarding regression@1.0.0

docs

Docs a fresh session reads first.

  • The document architecture@1.0.0
  • Per-directory AGENTS.md nodes@1.0.0

skills

Workflows on demand.

  • The curated core set@1.1.0
  • Vendor plugin set (superpowers, vercel, token-optimizer, karpathy)@1.0.0
  • Firecrawl web suite (search / scrape / crawl)@1.0.0

knowledge

Your knowledge, wired in.

  • Shared vault brain contract@2.0.0
  • Commonplace second brain@2.0.0
  • Graphify graph + query-first contract@1.0.0

services

Your services, connected.

  • Signet ask-owner (HITL)@2.0.0
  • Shakedown acceptance runs@2.0.0
  • MCP servers (serena + GitHub)@1.0.0

provisioning

Repo and hosting, stood up.

  • Git repo + GitHub@1.0.0
  • Vercel + Neon + domain (P0 runbook)@1.0.0
  • Machine harvest registration (OWNER-MACHINE-ONLY)@1.0.0

identity

Who the project is.

  • AGENTS.md + CLAUDE.md@1.0.0

Watch a setup install

A recorded composition, replayed in order: a fresh project goes from blank to fully disciplined as each block lights through its lifecycle.

samplesample composition — the first recorded real run replaces this
  1. identity-agents-md
    pending
  2. docs-architecture
    pending
  3. discipline-gates
    pending
  4. skills-core
    pending
  5. provision-repo
    pending

Install

Node is the only prerequisite. Everything runs on your machine, with your own Claude Code or Anthropic API key — your repos never leave your disk.

npx slipway

opens the visual composer in your browser

npx slipway init

the same composition, from the terminal

The package is shipping now — watch the repo for the release.

Open source, all the way down

Apache-2.0. The same setup Slipway installs is the setup that guards the Slipway repo itself — the gates, hooks and docs discipline it composes are the ones it was built under. Fork it, change the discipline, own it.