Frontend change
Use when changing the UI — Inertia + Vue pages/components (or Blade/Livewire). Enforces the project's component conventions, design tokens, RTL rules, and i18n handling.From its SKILL.md
npx -y skills add yousefkadah/laravel-ai-kit --skill frontend-changeAssembled from the repository path, not quoted from the project. Check it against their README if it does not work.
2 things to look at
- 27 days oldThe repository was created 27 days ago. New is not bad, but a brand new repository carrying a familiar-sounding name is the shape a typosquat arrives in, and there has been no time for anyone else to find a problem with it.
- 0 stars0 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.
SKILL.md
1.3 KB, 296 tokens by cl100k_base, as published. Nobody here has run it
Frontend change
Before writing
- Read a sibling component and match its API style. «State the project's choice: Options API vs Composition API — and use it.»
- Reuse an existing component before building a new one.
- If the project has a
DESIGN.md/ design system, read it first and use its tokens/components.
While writing
- One root element per Vue component.
- Use design tokens (CSS variables), not invented inline hex values.
- RTL: use logical properties (
ms-*/me-*,ps-*/pe-*), neverleft/right/ml-*/pr-*. - i18n: add user-facing strings to the correct translation bundle(s) for all locales the project supports. «Note the frontend vs backend bundle split if your project has one.»
- Keep logic out of templates; no secrets or tokens in frontend code.
Before done
- Build/typecheck passes. If a change isn't visible, the dev may need
npm run dev/npm run build. - Add/update a test if the project tests components; otherwise verify in the browser and say so.
- Self-review against
.ai/code-review.md. Tight diff.
What ships with it
Read from the repository
Just SKILL.md. No reference files, no scripts.