Skip to content

loliveirawebdev/ligeirinho

v0.3.2

An opinionated, proportional development process for coding agents: clarify, short plan, screen preview, test-first build in small chunks, and a gated close.

build

Builds the approved ligeirinho feature chunk by chunk, each in the loop failing test → code → green tests → checklist on the diff → commit. Use after the plan (and preview) are approved, or for a small change.

clarify

Asks the product questions before planning, one at a time, with a recommendation and options. Use at the start of a ligeirinho feature, or at any stage when a question comes up that changes the product, a rule, the contract or the experience.

close

Closes a ligeirinho feature - green gate, e2e for the journeys touched, review of the whole diff against the rules, feature note and updated area doc. Use once every build chunk is committed.

feature

Runs a whole ligeirinho feature (clarify → plan → preview → build → close). Use when the request brings a new rule, a new route, a new screen, touches more than one area or has an open product question, in a repository with .ligeirinho.yml. Don't use it for questions or small changes.

init

Sets up a repository to use ligeirinho - starts a new project from the template (scripts/init.sh), or in an existing one creates .ligeirinho.yml, enables the plugin for Claude Code, Codex and Antigravity, trims the agent instructions file and creates docs/areas and docs/features. Use when the user asks to adopt ligeirinho in a project (new or existing).

parallel

Splits the independent chunks of an approved ligeirinho plan across parallel sessions or subagents, each in its own git worktree, and merges them at the end. Use during the build when the plan has two or more chunks that don't depend on each other or touch the same files.

plan

Writes the short plan for a ligeirinho feature (domain rules, contract, screens, researched risks with sources, tests, parallel chunks) and asks the user to approve it. Use after clarify, before any code.

preview

Renders the feature's new screens in the project's previewer (/__preview) with their scenarios, side by side at 390/768/1280, light and dark, and asks the user to approve them. Use after the plan is approved when the feature has a new or changed screen.