agentleFS
beeblockbeeblock/orkestrai/.claude/skills/svelar-specialist/SKILL.md

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.

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
  1. Distinctive:

    Use this skill for Svelar app work.

    line 8
  2. Distinctive:

    Keep the app flow consistent: route -> controller/page action -> FormRequest/shared schema validation -> DTO -> action/service -> …

    line 12
  3. Distinctive:

    Use both FormRequest classes and DTOs for write paths.

    line 13
  4. Very specific:

    Keep validation consistent with svelar.validation.json: Zod apps use z.infer from @beeblock/svelar/validation.

    line 14
  5. Distinctive:

    Use Svelar ORM and migrations.

    line 17
  6. Distinctive:

    Keep one migration per table or focused schema change.

    line 18
  7. Distinctive:

    Use Svelar CLI generators when available:

    line 22
  8. Very specific:

    Use Svelte 5 runes in .svelte: $props, $state, $derived, $effect, and {@render children()}.

    line 37
  9. Very specific:

    Do not use runes in .ts files.

    line 38
  10. Distinctive:

    Use shared schemas with Superforms when frontend and backend validation are shared.

    line 39
  11. Very specific:

    When hardening features, account for auth/session/API tokens, policies/permissions/teams, queues and workers, scheduler, events/listeners, …

    line 46
  12. Distinctive:

    Run focused tests after changes.

    line 50
  13. Very specific:

    Run npm run build before release-impacting work.

    line 51
  14. Very specific:

    Use npm run dev:worker and npm run dev:scheduler for local queue/scheduler checks.

    line 52

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

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

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 use z.infer from @beeblock/svelar/validation; Valibot apps use v.InferOutput and 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 CleanupTask

UI And Forms

  • Use Svelte 5 runes in .svelte: $props, $state, $derived, $effect, and {@render children()}.
  • Do not use runes in .ts files.
  • 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 build before release-impacting work.
  • Use npm run dev:worker and npm run dev:scheduler for local queue/scheduler checks.

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.