agentleFS
yehyakinyehyakin/hermes-skills/AGENTS.md

hermes-skills

AGENTS.md9 starsChanged 7 months agoMITView on GitHub

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices. <!-- END:nextjs-agent-rules --> This project follows Apple Liquid Glass design, defined in DESIGN.md. Key rules: - All UI lives in {components.glass-panel} — frosted glass with blur(28px) saturate(160%) - Single accent: cyan #0891b2 for all interactive elements - Status communicated via {components.status-pill} variants, never raw colored text - No box-shadows…

The file

We split this AGENTS.md into the rules it gives an agent

2 rules. About 0 are common, 1 is distinctive, and 1 is very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

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

    All UI lives in {components.glass-panel} — frosted glass with blur(28px) saturate(160%)

    line 12
  2. Distinctive:

    No box-shadows — depth comes from blur + translucency + inset highlights

    line 15

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
AGENTS.md
<!-- BEGIN:nextjs-agent-rules -->

This is NOT the Next.js you know

This version has breaking changes — APIs, conventions, and file structure may all differ from your training data. Read the relevant guide in node_modules/next/dist/docs/ before writing any code. Heed deprecation notices.

<!-- END:nextjs-agent-rules -->

Design System

This project follows Apple Liquid Glass design, defined in DESIGN.md.

Key rules:

  • All UI lives in {components.glass-panel} — frosted glass with blur(28px) saturate(160%)
  • Single accent: cyan #0891b2 for all interactive elements
  • Status communicated via {components.status-pill} variants, never raw colored text
  • No box-shadows — depth comes from blur + translucency + inset highlights
  • Body text at 14px, panel titles at 13px/600 with negative letter-spacing
  • Page background uses inline style={{ background: ... }} with radial-gradient, not Tailwind
  • API calls use /api/... prefix (Next.js rewrites to localhost:8787)
  • Time/date rendering uses ClientOnlyText to avoid hydration mismatches
  • Font: SF Pro via system-ui stack; fallback: Inter

See DESIGN.md for full token reference.

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.