agentleFS
FAHTHIZFAHTHIZ/oasis/skills/web-app-development/SKILL.md

web-app-development

Skill4 starsChanged 9 days agoApache-2.0View on GitHub

Implement complete accessible web experiences with responsive UI, robust state, and tested runtime behavior.

1 other project uses a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    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
  1. Distinctive:

    Treat every browser input and imported file as untrusted.

    line 11
  2. Distinctive:

    Keep credentials and privileged operations on a trusted runtime.

    line 12
  3. Distinctive:

    Add deterministic tests for logic and UI anchors.

    line 14
  4. Distinctive:

    Verify responsive and accessibility behavior with real browser/device checks when available.

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 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.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

Web app development skill

  1. Inspect the current routes, rendering approach, design tokens, build scripts, browser support, and existing tests before choosing a framework or adding dependencies.
  2. Trace the user flow end-to-end: entry point, loading state, success state, empty state, validation, error recovery, keyboard use, and narrow-screen layout.
  3. Reuse established visual patterns and shared components. Avoid introducing parallel implementations of the same feature.
  4. Treat every browser input and imported file as untrusted. Escape rendered content, validate schemas and sizes, and avoid unsafe HTML injection.
  5. Keep credentials and privileged operations on a trusted runtime. Browser code must not receive provider API keys, GitHub tokens, or server secrets.
  6. Make loading and asynchronous work visible, prevent duplicate submissions, handle stale responses, and provide actionable error messages.
  7. Add deterministic tests for logic and UI anchors; run the repository quality gate and inspect the final diff.
  8. Verify responsive and accessibility behavior with real browser/device checks when available; clearly state what was not tested.

Download now (ZIP)

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.