Skip to content

improve synventis-vue-style #32

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
msladek wants to merge 1 commit into
base: dev
Choose a base branch
from
+14 −4
Open

improve synventis-vue-style #32

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
18 changes: 14 additions & 4 deletions skills/synventis-vue-style/SKILL.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -11,9 +11,11 @@ After changing relevant code, run available checks defined in `package.json` bef

## Localization

If the app uses localization:
- for new projects: place translation dictionaries under `@/conf/locale/`.
- for exisiting projects: reuse existing translation dictionaries, usually under `@/conf/locale/` or `@/locale`
If app uses localization, use dictionaries in `@/conf/locale/` or legacy `@/locale`.

## Vue

- Order SFC blocks: `<template>`, `<script>`, `<style>`.

## JavaScript and TypeScript

Expand All @@ -24,4 +26,12 @@ If the app uses localization:

## Styling

If the project uses Tailwind CSS, use it for all styling work. Avoid Vue `<style>` blocks or inline style attributes for CSS unless necessary.
In Tailwind projects, use it on Vue-owned elements, including states and pseudo-elements. Arbitrary properties and variants
are acceptable when concise and local.

Use `<style>` for third-party or legacy DOM, or when complex selectors are clearer than Tailwind.

Keep semantic class hooks only when consumed by JavaScript, CSS, or external code.

When static utilities exceed the line limit, use a `:class` array with the fewest reasonably packed strings. Keep dynamic
conditions separate.