Plain text
Skill jovd83/playwright-skill/documentation/test_cases/plain_text
End-to-end Playwright skill pack for planning, authoring, debugging, documenting, and operationalizing test automation.
npx -y skills add jovd83/playwright-skill --skill plain_textAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
One thing to look at
- 1 stars1 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
What its author says it does
Copied from the file, not written here
Legacy Playwright-specific alias for plain-text case formatting. Prefer the standalone `test-artifact-export-skill` skill for lightweight narrative case output, and use this only when Playwright-local conventions must be preserved explicitly.
SKILL.md
1.5 KB, as published. Nobody here has run it
Playwright Plain-Text Documentation
Use this skill for low-overhead scenario documentation.
Output Contract
For each scenario, capture:
- the goal,
- the relevant setup or preconditions,
- the main execution flow,
- the expected outcome,
- any requirement reference or open question that matters.
Output can be a short paragraph or a flat bullet list, whichever is clearer for the material.
Writing Rules
- Keep the sequence easy to follow.
- Prefer user intent and expected behavior over implementation detail.
- Make assumptions visible instead of hiding them in prose.
- Do not add formal structure unless the user specifically wants TDD or BDD.