team-conventions
Team code review conventions for ProVet Cloud frontend. Use when writing Vue components, composables, templates, or translations.
What this skill does
# Team Conventions
Coding patterns enforced during team code reviews. Apply when writing/modifying Vue components, composables, or translations.
## Nord Components
- Icon-only `<nord-button>` → add `square` prop; omit `size` on child `<nord-icon>` (inherits from button)
- Prefer CSS stack (`<div class="n:flex n:flex-col n:gap-m">`) over `<nord-stack>` component
- Prefer Tailwind classes (`n:flex n:flex-col n:gap-l`) over Nord layout web components
## Templates
- Emit directly in template unless handler has logic beyond the emit call
- No wrapper methods that only call `emit`
```vue
<!-- ✓ -->
<nord-button @click="emit('delete')">Delete</nord-button>
<!-- ✗ -->
<nord-button @click="handleDelete">Delete</nord-button>
<!-- where handleDelete() only calls emit('delete') -->
```
## Composables
- Params: `MaybeRefOrGetter<T>` + `toValue()` to unwrap
- TanStack Query keys: wrap in `computed()` when depending on reactive params
- API-only composables → `composables/api/ResourceName.ts`
- Domain logic composables → `composables/useResourceName.ts`
```typescript
// ✓
function useCatalogItems(
pagination: MaybeRefOrGetter<PaginationState>,
enabled?: MaybeRefOrGetter<boolean>,
) {
return useQuery({
queryKey: computed(() => keys.list(toValue(pagination))),
queryFn: () => fetch({ query: toValue(pagination) }),
enabled: toValue(enabled),
})
}
```
## Reuse Before Creating
Check existing composables before writing new ones:
- **`useAuth()`** → user-scoped departments/department groups (don't query all)
- **`useFiltersStateSync()`** → filter state + debounce (don't write manual watchers)
- **`useConsultationItemDisplay()`** → item type display/translation
## Translations
- Search `locales/en-US/application.json` for existing keys before adding new ones
- Common duplicates: "Items", "Name", "Account number", "Delete", "Edit", "Save"
- Use `tCommon()` for shared strings
## Utilities
- Shared helpers used in 2+ components → extract to `utils/` with unit tests
- Don't duplicate functions across Create/Edit modals
## Imports
- Don't use `#components` alias — use actual relative paths instead
- Refactor existing `#components` imports to relative paths when encountered
## TypeScript
- No unnecessary `as` casts when type already matches
- Trust inference
## Render Functions
Keep TanStack Table cell renderers simple — single element preferred.
```typescript
// ✓
cell: (props) => h('span', { style: { paddingLeft: `${level * 1.25}rem` } }, title)
// ✗ nested divs for simple indentation
```
## Pre-Review Checklist
- [ ] Icon-only buttons: `square` prop, no `size` on child icons
- [ ] No emit-only wrapper methods
- [ ] Composable params: `MaybeRefOrGetter` + `toValue()`
- [ ] Query keys: `computed()` when reactive
- [ ] Shared helpers in `utils/` with tests
- [ ] No duplicate translation keys
- [ ] Checked existing composables first
- [ ] API composables in `composables/api/`
- [ ] Tailwind over Nord layout components
- [ ] No unnecessary type casts
Related in Web Dev
generating-lwc-components
IncludedLightning Web Components with PICKLES methodology and 165-point scoring. Use this skill when the user creates or edits LWC components, builds wire service patterns, or writes Jest tests for LWC. TRIGGER when: user creates/edits LWC components, touches lwc/**/*.js, .html, .css, .js-meta.xml files, or asks about wire service, SLDS, or Jest LWC tests. DO NOT TRIGGER when: Apex classes (use generating-apex), Aura components, or Visualforce.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Set up queries with useQuery, mutations with useMutation, configure QueryClient caching strategies, implement optimistic updates, and handle infinite scroll with useInfiniteQuery. Use when: setting up data fetching in React projects, migrating from v4 to v5, or fixing object syntax required errors, query callbacks removed issues, cacheTime renamed to gcTime, isPending vs isLoading confusion, keepPreviousData removed problems.
document-processor-api
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
nutrient-document-processing
IncludedProcess documents with Nutrient DWS. Use when the user wants to generate PDFs from HTML or URLs, convert Office/images/PDFs, assemble or split packets, OCR scans, extract text/tables/key-value pairs, redact PII, watermark, sign, fill forms, optimize PDFs, or produce compliance outputs like PDF/A or PDF/UA. Triggers include convert to PDF, merge these PDFs, OCR this scan, extract tables, redact PII, sign this PDF, make this PDF/A, or linearize for web delivery.
tanstack-query
IncludedManage server state in React with TanStack Query v5. Covers useMutationState, simplified optimistic updates, throwOnError, network mode (offline/PWA), and infiniteQueryOptions. Use when setting up data fetching, fixing v4→v5 migration errors (object syntax, gcTime, isPending, keepPreviousData), or debugging SSR/hydration issues with streaming server components.
accelint-nextjs-best-practices
IncludedNext.js performance optimization and best practices. Use when writing Next.js code (App Router or Pages Router); implementing Server Components, Server Actions, or API routes; optimizing RSC serialization, data fetching, or server-side rendering; reviewing Next.js code for performance issues; fixing authentication in Server Actions; or implementing Suspense boundaries, parallel data fetching, or request deduplication.