"We fixed this last week."
Latest version
v1.3.2
Hold on. Think first. Code less.
waitsec is a set of instruction files for your AI coding agent. Not a library, not a runtime. It is a checklist the agent reads so it stops turning a one line fix into twelve new files.
npx waitsec
Run it inside your project folder. It detects your editors and puts the files in the right place.
The problem
If a small request keeps growing, the agent has no boundaries.
You ask for one change and get a refactor. You report a one line bug and watch five unrelated files change. You get told it is done before anyone ran it. These are not model failures you can prompt away every time. They are missing rules.
waitsec writes the rules down once, so every task in the project starts from the same boundaries.
what the rule looks like
# from the core skill
Keep the change small.
Change every file needed for a complete
solution, and no unrelated file.
If a choice could change permissions,
data safety, or something hard to undo,
ask one to three direct questions.Twelve new files for a two line change.
A rewrite where a patch was enough.
"Done" before anything was run.
The skills
Five skills. One core, four focused.
Install all of them, or keep only the ones your project needs. Every extension depends on the core skill, so always include waitsec.
waitsec
core
The core guardrails: ask first when a choice matters, avoid over-engineering, keep the diff small, debug from evidence, and verify before reporting.
waitsec-pagemaker
Builds complete web pages: project recon, section order, visual direction, responsive layout, and SEO with structured data only when the page calls for it.
waitsec-code
Clean code rules: no comment noise, small focused functions, and no dependency added for something the language already does.
waitsec-ui
Interface restraint: anti-slop visuals, mobile-first layout, real focus states, and copy that helps people act.
waitsec-quality
Security review, realistic tests, sensitive data handling, and migration safety.
Install
Pick the install that fits your setup.
The interactive installer handles every editor. Use the skills CLI when you want a non-interactive command.
Interactive installer
terminal
# inside your project folder
npx waitsecUniversal skills CLI
terminal
npx skills add mevebu/waitsec -yPartial install
Extensions depend on the core skill, so include waitsec with any extension you pick.
terminal
# core only
npx skills add mevebu/waitsec --skill waitsec
# core plus the page builder
npx skills add mevebu/waitsec --skill waitsec waitsec-pagemaker
# several extensions at once
npx skills add mevebu/waitsec --skill waitsec waitsec-pagemaker waitsec-uiInside the repository
Files go in the current folder, for example .agents/skills/ or .claude/skills/, plus a rules file. Best for teams: the rules travel with the repository and can be committed.
Every project on this machine
Files go in your home folder, for example ~/.agents/skills or ~/.claude/skills. Every project gets the guardrails, even brand new ones. A project install wins inside that project.
How it works
Three steps, and the rules travel with the project.
-
Run the installer
It lists the editors it can see and asks where to put the files.
-
Choose a scope
Project only keeps the rules in the repository, so your team gets them too. Global puts them in your home folder, so every project gets them.
-
Work as usual
The agent reads the rules on its next task. No command to remember after this.
FAQ
Common questions.
Is waitsec a library?
No. It is a set of plain instruction files that your coding agent reads. There is nothing to import and nothing running in your app.
Which editors does it support?
The installer detects the editors it can see and writes the right rule file for each, for example .cursorrules, .kilorules, or a block in AGENTS.md.
Does a project install override a global one?
Yes. If both are installed, the project rules win inside that project.
Can I install only one skill?
Yes, but always keep waitsec itself. The focused skills build on it.
Give your agent the checklist.
One install in the project. The rules stay in the repository from then on.
npx waitsec
Also from mevebu
