Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make documentation available to LLMs by using llms.txt convention #1568

Open
YugoCode opened this issue Dec 19, 2024 · 4 comments
Open

Make documentation available to LLMs by using llms.txt convention #1568

YugoCode opened this issue Dec 19, 2024 · 4 comments
Labels
type: feature Introduction of new functionality to the application

Comments

@YugoCode
Copy link

YugoCode commented Dec 19, 2024

Describe the feature

It would be great to enable tools like Cursor to leverage shadcn-svelte’s documentation for generating more accurate and useful code. The Svelte team recently introduced support for LLMs (see https://svelte.dev/docs/llms) by adopting the llms.txt convention (https://llmstxt.org/), which allows LLM tools to parse documentation effectively. It would be awesome if shadcn-svelte could adopt this convention and ensure the llms.txt file stays updated whenever the documentation changes.

@YugoCode YugoCode added the type: feature Introduction of new functionality to the application label Dec 19, 2024
@good-dev-student
Copy link

or like https://svelte-llm.khromov.se/

@good-dev-student
Copy link

or like : https://llmctx.com/

@good-dev-student
Copy link

here can use: https://llmctx.com/shadcn-svelte idk if @huntabyte have plan to create an automated on in hist main svelte-shadcn website

@huntabyte
Copy link
Owner

Yeah, it's definitely in the plans once I get this stable release out. I'll remove all the extra components that I use in the markdown that aren't relevant and such.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature Introduction of new functionality to the application
Projects
None yet
Development

No branches or pull requests

3 participants