idavidov13idavidov13/agentic-playwright/.agents/skills/common-tasks/SKILL.md

common-tasks

Skill268 starsChanged 10 days agoMITView on GitHub

Use when the user wants a prompt template ("give me a prompt for X", "how do I add a page object, test, schema, factory, fixture or component") or the post-codegen verification checklist. Not for building the artifact directly (see `ai-native-workflow`, which routes that to the leaf skill).

1 other project uses a version of this.

Adopted by

Most recently taken up by

trezor/trezor-suitetheir own version, first seen Oct 8, 2026

Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
trezor/trezor-suite★ 1.1ksame name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository35 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- ai-native-workflowSkill
- api-testingSkill
- configSkill
- data-strategySkill
- debuggingSkill
- enumsSkill
- fixturesSkill
- helpersSkill
- page-objectsSkill
- playwright-cliSkill
- pr-reviewerSkill
- refactor-valuesSkill
- selectorsSkill
- skill-creatorSkill
- test-standardsSkill
- type-safetySkill
- ai-native-workflowSkill
- api-testingSkill
- common-tasksSkill
- configSkill
- data-strategySkill
- debuggingSkill
- enumsSkill
- fixturesSkill
- helpersSkill
- page-objectsSkill
- playwright-cliSkill
- pr-reviewerSkill
- refactor-valuesSkill
- selectorsSkill
- skill-creatorSkill
- test-standardsSkill
- type-safetySkill

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 0 are distinctive, and 1 is very specific to this project.

≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.

Common
Distinctive
Very specific

Very specific:
Resolve {area} before filling any template: Run the row's ls and substitute the real folder name.
line 10

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.

Files

SKILL.md

Common Tasks

Critical

Resolve {area} before filling any template. Run the row's ls and substitute the real folder name; never guess it.
Templates are starters. The leaf skill in the row owns the rules; load it and follow it end to end instead of restating its rules in the prompt.
Walk references/verification-checklist.md after generating, also when routing skipped this skill and went straight to a leaf skill.

Procedure

Match the request to one row and run its ls:

Artifact	Template	Leaf skill	`ls` first
Page object	`references/templates/page-objects.md`	`page-objects`	`ls pages/`
Component	`references/templates/components.md`	`page-objects`	none
Functional, E2E or data-driven test	`references/templates/tests.md`	`test-standards`	`ls tests/`, `ls test-data/static/`
API test	`references/templates/tests.md`	`api-testing`	`ls tests/`, `ls fixtures/api/schemas/`, `ls enums/`
Zod schema	`references/templates/api-schemas.md`	`api-testing`, `type-safety`	`ls fixtures/api/schemas/`
Factory or static data	`references/templates/data.md`	`data-strategy`	`ls test-data/factories/`, `ls test-data/static/`
Fixture	`references/templates/fixtures.md`	`fixtures`, `helpers`	none

Open the template, copy the block, replace every [PLACEHOLDER] and {area}; none may remain.
Load the leaf skill; generate per its Critical block and Procedure.
Walk the checklist, then run npx playwright test <file>; red → debugging.

References

references/verification-checklist.md: after every generated artifact.
references/templates/page-objects.md: page object with or without exploration, add locators, add an action method.
references/templates/components.md: reusable component.
references/templates/tests.md: functional, E2E, data-driven and API tests.
references/templates/api-schemas.md: schema from the documentation, fallback capture, add fields.
references/templates/data.md: factory, static data set.
references/templates/fixtures.md: page-object fixture, helper fixture, fixture category.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

It worked
Partly
It didn't

What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free