agentleFS
season179season179/season-claude-plugins/ai-elements/SKILL.md

ai-elements

Skill1 starsChanged 11 months agoNo licenceView on GitHub

Provides React components and hooks for building AI chat interfaces with Vercel AI SDK. Covers useChat, useCompletion, useObject hooks for state management, plus pre-built UI components (Conversation, Message, PromptInput, Response, Tool, Reasoning) from shadcn/ui. Triggers on chatbots, conversational UIs, AI assistants, streaming responses, message.parts rendering, tool call UIs, generative UI, sendMessage, DefaultChatTransport, or production AI interface patterns with Next.js.

  • Installs packages

36 other projects use a version of this.

Adopted by

Most recently taken up by

Used with

Projects with it also use dep-refs, feature-boundary-planner and 10 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.
  • axiom-desuSkill

    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 6 projects that use this

  • axiom-desuSkill

    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 6 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 6 projects that use this

  • crafter-stationSkill

    create-element

    Create new UI elements for tryelements.dev registry. Use when: (1) Adding new UI components (buttons, inputs, cards), (2) Building integration components (Clerk, Stripe, Uploadthing), (3) Creating theme-related elements, (4) Any shadcn-style registry component. IMPORTANT: For logo components with variants (icon/wordmark/logo + dark/light), use the logo-with-variants skill instead. This skill includes scaffolding, registry schema, and component patterns. ALWAYS use Context7 MCP to fetch latest dependency docs before implementing.

    Also in 4 projects that use this

  • FracteraSkill

    ask-element

    Work skill. The architect wants an element of this node to check or find out something and you to bring the answer («попроси template проверить …», «узнай у auth …»), or wants you to start or close an element's agent yourself. Also when «агент элемента … сообщил, что закончил (надзор …)» wakes you after such a task.

    Also in 3 projects that use this

  • FracteraSkill

    audit-broken-characters

    Scan the whole project for BROKEN / REPLACEMENT characters in localized text — a control byte (e.g. 0x13) or U+FFFD or mojibake left where an accented letter belonged, which renders as a box (e.g. "Documentación" showing "Documentaci□n"). Use when the owner reports a square / wrong glyph in the UI or content, says "broken character", "weird symbol", "mojibake", "validate encoding", or after authoring multilingual content and before closing a content step. It SHIPS SILENTLY (the file still parses), so run the audit to catch it. One project-root script, nothing external needed.

    Also in 3 projects that use this

  • +5 more from Fractera

The file

We split this skill into the rules it gives an agent

1 rule. 0 are common, 0 are distinctive, and 1 is very specific to this project.

  • 0

    Common

    Most of the 34 edited versions we read keep these.

  • 0

    Distinctive

    This author's own choices. Worth a look.

  • 1

    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 34 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.

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.