probe-conventionslisted

# Skill: probe-conventions Every other skill in this pack is deliberately convention-free: it asks the repository how it writes tests rather than telling it. This skill is where that answer comes from. The output is `.claude/test-profile.md` — a short, factual description of *this* suite. It is not a style guide and not aspirational. If the repo does something you would not recommend, record what it does, then note the disagreement in the `Frictions` section. Skills follow the record; humans decide about the frictions. ## When to run - First contact with a repository. - A skill in this pack stopped and told you the profile is missing. - The suite was restructured, renamed, or migrated (new runner config, new directory layout). - The profile's `Probed` date is older than the last significant refactor. ## Procedure Work from evidence in the repo. Never fill a field by guessing — an unknown field is written as `unknown` and the skills will ask the user at the point they need it. ### 1. Confirm this is a Playwright suite at all Look for a Playwright config (`playwright*.config.*`) and `@playwright/test` in the manifest. If neither exists, stop and say so — the rest of this pack does not apply. ### 2. Find the tests, and let them tell you the taxonomy Locate spec files by extension convention (`*.spec.*`, `*.test.*`) and group them by directory. Read **three** specs from each group, not one — a single file is an anecdote. For each group, record what kind of test it is b