Aisles / Baseline
Habits every project benefits from. The core kit and a quality check for every change.
Apply clear-code rules while writing or changing code, then run the project's own lint, type check and tests and fix what fails. Use when writing or editing code, when asked to clean up or tidy code, and before saying a coding task is done. Do not use for prose, design work or one-line fixes the user dictated exactly.
View skill★ 2
Strict low-cost mode for the rest of the session, with tighter reading limits and terse replies. Slash command only. Run it when you want the agent to spend as few tokens as possible.
View skill★ 2
Write a clear git commit for the current changes, splitting unrelated work into separate commits. Use when asked to commit or to split work into logical commits. Do not use to push, amend or rewrite history unless the user asks.
View skill★ 2
Tighten and clarify writing without changing its meaning or voice. Use when asked to edit, proofread or shorten an article, email, README or other document. Do not use to write new content or to change what an argument says.
View skill★ 2
Map an unfamiliar codebase before changing it, reading only what the question needs. Use when asked to understand, survey or find where something lives in a repository, or before changing code you have not seen. Do not use when you already know where the change goes.
View skill★ 2
Write a short handoff note so a fresh session can resume cheaply, and read it at the start of the next one. Use when stopping work with something unfinished, when a session is getting long, or when asked to hand off. Do not use to record a finished task or to document the code.
View skill★ 2
Carry out an agreed plan in small steps, checking each one before the next. Use after a plan is approved, or when asked to build or change something with clear requirements. Do not use when the requirements are still unclear; plan or ask first.
View skill★ 2
Turn a request into an ordered, checkable plan before touching any files. Use when a task spans several files or steps, when requirements are unclear, or when asked to plan first. Do not use for one-step changes or for questions that need an answer rather than a plan.
View skill★ 2
Review a diff for correctness, clarity and risk, and report findings by severity. Use when asked to review changes, a pull request or a commit. Do not use to write the fix; report first, change code only when asked.
View skill★ 2
Run the project's lint, type check and tests (and the route JavaScript budget when available) and print failures only, before calling work done. Use when finishing a coding task, before a commit or pull request, or when asked to check that everything still passes. Do not use as a substitute for reading the failures; fix what it reports.
View skill★ 2
Skills by other authors. We link to them and show their license. We do not host them and our CLI does not install them.
Explore intent and options before starting creative or build work.
Open on GitHub
Shrinks a memory file to save input tokens.
Open on GitHub
Security-focused review of a code change.
Open on GitHub
An interview that sharpens a plan or design.
Open on GitHub
Compact the current conversation into a handoff for another session.
Open on GitHub
Create, improve and measure other skills.
Open on GitHub