agentleFS
wrg32786wrg32786/aigent-design-system/skills/aigent-asset-gallery-system/SKILL.md

aigent-asset-gallery-system

Skill4 starsChanged 3 months agoMITView on GitHub

Build AIgent-style resource, prompt, repo, creator-stack, or operator-kit gallery pages with scroll chapters, sticky nav, mobile-safe reveals, plain-English descriptions, clickable external links, accurate counts, and premium 3D/Spline backgrounds.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    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:

    Use this skill for pages that present lists of assets: repos, prompts, tools, creator stacks, operator kits, skills, or templates.

    line 8
  2. Distinctive:

    Put a sticky top nav above the chapters.

    line 13
  3. Distinctive:

    Update both page copy and data source.

    line 24
  4. Distinctive:

    Put the diagonal arrow beside the title, inside the same link.

    line 39
  5. Distinctive:

    Do not create a dead icon button.

    line 40
  6. Distinctive:

    No horizontal page scroll.

    line 48
  7. Distinctive:

    Every external link opens.

    line 60

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

AIgent Asset Gallery System

Use this skill for pages that present lists of assets: repos, prompts, tools, creator stacks, operator kits, skills, or templates.

Structure

  1. Group assets into clear chapters.
  2. Put a sticky top nav above the chapters.
  3. On desktop, let the chapter header stick while the list scrolls.
  4. On mobile, do not use a second sticky chapter header; the top nav is enough.
  5. Cards reveal one at a time as the user scrolls.

Count Rule

Never overstate inventory.

  • Count cards from the rendered source.
  • Compare stated count to actual count.
  • Update both page copy and data source.

Copy Rule

Descriptions should explain why a normal operator cares.

Bad: Vision-first DOM abstraction for browser workflows.

Better: Lets an AI use websites even when normal automation breaks.

Card Rule

  • The card title should be linked if there is a URL.
  • Put the diagonal arrow beside the title, inside the same link.
  • Do not create a dead icon button.
  • Card click can expand details, but it must not block the title link.
  • Tags should be short and scannable.

Mobile Rule

  • Active nav chip centers itself.
  • Cards and headers appear early, not after the user has almost passed them.
  • No horizontal page scroll.
  • Body text stays readable.

Background Rule

The 3D scene is atmosphere and orientation. It should not make cards harder to read. Increase the dark veil behind dense lists.

Verification

Check:

  • Actual card count.
  • Every external link opens.
  • Mobile nav scrolls horizontally.
  • No sticky overlap.
  • First card in each chapter appears with the chapter intro.

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.