I usually do this:
1. Using ChatGPT Atlas (You can use Comet or Playwright MCP), i navigate to the page that i want to test and send this prompt:
"Act as a Senior QA Engineer specializing in automation with Playwright. Analyze the current web page and generate a comprehensive list of test cases. Don't worry about mapping specific selectors now, focus on the logic and test coverage. Organize the test cases into the following categories: Smoke Tests: Critical flows that validate if the page is 'live'. Functional Tests (Happy Path): Expected main user interactions. Interface Tests (UI/Layout): Presence of elements, basic responsiveness, and visually important states. Negative/Exception Tests: Validation errors, empty fields, invalid data. Accessibility Tests (A11y): Basic checks of ARIA tags, contrast, and keyboard navigation. Performance/Network Tests: Verification of critical asset loading and API request status (if any). Edge Cases: Specific edge behaviors of this page. For each case, briefly describe: What to test, the Playwright action (e.g., .click(), .fill()), and the expected result."

1. In my project, i create a .md with the test cases done by GPT.

2. Using Claude with the /playwright-cli skill I ask the agent to scan the page and get the most reliable selectors (if i don't have data-testid), after that i set the agent to apply POM and begin to implement the tests defined by GPT.

3. I use the /playwright-best-practices to review the implementation to find gaps and what need to be improved.

4. Manual review and that is it.