agentleFS
Sign inStart free
jihe520jihe520/mindpocket/.agents/skills/ai-elements/SKILL.md

ai-elements

Skill349 starsChanged 7 months agoNo licenceView on GitHub

Create new AI chat interface components for the ai-elements library following established composable patterns, shadcn/ui integration, and Vercel AI SDK conventions. Use when creating new components in packages/elements/src or when the user asks to add a new component to ai-elements.

  • Reads credentials

We split this skill into the rules it gives an agent

13 rules. 9 are common, 0 are distinctive, and 4 are very specific to this project.

  • 9

    Common

    Most of the 26 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 4

    Very specific

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

No licence file, so all rights are reserved — read it at the source. We count its rules but don't quote them. Read them on GitHub.

“Common” is measured: kept by at least 6 in 10 of the 26 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.

  • Other versions29 projects use a version of this.

    Word for word · 1

    1. marian2js/opengoat★ 427100% same

    Edited · 23

    1. trycompai/crm★ 11k92% same
    2. zai-org/ZCode★ 7.9k88% same
    3. vercel/ai-elements★ 2.5k92% same
    4. xiaoiver/infinite-canvas-tutorial★ 1.1k100% same
    5. subhadeeproy3902/mvpblocks★ 83492% same
    6. mxyhi/ok-skills★ 50992% same
    7. oasm-platform/open-asm★ 26792% same
    8. ZCodium-project/ZCodium★ 24788% same
    9. mweinbach/agent-coworker★ 15692% same
    10. HamedMP/matrix-os★ 8292% same

    13 more not listed

    Wrote their own version · 5

    1. openai/plugins★ 7.4ksame name
    2. crafter-station/elements★ 524same name
    3. laguagu/claude-code-nextjs-skills★ 71same name
    4. trancethehuman/template-next-agent★ 2same name
    5. mm-mazhar/agent-skills-config★ 0same name

    How matches are found. Word for word: the exact same text. Edited: shares passages with this file (“99% same” means 99% of its five-word phrases also appear here; 10% or more counts). Their own version: similar meaning, or, weakest, the same name. We can’t tell which project had it first. Projects are counted among the 200 most-starred candidates, and mentions are links to the repository we found, up to 50 per site, so both counts are a floor.

  • Used alongsideProjects with it also use dep-refs, feature-boundary-planner and 7 more.

    Other files people use alongside this one.

    Files found in the same public projects as a version of this one, more often than they turn up anywhere else. Each project counts once, large collections count for less, and this file's own repository is left out.
    • betacatslingSkill

      dep-refs

      Use when needs to inspect TypeScript export references in the z-code workspace, list exports from a file, verify whether an export is unused before deletion, investigate who imports a symbol during refactors, or combine pnpm knip unused-export results with pnpm dep:refs symbol-level reference tracing.

      Also in 5 projects that use this

    • betacatslingSkill

      feature-boundary-planner

      Map a ZCode behavior change to current UI surfaces, state owners, protocol commands, persistence, and validation. Use for impact analysis, product-boundary planning, or an implementation handoff grounded in the checked-out source.

      Also in 5 projects that use this

    • Cartograf666Skill

      architecture-governance

      Bootstrap, document, enforce, and review a project's architecture through layer responsibilities, dependency direction, architecture manifests, legacy baselines, Change Envelopes, cross-layer approval policy, and deterministic architecture checks. Use when starting a project, auditing an existing codebase, planning cross-layer work, preventing architecture erosion, reviewing structural changes, or deciding whether implementation may expand into another layer.

      Also in 5 projects that use this

    • VercelSkill

      electron

      Automate Electron desktop apps (VS Code, Slack, Discord, Figma, Notion, Spotify, etc.) using agent-browser via Chrome DevTools Protocol. Use when the user needs to interact with an Electron app, automate a desktop app, connect to a running app, control a native app, or test an Electron application. Triggers include "automate Slack app", "control VS Code", "interact with Discord app", "test this Electron app", "connect to desktop app", or any task requiring automation of a native Electron application.

      Also in 5 projects that use this

    • SentrySkill

      next-best-practices

      Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

      Also in 5 projects that use this

    • VercelSkill

      next-cache-components

      Next.js 16 Cache Components - PPR, use cache directive, cacheLife, cacheTag, updateTag

      Also in 3 projects that use this

    • +1 more from vercel-labs
  • In this repository15 other files it gives its agents.

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

Reviews can't be read right now.

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