agentleFS
Sign inStart free
openclawopenclaw/openclaw-enterprise/.agents/skills/console-ui/SKILL.md

console-ui

Skill454 starsChanged 8 days agoMITView on GitHub

Build or change Enterprise Console pages, shared styles, and interactions using the existing browser components and Storybook.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    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:

    Start with the Console components and styles.

    line 8
  2. Distinctive:

    Keep permissions, request outcomes, and recovery in the feature that owns them.

    line 11
  3. Distinctive:

    Follow the repository's visual review requirements and local development workflow.

    line 13

≈ “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.

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

Change the Console UI

Start with the Console components and styles. Find the closest production page and its Storybook story before adding a component. Change a shared pattern at its source and inspect it on the pages that use it. Keep permissions, request outcomes, and recovery in the feature that owns them.

Follow the repository's visual review requirements and local development workflow.

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