Skills
The SKILL.md workflows in skills/: what each one does, what it asks you for and how it confirms the work is done.
skills/<name>/SKILL.md holds the workflows a coding agent such as Claude Code follows when it works on this repository or a project made from it. .claude/skills/<name> links each one, so opening the checkout is enough. Every skill has four sections: Inputs (what the agent asks you for), Invariants (rules it keeps), Workflow (the steps) and Verification (the commands and pages that prove the task is done). How to install and run them elsewhere is in Use the coding agent skills.
These are not the agent-skills/ packages that the optional /app/agent workbench runs; those are described in Agent template.
At a glance
| Skill | Use it to | You provide |
|---|---|---|
project-context | Learn the project before changing it | The task or the area to understand |
quick-start | Create a project and reach a working admin sign-in | Project name, domain, platform, whether the agent is needed |
configure-providers | Connect sign-in, email, payments, storage, AI, analytics or cache | The capability and the provider's credentials |
new-page | Add one admin or workspace page | Path, what it reads and writes, the permission key |
new-module | Add a capability module end to end | Module key, tables, pages, permission keys, required modules |
new-agent-plugin | Add an agent capability to the one workbench | Plugin id, scene, the Skill it ships, what the reader sees |
deploy | Deploy to Cloudflare, Fly.io, Railway or Docker | Platform, its signed-in CLI, a Postgres URL where needed |
add-module | Install or upgrade a module from a Kernlift registry | Module key |
remove-module | Uninstall a registry module, keeping edits and data | Module key, whether its data goes too |
Ask for the task in plain words, or name the skill: "use the new-page skill to add an admin page for exports".
Understand
project-context
Has the agent run pnpm kernlift context for an overview, read AGENTS.md, then narrow to the routes, plugins, settings pages, variables, scripts or validators the task touches, open the files named, and pick the task skill. Done when the overview's plugin list matches src/plugins/installed.ts and pnpm validate:skills passes.
Build
new-page
Adds a page under /admin/<x> or /app/<x> with copy in both locales, server functions gated by a permission key, a navigation entry and the guards of the layout it sits under. Done when pnpm validate:route-i18n, pnpm validate:app-i18n, pnpm validate:auth-boundary and pnpm validate:beui-console pass, the page renders in both locales and themes, and the entry is hidden from a user without the permission.
new-module
Adds a capability as a module: repository, service, routes, schema and migrations for both dialects, copy in both locales, a validator, and a manifest with @module markers. Done when pnpm validate:registry shows the foundation still typechecks on its own, the module's own validator passes, and pnpm validate:all turns no check red.
new-agent-plugin
Adds a plugin to the agent workbench: server extension, browser entry, Skill, cards, panels and operations, switched on and off at runtime from /admin/plugins. Done when pnpm validate:agent-plugin-contract and the plugin's validator pass, pnpm build:agent-service still builds, and the plugin appears in the /app/agent picker.
Configure and ship
quick-start
Creates a project, installs it, migrates the local database, creates the super administrator and starts pnpm dev. Done when pnpm typecheck and pnpm validate:gate pass and /setup shows the session secret and one sign-in method as ready.
configure-providers
Walks through the /admin/config/* page for a capability and keeps provider credentials out of the environment. Done when /setup shows the item as ready and pnpm validate:env-example passes; EXTERNAL_VALIDATE_STRICT=true pnpm validate:external runs the real provider checks.
deploy
Picks or switches the platform recorded in deploy.config.json, stores the generated secrets, migrates and deploys. Done when the deploy command prints the URL and /setup shows the platform, the session secret and scheduled jobs as ready. pnpm smoke:node or pnpm smoke:worker checks the build first.
Modules
These two apply only to projects that install modules from a Kernlift registry. Templates bought from the store arrive as their own GitHub repository and need neither; see Get Kernlift.
add-module
Installs or upgrades a module, then runs its install, migrate and validator steps. Done when the module's validator passes, the CLI's health check is clean, and its admin page appears for users with its permission.
remove-module
Uninstalls a module: previews the plan, keeps your local edits and keeps the module's data unless you ask otherwise. Done when the CLI's health check is clean, pnpm typecheck and pnpm build pass, and the module's pages are gone.
Checks
| Command | What it checks |
|---|---|
pnpm validate:skills | Every skill has the four sections and names only commands, paths and routes that exist |
pnpm skills:pack | Builds @kernlift/skills from skills/ |