wires/hypnagaga
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

Update readme.md

Browse source
This commit is contained in:
Ben Aultowski 2026-02-25 20:57:24 -05:00
parent 2b4906b563
commit 24950f5e7b
4 changed files with 2 additions and 73 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

2
.cursor/debug.log
View file

@ -1,2 +0,0 @@
{"location":"ScrollerBase.svelte:effect","message":"snippet undefined","data":{"backgroundSnippetDefined":false,"foregroundSnippetDefined":false,"backgroundSnippetType":"undefined","foregroundSnippetType":"undefined"},"timestamp":1772067326985,"hypothesisId":"B"}
{"location":"ScrollerBase.svelte:effect","message":"snippet props check","data":{"backgroundSnippetDefined":false,"foregroundSnippetDefined":false},"timestamp":1772067326984,"hypothesisId":"A"}

7
.cursor/mcp.json
View file

@ -1,7 +0,0 @@
{
"mcpServers": {
"svelte": {
"url": "https://mcp.svelte.dev/mcp"
}
}
}

23
AGENTS.md
View file

@ -1,23 +0,0 @@
You are able to use the Svelte MCP server, where you have access to comprehensive Svelte 5 and SvelteKit documentation. Here's how to use the available tools effectively:
## Available MCP Tools:
### 1. list-sections
Use this FIRST to discover all available documentation sections. Returns a structured list with titles, use_cases, and paths.
When asked about Svelte or SvelteKit topics, ALWAYS use this tool at the start of the chat to find relevant sections.
### 2. get-documentation
Retrieves full documentation content for specific sections. Accepts single or multiple sections.
After calling the list-sections tool, you MUST analyze the returned documentation sections (especially the use_cases field) and then use the get-documentation tool to fetch ALL documentation sections that are relevant for the user's task.
### 3. svelte-autofixer
Analyzes Svelte code and returns issues and suggestions.
You MUST use this tool whenever writing Svelte code before sending it to the user. Keep calling it until no issues or suggestions are returned.
### 4. playground-link
Generates a Svelte Playground link with the provided code.
After completing the code, ask the user if they want a playground link. Only call this tool after user confirmation and NEVER if code was written to files in their project.

43
README.md
View file

@ -1,42 +1,3 @@
# sv
# hypnagaga
Everything you need to build a Svelte project, powered by [`sv`](https://github.com/sveltejs/cli).
## Creating a project
If you're seeing this, you've probably already done this step. Congrats!
```sh
# create a new project
npx sv create my-app
```
To recreate this project with the same configuration:
```sh
# recreate this project
pnpm dlx sv create --template minimal --types ts --add prettier eslint vitest="usages:component" sveltekit-adapter="adapter:static" devtools-json mdsvex storybook mcp="ide:cursor,vscode+setup:remote" --install pnpm .
```
## Developing
Once you've created a project and installed dependencies with `npm install` (or `pnpm install` or `yarn`), start a development server:
```sh
npm run dev
# or start the server and open the app in a new browser tab
npm run dev -- --open
```
## Building
To create a production version of your app:
```sh
npm run build
```
You can preview the production build with `npm run preview`.
> To deploy your app, you may need to install an [adapter](https://svelte.dev/docs/kit/adapters) for your target environment.
A website, powered by [`Svelte`](https://github.com/sveltejs/) and Reuters‘ [`graphic-components`](https://github.com/reuters-graphics/graphics-components), and [`Motion`](https://github.com/motiondivision/motion). Very much under construction.