svelar-specialist
Skill27 starsChanged 13 days agoApache-2.0View on GitHub
Use when working in this Svelar app, including routes, controllers, DTOs, FormRequests, schemas, ORM models, migrations, policies, permissions, teams, queues, cache, storage, PDF, search, SSE/Soketi broadcasting, Docker, tests, or production hardening.
In this repository7 other files it gives its agents.
- AGENTS.mdAGENTS.md
- CLAUDE.mdCLAUDE.md
- design-taste-frontendSkill
- make-interfaces-feel-betterSkill
- orkestrai-releaseSkill
- web-design-guidelinesSkill
- orkestrai-releaseSkill
The file
Show its rules and text
We split this skill into the rules it gives an agent
14 rules. About 0 are common, 8 are distinctive, and 6 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈8
Distinctive · estimate
This author's own choices. Worth a look.
6
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Distinctive: line 8
Use this skill for Svelar app work.
- Distinctive: line 12
Keep the app flow consistent: route -> controller/page action -> FormRequest/shared schema validation -> DTO -> action/service -> …
- Distinctive: line 13
Use both FormRequest classes and DTOs for write paths.
- Very specific: line 14
Keep validation consistent with svelar.validation.json: Zod apps use z.infer from @beeblock/svelar/validation.
- Distinctive: line 17
Use Svelar ORM and migrations.
- Distinctive: line 18
Keep one migration per table or focused schema change.
- Distinctive: line 22
Use Svelar CLI generators when available:
- Very specific: line 37
Use Svelte 5 runes in .svelte: $props, $state, $derived, $effect, and {@render children()}.
- Very specific: line 38
Do not use runes in .ts files.
- Distinctive: line 39
Use shared schemas with Superforms when frontend and backend validation are shared.
- Very specific: line 46
When hardening features, account for auth/session/API tokens, policies/permissions/teams, queues and workers, scheduler, events/listeners, …
- Distinctive: line 50
Run focused tests after changes.
- Very specific: line 51
Run npm run build before release-impacting work.
- Very specific: line 52
Use npm run dev:worker and npm run dev:scheduler for local queue/scheduler checks.
≈ “Common” is an estimate: at least 1 in 5 of the 372,429 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
Svelar Specialist
Use this skill for Svelar app work. Svelar is Laravel-inspired on SvelteKit 2.
Architecture
- Keep the app flow consistent: route -> controller/page action -> FormRequest/shared schema validation -> DTO -> action/service -> repository -> model/resource -> response.
- Use both FormRequest classes and DTOs for write paths.
- Keep validation consistent with
svelar.validation.json: Zod apps usez.inferfrom@beeblock/svelar/validation; Valibot apps usev.InferOutputand may import Laravel-like rules from@beeblock/svelar/validation/valibot. - Side effects belong in actions/services and events/listeners, not scattered through pages.
- Cross-module reads should go through a narrow public application service/query/facade from the owning module and return plain DTO/contract data. Events are for side effects, not request/response queries.
- Use Svelar ORM and migrations. Avoid raw SQL unless it is a low-level infrastructure exception.
- Keep one migration per table or focused schema change.
CLI
Use Svelar CLI generators when available:
npx svelar make:entity Post --module posts --fields "title:string,body:text" --crud
npx svelar make:model Post --module posts
npx svelar make:migration create_posts_table
npx svelar make:controller PostController --module posts
npx svelar make:request CreatePostRequest --module posts
npx svelar make:action CreatePostAction --module posts
npx svelar make:job SendDigestJob
npx svelar make:task CleanupTaskUI And Forms
- Use Svelte 5 runes in
.svelte:$props,$state,$derived,$effect, and{@render children()}. - Do not use runes in
.tsfiles. - Use shared schemas with Superforms when frontend and backend validation are shared.
- Action results should follow Svelar resource shape:
{ data, meta }. - Render field errors inline. Avoid duplicate validation toasts for normal field errors.
- Mutating browser fetch calls must include the CSRF token header.
Runtime Coverage
When hardening features, account for auth/session/API tokens, policies/permissions/teams, queues and workers, scheduler, events/listeners, observers, cache, uploads/storage, PDF, search, mail, SSE/Soketi broadcasting, audit/logs, and exception handling.
Verification
- Run focused tests after changes.
- Run
npm run buildbefore release-impacting work. - Use
npm run dev:workerandnpm run dev:schedulerfor local queue/scheduler checks.
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.

