agentleFS
sayurionishisayurionishi/playwright-scaffold/.claude/skills/common-tasks/SKILL.md

common-tasks

Skill1 starsChanged 3 months agoMITView on GitHub

Use as the entry point when the request is a generic "how do I add X?" or "generate a prompt for Y", or when no other skill obviously matches. Routes to the right specialized skill.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈2

    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
  1. Distinctive:

    When the ask is generic, classify it and hand off to the specialized skill that owns the deep rules.

    line 8
  2. Very specific:

    If asked to produce a reusable prompt for a teammate/Copilot, write it to point at the relevant SKILL.md and the Constitution (CLAUDE.md …

    line 28
  3. Distinctive:

    Ask one clarifying question.

    line 34

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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 (router)

When the ask is generic, classify it and hand off to the specialized skill that owns the deep rules.

The user wants…Hand off toFirst move
Configure a fresh clonebootstrapcheck PROJECT.md exists
A page object / new screenpage-objectsls pages/, then explore
A functional UI testtest-standardssplit into behaviors
An e2e journeytest-standardsmap the journey in playwright-cli
API tests for an endpointapi-testingPhase-1 tool gate, then OpenAPI
Security / fuzzing testssecurity-testingenumerate input fields
A locator chosen/fixedselectorsexplore the live element
A flake fixedwait-strategy → debuggingclassify the wait
A Zod schema / kill an anytype-safetysource the contract
A factory / invalid datadata-strategyclassify the value kind
A fixture wiredfixturespage-object vs helper
An endpoint/route/message addedenumsverify live, then add
An env var / URL / secretconfigenv vs enums

Generate-a-prompt requests

If asked to produce a reusable prompt for a teammate/Copilot, write it to point at the relevant SKILL.md and the Constitution (CLAUDE.md §1), include the explore-first rule and the confidence gate, and list the hard stops that apply to that task.

If nothing matches

Ask one clarifying question. Don't guess a skill — wrong routing wastes a whole cycle.

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.