agentleFS
sayurionishisayurionishi/playwright-scaffold/.claude/skills/config/SKILL.md

config

Skill1 starsChanged 3 months agoMITView on GitHub

Use when adding an environment variable, base URL, credential, or environment-driven setting, or when wiring multi-environment runs. Single source of truth for URLs and secrets.

  • Reads credentials

25 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use uninstall.

Other files people use alongside this one.

Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
  • AnthropicSkill

    uninstall

    Uninstall a community skill that was installed via the hub. Confirms before deleting files, refuses to touch first-party plugin skills, and logs every action. Use when the user wants to fully remove a community skill ("uninstall [skill]", "remove this skill") rather than just disable it.

    Also in 3 projects that use this

The file

We split this skill into the rules it gives an agent

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

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 3

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  • could be automatic: a setting could enforce it
  1. Very specific:

    Add new vars to env/.env.<env>.example (and your real env file) so the contract is documented.

    line 30
  2. Very specific:

    Read via appConfig.* (which reads process.env.* with ??

    line 31
  3. Very specific:

    Add a typed appConfig property only if the value is reused or needs a guard.

    line 33
  4. Distinctive:

    Never commit a real secret.

    line 34

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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

Config & Environments

URLs and credentials come from the environment, never hardcoded.

Loading

playwright.config.ts reads ENVIRONMENT (default dev) and loads env/.env.<environment> via dotenv. Files: env/.env.dev, .env.staging, .env.prod, .env.ci — all gitignored; only *.example is tracked.

ENVIRONMENT=staging npx playwright test     # loads env/.env.staging

Where a value belongs

ValueHome
Base URL, API URL, credentials, env-driven settingprocess.env.*, surfaced via config/app.config.ts
Endpoint path, route, UI messageenums/ (NOT config)

Rules

  • BASE_URL is the app ROOT only — never bake in a path (e.g. .../todomvc), or a goto('/') drops it. Path segments belong in enums/util/routes.ts; navigate to them.
  • Add new vars to env/.env.<env>.example (and your real env file) so the contract is documented.
  • Read via appConfig.* (which reads process.env.* with ?? fallback or the required() guard). Never process.env.X as string.
  • Add a typed appConfig property only if the value is reused or needs a guard; otherwise read process.env.* directly.
  • Never commit a real secret. Never print a credential to the console/report.

CI

CI=1 is set in GitHub Actions; appConfig.isCI and playwright.config.ts use it to enable retries and the GitHub reporter. Replay CI locally: npm run test:ci.

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.