whitebox-e2e
Skill11 starsChanged 7 days agoMITView on GitHub
Guide for Whitebox End-to-End tests with the Neural Link Playwright fixture; use before writing, modifying, or running Playwright E2E tests, adding E2E coverage, or testing a component holistically.
In this repository39 other files it gives its agents.
- architecture-pre-flightSkill
- blocked-task-stateSkill
- blog-postSkill
- context-recoverySkill
- create-skillSkill
- design-sweepSkill
- epic-createSkill
- epic-resolutionSkill
- epic-reviewSkill
- goal-scopingSkill
- guide-authoringSkill
- hostile-content-quarantineSkill
- ideation-sandboxSkill
- identity-firewallSkill
- industry-friction-radarSkill
- lane-intentSkill
- lead-roleSkill
- memory-miningSkill
- neo-app-authoringSkill
- neo-identity-updateSkill
- neural-linkSkill
- overviewSkill
- peer-namingSkill
- peer-roleSkill
- post-review-pickupSkill
- pr-reviewSkill
- pull-requestSkill
- release-notesSkill
- self-repairSkill
- session-sunsetSkill
- structural-pre-flightSkill
- tech-debt-radarSkill
- ticket-createSkill
- ticket-intakeSkill
- ticket-triageSkill
- turn-memory-pre-flightSkill
- unit-testSkill
- update-roadmapSkill
- video-createSkill
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: line 7
If you are tasked with writing new End-to-End tests for Neo.mjs applications, you MUST immediately use the view_file tool to read and …
≈ “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.
Files
Whitebox E2E Testing Protocol
If you are tasked with writing new End-to-End tests for Neo.mjs applications, you MUST immediately use the view_file tool to read and strictly adhere to .agents/skills/whitebox-e2e/references/whitebox-e2e-protocol.md before planning your assertions or writing any test code.
CRITICAL: Neo.mjs uses Playwright in a highly custom way and standard Playwright patterns will fail; this protocol prevents brittle, visual-only DOM locator tests by utilizing the deep-state introspection capabilities of the Neural Link fixture.
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.