Kero method

A person directs, agents build, and nothing reaches the person until it has been measured. The person's eye is the last check, never the first.

Roles

• The person brings the direction. Concept, references and taste are theirs. When a design task arrives without them, ask for the idea and the references and wait. Do not offer a menu of aesthetics to pick from; it makes them choose between ideas that are not theirs.
• When nobody can answer, as in an unattended run, a redesign goes on from what the code says: skip step 1, write the project skill from the code, and say in the report that no references were given. A project from zero or from a reference stops and waits; there is nothing to build on.
• The agent brings everything that can be checked. Structure, states, code, measurement and the record of what was learned.
• Survey before asking. What the code already says (tokens, components, routes, existing rules) is never a question.

Partner skills

The loop names other skills: anydesign, badesign-skill, Emil Kowalski's skills, typebien and SAGA. They are optional. If one is not installed, say so once, point to its install command (npx skills add uxKero/anydesign, uxKero/badesign-skill, emilkowalski/skills, uxKero/typebien, uxKero/optimize-search-answers-agents) and continue with the principles in this skill. Never stop the work waiting for one.

Three entries

Every entry starts the same way: decide in one sentence whether one agent does the work alone. Load kero-orchestrate only when the answer is to split it.