ui-consistency

What you can ask

• Add a returns page like the orders pageCopy

  · decisions skill

• Check whether our settings pages match each other
• Build the signup form the way our other forms are built

Skills

10 in the ChatGPT listing

• accessibilityFor 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.
• adjustingFor what the end user sees — prepares a change to one region of one existing page, so it comes out the way the project's other pages write that position.
• conventionsFor what the end user sees — counts what a project's pages do, so a convention is told apart from one page's habit.
• decisionsFor 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.
• designFor 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.
• Finding 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.
• implementingFor what the end user sees — builds each page from its checklist, one page per task.
• planningFor what the end user sees — turns each page's checklist into a plan of one checkable task per page.
• valuesFor 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.
• verifyingFor what the end user sees — a separate agent checks written pages against their checklist and the rest of the project, and reports what differs.