wiluszdamian/cue
Playwright testing conventions for this repository: constitution, locators from .agent-kb, and the skill catalog that writes tests the way this team already writes them.
Wire this repository to Cue once: check the environment, choose agent targets, and install the constitution and scaffold. Use on a fresh repository, or when cue doctor reports errors.
Name the right Cue skill for the situation and stop. Use when you do not know where to start with testing this repository, or which of survey, extract, pin, compose or inspect applies.
Write or change a Playwright test in this repository. Obey the constitution, take locators from .agent-kb, and import fixtures from the single harness entry point. Use when adding or editing e2e, functional, or API tests.
Use the Cue plugin to write Playwright tests in this repository. Use when adding, changing, or reviewing e2e, functional, or API tests, looking up a selector, or resolving conflicting Playwright advice.
Read the product source and write its structure into .agent-kb/product — routes, endpoints, entities, roles, test ids. Use when the application's code is available alongside the test suite.
Audit an existing Playwright suite against the constitution, and report drift in the knowledge base and routes with no test. Use to assess a suite you inherited or have not checked in a while.
Turn a testing intent into a concrete set of test cases with data, tags and locator candidates. Use when you know what needs checking but the cases are not written down yet.
Find the real selector for an element from the project knowledge base, with its freshness and confidence. Use before writing any locator, and whenever a selector in a test looks uncertain.
Decide which source of Playwright advice governs a topic when two of them disagree. Use before following guidance that conflicts with this repository's rules, or when unsure whether a topic is Cue's at all.
Map the running application into .agent-kb/app-map by exploring it with playwright-cli. Use when the UI is not yet in the knowledge base, or when locators have gone stale.