Claude already codes.
skAIld makes it behave.
Left alone, Claude improvises: it skips the plan, marks its own work correct, and forgets the rules you set three messages ago. skAIld rides along in the session and holds the process — so the same disciplined loop runs every time, whether you’re paying attention or not.
Four things, every session.
Not a prompt pack. A workflow that runs whether or not you remember to ask for it.
It shows up
Every session starts the same way.
A session-start hook fires before you type anything: it loads the guidelines for disciplined AI pair-programming, shows the workflow menu, and tells Claude what's available. No pasting rules into chat. No hoping it remembers.
It thinks first
It makes Claude plan before it writes code.
Instead of diving straight in and improvising, work starts as a written plan you can read and correct — a quick plan for a small change, a full spec for a real feature. You catch the wrong approach on a page, not in a diff.
It holds the line
It keeps the build honest while it runs.
Work happens in an isolated worktree, changes get reviewed by a separate reviewer before they land, and fixes are applied by a different agent than the one that judged them. Claude doesn't get to grade its own homework.
It won't let you skip
Nothing ships past the gates.
Pre-deploy gates run the real checks and read the real output before anything goes out — plus a fast path for small releases, an urgent hotfix cut, and a handoff ritual so the next session picks up where you left off.
Plan → Build → Ship, on rails.
Every skill below is part of one continuous loop — and they all ship in the one subscription.
Foundation
Start every Claude Code session the right way.
A session-start banner and workflow menu, the Karpathy guidelines for disciplined AI pair-programming, and an auto-generated What's New changelog from your commits — the on-ramp to the whole skAIld dev loop.
- Session-start banner + workflow menu
- Karpathy guidelines baked in
- Auto-changelog from your git history
/start/karpathy-guidelines/whats-newPlan
Turn fuzzy ideas into a plan Claude can execute.
A disciplined planning workflow — quick plans for small changes and full start-planning runs for real features — so you stop winging it and start shipping against a spec.
- quick-plan for small, scoped changes
- start-planning for full feature specs
/quick-plan/start-planningBuild
Build with PR hygiene and worktree discipline.
The actual coding — start-coding, isolated worktree serving, and a tight review-PR / create-PR cycle — so every change lands clean, reviewed, and shippable.
- start-coding kicks off a disciplined build
- serve-worktree for isolated work
- review-pr + create-pr for clean PRs
- team-review fixes review findings in one window (Agent Teams)
- merge-approved batch-lands approved PRs
/start-coding/serve-worktree/review-pr/team-review/create-pr/merge-approvedShip
Ship safely with pre-deploy gates and clean handoffs.
Pre-deploy gates, a light-deploy path, an urgent hotfix cut, and structured handoff / close-session rituals — so you stop shipping bugs you skipped the checks on.
- pre-deploy gates before you ship
- light-deploy for fast, safe releases
- hotfix for urgent out-of-band patch releases
- handoff + close-session rituals
/pre-deploy/light-deploy/handoff/close-session/hotfixWhat you actually do
Mostly nothing. Start a session and skAIld announces itself with the menu. Say what you want built — it reaches for the right workflow on its own. When you want to steer, the slash commands above are there, but the point is that the discipline runs by default instead of depending on you to enforce it.
It updates itself weekly, and it tunes to the model you’re running — a build for Opus 5, and for the 4.x line if you drop back.
Ready to put it in your session?
Two minutes to install, in your terminal, your IDE, or the Claude Desktop app.