One seed and your project bounces back.
Rules, memory and walls that really block, for Claude Code and Codex. In English or Spanish.
> /plugin marketplace add petersonsenadevs/senzu > /plugin install senzu-all@senzu > /install Stack detected: astro Rules, skills, walls and commands installed. Done. Open a new session.
Your agent forgets, rushes in and assumes.
Your agent forgets what you decided together, ships to production without asking and assumes what it never tested. Senzu fixes all three.

- “I didn’t know we had decided that”
- Memory. MEMORIA.md and the devlog search: every session starts knowing what was decided and why.
- “I already pushed”
- Walls. Push, production deploys and destructive deletes are blocked until you approve them.
- “It should work”
- Verification. Lint, types, tests and mobile at 375 px before saying «done», with the output in front of you.
One seed. Your CLI, recharged.
Scroll slowly: this is what happens when you install Senzu in your agent.
- The seed goes into your project with one command.
- Memory: what you decided, loaded in every session.
- Walls: push, deploy and deletes, under your approval.
- Verification: nothing is «done» without the output in front of you.
Dangerous actions are not asked nicely: they are blocked.
A hook denies the action and says why, before it happens. Not a piece of advice in a prompt.
- Push and deployNothing reaches main or production without your explicit approval at that moment.
- SecretsKeys and tokens do not get into the code.
- Destructive migrationsDROP, TRUNCATE and resets, stopped.
- ConventionsWhat the project sealed is respected.
> git push origin main [BLOCKED by Senzu] This git push is not allowed: it targets a main branch (main, develop, staging, production, release/…). > netlify deploy --prod [BLOCKED by Senzu] Production deploy detected. It needs the user's explicit approval right now (/deploy checklist: fresh verified backup + rollback plan + smoke test). > it.only('computes the total', ...) [BLOCKED by Senzu] You are introducing .only in a test: a focused test that reaches CI silently disables the suite.
git push to main.Install SenzuStart every session knowing what was decided.
Current decisions live in MEMORIA.md and load on their own at the start. Whatever is not there, the agent looks up in the devlog and cites the entry: it does not guess.
## Decisiones vigentes
- D-004 · Dominio gratuito de Vercel de momento; URL del sitio por variable · ver 003
- D-005 · Pie: «Hecho por Peterson Sena» → github.com/petersonsenadevs · ver 003
- D-012 · Loader B (brota en 3D y vuela a la cabecera) · ver 015> node buscar.mjs "dominio" 3 resultado(s) para "dominio" (19 entradas en senzu/devlog): 1. 003 · 2026-10-02 · Brief: dominio y autoría cerrados [decisión] «dev-004: dominio gratuito de Vercel de momento.» senzu/devlog/2026-10-02/003-brief-dominio-y-autoria.md
Real output from the devlog of this site, built with Senzu. It is in Spanish because the devlog is written in the project’s language.
If it says it works, show the output.
Before anything is done: lint, types, tests and the mobile view at 375 px, in monorepos too. If something fails, it is fixed and run again; «done» comes with the output in front of you.
How it verifies the UI> npm run lint ✓ 0 problems > astro check ✓ 0 errors · 0 warnings > npm run build ✓ exit 0 > ui-verify /docs/ · 375px ✗ 4 tap targets < 44px on mobile … fixed and run again … > ui-verify /docs/ · 375px ✓ no problems found
Design goes in rounds too.
Two mockups that open with a double click. You vote on every piece: what you like is pinned, what you don’t is vetoed, and the next round always brings something new. This site came out like that, in three rounds.
How rounds workThe essentials, at a glance.
The commands that save you the most work and the walls that cover you the most. Each one links to its page.
Commands for every day
Type them or ask in plain words: the router knows which one applies.
/verifyVerify the project after changes — build, lint, types, tests and (if there is UI) mobile/debugMethodical debugging — reproduce, failing test, hypothesis, narrow down, fix the cause and verify/securitySecurity review with evidence — surface map, OWASP pass, report and fix plan/dependenciesAudit the supply chain — packages with malware or typosquatting and malicious third-party skills/rememberNote something in memory — for this project (decision, rule, what didn't work, pending) or for the user (all their projects)/resumeResume where the previous session left off — what was asked, what was touched, what was left half-done and the next step
Walls that work on their own
They fire on every action the agent takes, without it having to remember.
- Push, deploy and destructive commandsBlocksNothing reaches main or production without your approval; database wipes, rm ‑rf and resets are stopped.
guard.mjs - Supply chainBlocksBefore installing, it checks the package name (typosquatting, known malware); on commit, it reviews dependencies, skills and MCP servers.
supply-guard.mjs - SecretsBlocksReal keys and tokens do not go into the code; example ones do.
secrets-guard.mjs - Injection and XSSWarnsWarns when the code puts a variable into HTML, SQL or a command without escaping it.
security-guard.mjs - Done, with proofBlocksA task is not marked done without the evidence, what it is for and its devlog entry.
tarjeta-guard.mjs - Clean closeBlocksThe session does not close without the devlog, without verifying the code or without checking the UI on mobile.
stop-guard.mjs
What's new
v2.24.2Documentation fixes: the brand skill always regenerates the tokens with sync-senzu.mjs, and the security review points to the /dependencies command for the supply chainv2.24.1The whole documentation is also in English: besides the guides, every skill and every command has its translated page (the agent still reads the original)v2.24.0New walls: supply chain (malware/typosquatting), secrets in commits, injection/XSS when editing and pentesting scope; /security skill (OWASP and AI agents); N+1 warning and TanStack for tables and lists
What comes with Senzu v2.24.2
Counted from the repository every time the site is published: if Senzu grows, these numbers change on their own.
Install it in two minutes.
Pick where you work. The installer detects the stack and asks about the rest.
Claude Code
plugin + full project install> /plugin marketplace add petersonsenadevs/senzu > /plugin install senzu-all@senzu > /install
Codex
marketplace from the app- In the Codex app: Customize → Plugins.
- Add → Add marketplace.
- In Source, paste the repository URL. Leave «Git reference» and «Sparse paths» empty.
- Install senzu-all and approve the hooks when Codex asks.
https://github.com/petersonsenadevs/senzuSee where it is

From a terminal? Clone the repository and run node senzu/tools/init.mjs --stack <stack> --path . --tools codex
Interactive installer
everything, by category or custom$ git clone https://github.com/petersonsenadevs/senzu.git $ node senzu/tools/init.mjs
Requirements, updates and every option in the install guide.
New or inherited project: start with a method.
After installing, every step is a command. You can also ask in plain words: the router knows which one applies.
New project
From the idea to the first task, without writing code blindly.
/briefPlain-language discovery interview — for clients who don't know the technical jargon/proposalsProposal mode — an approvable blueprint + 2 visual A/B mockups before building/design-systemGenerate (or review) the project's design system with ui-ux-pro-max/planCreate or resume the project plan (senzu/plan/PLAN.md) with the project-planner skill/nextRun the next task in the plan (project-planner task-protocol)
Existing project
Senzu learns how it is built before touching anything, and writes like it.
/adoptAdopt the conventions of an existing project and seal them as an immutable rule/mapProject map — what it is, how to run it, structure, critical flows and where to touch for each thing/auditBackend and architecture audit with proof — real tools, evidence per finding, report and plan/planCreate or resume the project plan (senzu/plan/PLAN.md) with the project-planner skill
One seed. One command.
Your project, in order from the next session: rules, memory and walls that really block.
/plugin marketplace add petersonsenadevs/senzu