‹ Back to apps
ui-consistency
Keeps new UI consistent with a project's existing pages. Your coding agent reads how they are built and writes new ones the same way.
What’s inside
10 skills- SkillaccessibilityFor what the end user sees — checks whether it can be read and used without a mouse (contrast, focus, keyboard reach, labels, text alternatives, target size, structure) against a standard. Use when asked whether a page meets an accessibility standard, or when the project states an accessibility requirement.
- SkilladjustingFor what the end user sees — prepares a fix or a small change to pages that already exist, at the positions a request names, on one page or on the pages it names, so they come out the way the project's other pages write them. Use when a page is fixed or tuned rather than built — a QA finding, a review comment, a screenshot with a note, a gap, size, colour or border to change, a label, a value, a field or a button — and no new page is asked for.
- SkillconventionsFor what the end user sees — counts what a project's pages do, so a convention is told apart from one page's habit. Use when a count of how the other pages write something is about to be recorded, or when a checker recounts a line of a checklist.
- SkilldecisionsFor what the end user sees — the order that settles how a page is written when the project disagrees with itself, and what waits on a person. Use when the request, a named page, a shared piece and the other pages do not all agree on how a page is written, or before anything is put to a person.
- SkilldesignFor what the end user sees — reads the design for a page where there is one, and where there is none agrees the page's shape with the person, as a tree of the project's own pieces, before any code; draws it only when asked. Use when a request comes with a design, a picture, a described screen or an older screen to port, when a new page has no page near enough to follow, or when somebody wants to see how a page will look before it is built.
- Skillfinding-patternsFor what the end user sees — finds how this project already builds that kind of page (the components its pages reuse, theme values, validation, error handling) and writes it as a checklist before any UI code. Use when anything the end user sees is built or changed — a page, screen, form or component — whether or not the request names a page to follow, and before a plan's first task that changes what the user sees is handed to anyone, whichever process wrote the plan.
- SkillimplementingFor what the end user sees — builds each page from its checklist, one page per task. Use when writing or changing UI and a checklist or UI plan exists, whether executing that plan page by page, refactoring a set of pages, or making a fix or a small change to pages that exist.
- SkillplanningFor what the end user sees — turns each page's checklist into a plan of one checkable task per page. Use when UI work spans several steps or pages (a new feature, a refactor of many pages), including when another planning skill is about to write that plan.
- SkillvaluesFor what the end user sees — how this project sets its values and elements — its theme, spacing, typography, and the element each role comes out as. Use when a phase needs a value or an element recorded, written or checked, or when somebody asks what the project's theme or scale is.
- SkillverifyingFor what the end user sees — a separate agent checks written pages against their checklist and the rest of the project, and reports what differs. Use when UI has been written, before calling it done or opening a PR, or when asked whether pages match ("does this match", "did I miss a page", a page that looks or behaves unlike its neighbours).