web-dev
Skill1 starsChanged 3 months agoMITView on GitHub
TypeScript and Python web development: React, Vue or Svelte UI, Node and Python backends, accessibility audits, CI, deploy and rollback. Use for components, forms, API routes, migrations, WCAG, Dockerfiles, GitHub Actions.
1 other project uses a version of this.
Adopted by
Most recently taken up by
- charliesbot/skillstheir own version, first seen Sep 27, 2026
Other versions1 project uses a version of this.
Word for word · 0
None found.
Edited · 0
None found.
Wrote their own version · 1
- charliesbot/skills★ 1same name
How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.
In this repository12 other files it gives its agents.
- templates/AGENTS.mdAGENTS.md
- templates/CLAUDE.mdCLAUDE.md
- adversarial-reviewSkill
- architect-reviewSkill
- delivery-loopSkill
- fast-pr-workflowSkill
- orchestratorSkill
- post-merge-cleanupSkill
- qa-automationSkill
- security-reviewSkill
- see-it-liveSkill
- task-researchSkill
The file
We split this skill into the rules it gives an agent
2 rules. About 0 are common, 2 are distinctive, and 0 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
0
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 26
Match the project: Use its styling system, framework data layer, package manager and conventions.
- Distinctive: line 27
Reuse before writing: Search for the existing component, hook, util or route first.
≈ “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
Web dev
Load the reference that matches the work; a change spanning layers loads each one it touches.
| Work | Reference |
| Components, pages, hooks, state, styling, performance | references/frontend.md |
| Routes, middleware, data, async, logging, CI, deploy, rollback | references/backend.md |
| Accessibility audit of a page or flow against WCAG 2.2 AA | references/a11y.md |
Rules for every layer
- Types are not negotiable. TypeScript
strict, Python annotated and checked (mypy --strictorpyright). Noany,@ts-ignore,# type: ignoreoras unknown as Tto silence a checker; fix the type. - Validate at every boundary (request, response, storage, URL, env) with a schema (
zod,pydantic); inferred types come from the schema, not the reverse. - Match the project. Use its styling system, framework data layer, package manager and conventions; do not introduce a second one.
- Reuse before writing. Search for the existing component, hook, util or route first.
- Idempotent, loud, reproducible. Scripts fail on any unhandled error, run twice with the same result, and work from a clean checkout.
- Measure before optimizing. Profile, Lighthouse,
EXPLAIN ANALYZE; never cargo-cult memoization or indexes.
Hand-offs
- Auth, tokens, sessions, uploads, SSRF:
security-reviewbefore wiring them. - Writing or fixing tests:
qa-automation. Browser, HTTP or CLI journeys live in itsreferences/e2e.md. - Launching the app to prove a change:
see-it-live. - Design and boundary critique of the result:
architect-review.
Done means
Type-check, lint and tests pass; the feature was exercised in the running app on the golden path and the error states; for services, the endpoint was hit with a real payload and the response matches the schema; for migrations, forward and rollback ran against a real database copy; for UI, axe or Lighthouse ran on the changed pages. Type-check passing is not feature-correctness.
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.