claude-web-studio / testing
CLAUDE.md4 starsChanged 45 days agoMITView on GitHub
This folder is the QA layer for the studio's skills/agents. It is not part of any project. Rules: the spec path comes from the catalog's spec:, never guessed; when evaluating an assertion, quote the skill/agent line; write results only after "May I write?"; never modify skills from a test mode (use /skill-improve for edits).
In this repository52 other files it gives its agents.
- CLAUDE.mdCLAUDE.md
- a11y-auditSkill
- adoptSkill
- api-contractSkill
- architecture-decisionSkill
- architecture-reviewSkill
- backlogSkill
- brainstormSkill
- changelogSkill
- code-reviewSkill
- collaboration-protocolSkill
- create-storiesSkill
- data-modelSkill
- dependency-auditSkill
- deploySkill
- design-systemSkill
- dev-storySkill
- docsSkill
- feature-specSkill
- game-conceptSkill
- hardenSkill
- helpSkill
- hotfixSkill
- impactSkill
- incidentSkill
- initSkill
- migrateSkill
- pentestSkill
- perf-auditSkill
- product-specSkill
- qa-planSkill
- refactorSkill
- release-checklistSkill
- retrospectiveSkill
- security-auditSkill
- setup-stackSkill
- skill-improveSkill
- skill-testSkill
- sprint-planSkill
- sprint-statusSkill
- stack-updateSkill
- startSkill
- story-doneSkill
- team-featureSkill
- team-gameSkill
- team-releaseSkill
- team-securitySkill
- tech-debtSkill
- test-setupSkill
- threat-modelSkill
- updateSkill
- ux-specSkill
The file
Files
Web Studio Testing Framework — instructions for Claude
This folder is the QA layer for the studio's skills/agents. It is not part of any project.
| File | Purpose |
catalog.yaml | Registry of every skill and agent: category/tier, spec: (authoritative path), last_* fields. Read first in any test mode. |
quality-rubric.md | Metrics per category (### <category>) and agent tier (### agents:<tier>). |
skills/<category>/<name>.md, agents/<tier>/<name>.md | Behavioural specs: 5 cases + protocol. |
templates/*.md | Templates for new specs. |
results/ | Output of /skill-test spec (gitignored). |
Rules: the spec path comes from the catalog's spec:, never guessed; when evaluating an assertion,
quote the skill/agent line; write results only after "May I write?"; never modify skills from a test
mode (use /skill-improve for edits).
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
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.