stack-svelte
Skill0 starsChanged 2 months agoMITView on GitHub
Implement and validate Svelte user interfaces using the repository's actual package manager, scripts, component conventions, type checks, and browser-test setup.
In this repository18 other files it gives its agents.
- AGENTS.mdAGENTS.md
- elixir-docsSkill
- feature-planSkill
- independent-reviewSkill
- multi-repo-changeSkill
- package-readinessSkill
- parallel-deliverySkill
- safe-refactorSkill
- security-reviewSkill
- stack-elixirSkill
- stack-nextjsSkill
- stack-phoenix-liveviewSkill
- stack-rustSkill
- systematic-debuggingSkill
- technical-writingSkill
- ui-validationSkill
- unslopSkill
- worktree-integrationSkill
The file
We split this skill into the rules it gives an agent
7 rules. About 0 are common, 6 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈6
Distinctive · estimate
This author's own choices. Worth a look.
1
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 12
Use the package manager selected by the checked-in lockfile/project policy.
- Distinctive: line 14
Prefer semantic HTML and accessible interactions.
- Distinctive: line 15
Keep server-only data and secrets out of browser bundles.
- Distinctive: line 16
Treat hydration, navigation, async loading, errors, and client/server boundaries as correctness concerns when applicable.
- Distinctive: line 17
Do not assume SvelteKit when the project is plain Svelte.
- Distinctive: line 21
Run the repository's scripts for formatting/linting, type checking, unit/component tests, build, and browser tests as applicable.
- Very specific: line 25
Do not substitute guessed commands such as npm test for the scripts declared by the project.
≈ “Common” is an estimate: at least 1 in 5 of the 350,495 skill 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.
Files
Svelte
Inspect package.json, lockfile, Svelte/SvelteKit configuration, TypeScript settings, lint/test configuration, and applicable AGENTS.md before selecting commands.
Working rules
- Use the package manager selected by the checked-in lockfile/project policy.
- Preserve established component, routing, data-loading, state, styling, and form conventions.
- Prefer semantic HTML and accessible interactions.
- Keep server-only data and secrets out of browser bundles.
- Treat hydration, navigation, async loading, errors, and client/server boundaries as correctness concerns when applicable.
- Do not assume SvelteKit when the project is plain Svelte.
Validation
Run the repository's scripts for formatting/linting, type checking, unit/component tests, build, and browser tests as applicable.
For user-visible changes, run ui-validation against the real application and inspect relevant console/network behavior.
Do not substitute guessed commands such as npm test for the scripts declared by the project.
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
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.