config-plugin-example-check
Skill1 starsChanged 3 months agoNo licenceView on GitHub
Deterministically validate Expo config plugin examples in the docs against the real plugin option types in the monorepo's packages/. No LLM in the verdict path; the source of truth is the TypeScript type behind each plugin's ConfigPlugin<T>. MUST USE when the user says "config plugin check", "check config plugin examples", "plugin example drift", "are the config plugin examples right", or "/config-plugin-example-check".
In this repository9 other files it gives its agents.
- docs-componentsSkill
- docs-prSkill
- docs-writing-styleSkill
- skill-qualitySkill
- ide-screenshot-driftSkill
- docs-boxlink-auditSkill
- docs-eas-env-driftSkill
- docs-reviewSkill
- screenshot-auditSkill
The file
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.