agentleFS
Sign inStart free
skyelan1999skyelan1999/aide/.agents/skills/aide-frontend/SKILL.md

aide-frontend

Skill4 starsChanged 31 days agoMITView on GitHub

Implement or inspect Aide browser UI, settings, styles, accessibility, localization, and file viewers. Load for frontend or visual interaction changes.

We split this skill into the rules it gives an agent

2 rules. About 0 are common, 0 are distinctive, and 2 are 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.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Read the relevant UI section in docs/architecture.md.

    line 8
  2. Very specific:

    Run focused node --check or repository UI scripts for changed files.

    line 10

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

Aide web UI

  • Read the relevant UI section in docs/architecture.md; source is internal/server/web/ (native JavaScript/CSS, not a separate frontend build system).
  • Trace existing state, persistence, localization, keyboard behavior, and responsive layout before editing. Keep shared components and translations consistent across supported locales.
  • Run focused node --check or repository UI scripts for changed files. For visible UI changes, open the actual page and verify the interaction at relevant sizes/themes; if unavailable, report NOT_RUN.
  • Go API or security changes belong to their matching specialist; coordinate API shapes explicitly rather than silently inventing them.

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.

Check your setup, free