agentleFS
Pdiamondz1Pdiamondz1/hma_project_foundation/.claude/skills/test-app/SKILL.md

test-app

Skill1 starsChanged 5 months agoNo licenceView on GitHub

Use when someone asks to "test my app", "add tests", "write tests", "does my app actually work", "check that my app works", or says "/test-app". Generates a real, runnable test suite (Vitest + Testing Library + Playwright + coverage) for the already-built web app in app/, and maps it to your charter's success criteria — each becomes an automated test or a flagged manual/metric note. Reads the built app/ and wiki/charter.md; one confirm gate; scaffolds fully OFFLINE (no keys, nothing installed). Extends an existing test setup rather than duplicating it. Offers the run — runs only the fast Vitest suite (unit + component) on an explicit yes (as build-app runs the dev server), never the Playwright browser download unprompted. Tier 0. Attended-only — never runs in the maintenance loop. Re-runnable. Zero-argument safe.

  • Reads credentials
  • Installs packages

4 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

12 rules. 0 are common, 1 is distinctive, and 11 are very specific to this project.

  • 0

    Common

    Most of the 4 edited versions we read keep these.

  • 1

    Distinctive

    This author's own choices. Worth a look.

  • 11

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 4 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.

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.