agentleFS
Zack-GroganZack-Grogan/agentos-foundation/.agents/skills/teach-impeccable/SKILL.md

teach-impeccable

Skill0 starsChanged 2 months agoMITView on GitHub

Capture a project’s durable design context and spatial invariants.

20 other projects use 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. 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • 0

    Common

    Most of the 20 edited versions we read keep these.

  • 4

    Distinctive

    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:

    Read app shell rules first: no hero/masthead, conventional footer, default card grid or permanent chat.

    line 6
  2. Distinctive:

    Read the spatial contract.

    line 9
  3. Distinctive:

    Ask only for missing domain, accessibility and aesthetic decisions.

    line 12
  4. Distinctive:

    Write project design guidance containing composition, typography, density, state and motion rules.

    line 13

“Common” is measured: kept by at least 6 in 10 of the 20 edited versions of this file we could read. “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

Read app shell rules first: no hero/masthead, conventional footer, default card grid or permanent chat; use contextual instruments and stable app windows.

Original AgentOS-specific procedure; not a vendored upstream skill. Read the spatial contract. Use visual grammar for styling and interactions for behavior; load only the relevant reference.

  1. Inspect current interface, audience and earlier approved choices.
  2. Ask only for missing domain, accessibility and aesthetic decisions.
  3. Write project design guidance containing composition, typography, density, state and motion rules.

Deliver changed artifacts or a concrete review with evidence. Preserve canonical state and permission boundaries. Do not make the screenshot more attractive by hiding real failures.

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.