agentleFS
Sign inStart free
themesbergthemesberg/flowbite-svelte/AGENTS.md

flowbite-svelte

AGENTS.md2.8k starsChanged 12 months agoMITView on GitHub

You can use the Flowbite-Svelte MCP server, where you have access to comprehensive Flowbite-Svelte component documentation. Here's how to use the available tools effectively: Use this FIRST to discover components by name or category. Returns component information including the documentation path. When asked about Flowbite-Svelte components, ALWAYS use this tool to locate the correct component before fetching documentation. Example queries: 'Button', 'CardPlaceholder', 'form checkbox' Lists all available Flowbite-Svelte components with their categories. Use this to discover what components are available…

Trending

Less talk lately.about the whole repository

Dec 2025: 0 mentionsJan 2026: 0 mentionsFeb 2026: 2 mentionsMar 2026: 0 mentionsApr 2026: 2 mentionsMay 2026: 8 mentionsJun 2026: 0 mentionsJul 2026: 4 mentionsAug 2026: 0 mentionsSep 2026: 0 mentionsOct 2026: 2 mentionsNov 2026: 1 mention
Dec 2025Jun 2026Nov 2026
Mentions a month of the themesberg/flowbite-svelte repository that our weekly crawl found. There is no adoption data for this file yet.

Who's talking about themesberg/flowbite-svelte

The biggest 5 of 51 mentions linking to the repository that our crawl found. Each line is their own headline.

See all 51

Talked about on GitHub and Stack Overflow (51 times).

On GitHub · 50

45 more on GitHub
  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,439 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository2 other files it gives its agents.

The file

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

5 rules. About 0 are common, 3 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

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

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

    Use this FIRST to discover components by name or category.

    line 7
  2. Very specific:

    When asked about Flowbite-Svelte components, ALWAYS use this tool to locate the correct component before fetching documentation.

    line 8
  3. Distinctive:

    Use this to discover what components are available or to help users explore component options.

    line 14
  4. Distinctive:

    After calling findComponent, use this tool to fetch the complete documentation including usage examples, props, and best practices.

    line 19
  5. Distinctive:

    Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns.

    line 24

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

You can use the Flowbite-Svelte MCP server, where you have access to comprehensive Flowbite-Svelte component documentation. Here's how to use the available tools effectively:

Available MCP Tools:

1. findComponent

Use this FIRST to discover components by name or category. Returns component information including the documentation path. When asked about Flowbite-Svelte components, ALWAYS use this tool to locate the correct component before fetching documentation. Example queries: 'Button', 'CardPlaceholder', 'form checkbox'

2. getComponentList

Lists all available Flowbite-Svelte components with their categories. Use this to discover what components are available or to help users explore component options.

3. getComponentDoc

Retrieves full documentation content for a specific component. Accepts the component path found using findComponent. After calling findComponent, use this tool to fetch the complete documentation including usage examples, props, and best practices.

4. searchDocs

Performs full-text search across all Flowbite-Svelte documentation. Use this when you need to find specific information that might span multiple components or when the user asks about features or patterns.

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.

Check your setup, free