ddd-architecture
DDD component architecture for Vue/Nuxt projects — folder structure, naming conventions, translation keys, and component organisation. Use when creating components, choosing file paths, naming files, structuring translations, or organising domain folders.
What this skill does
# DDD Component Architecture
Domain-driven folder structure and conventions for Vue/Nuxt component organisation. Apply when creating, moving, or renaming components and translation keys.
## Structure
Path: `components/[Domain]/[Feature]/[Function]/`
File: `[Name].vue` (short names, Nuxt auto-generates full path prefix)
Kebab folders — Nuxt handles PascalCase resolution.
## Hierarchy
1. **Domain** - business vertical (`patient-care`, `records`, `inventory`, `catalog`, `calendar`, `reporting`, `settings`)
2. **Feature** - logical module (`plans`, `laboratory`)
3. **Function** - UI pattern (`form`, `list`, `card`, `chart`, `dialog`, `menu`)
4. **Component** - the Vue file
## Function Types
| Function | Purpose |
| ---------------------- | -------------------------- |
| `form/`, `form/fields` | inputs, fieldsets, wizards |
| `list/` | tables, rows, grids |
| `card/` | summaries, widgets |
| `chart/` | visualisations, graphs |
| `dialog/` | modals, drawers |
| `menu/` | context menus, dropdowns |
## Examples
| Path | Filename | Nuxt Component Name |
| ------------------------------- | ------------ | ---------------------------------- |
| `patient-care/plans/list/` | `Active.vue` | `PatientCarePlansListActive` |
| `patient-care/laboratory/card/` | `Result.vue` | `PatientCareLaboratoryCardResult` |
| `inventory/stock/actions/` | `Adjust.vue` | `InventoryStockActionsAdjust` |
## Rules
- Simple forms can be contained directly within dialog components
- Extract forms to `form/` only when reused across multiple dialogs or contexts
- Generic components (`StatusBadge`) — `base/` or `ui/`
- Domain-specific shared components stay in primary domain, imported elsewhere
- No barrel files (`index.ts`) in domain folders — direct imports only
## Creating Components
Before creating, verify:
1. **Path provides context** — folder structure determines the full component name
2. **Short descriptive filename** — `Active.vue`, `Result.vue`, `Adjust.vue`
3. **No generic names** — never `Main.vue`, `Default.vue`, `Component.vue`
4. **Correct function folder** — form logic in `form/`, not `dialog/`
5. **Single responsibility** — one component = one purpose
6. **Import direction** — lower domains can import from higher, not reverse
## Translations
Translation keys follow the same structure as file paths. Use dots instead of hyphens.
**Path:** `pages.[domain].[feature].[function].*`
**Folder path to translation path:**
- `components/inventory/stock-locations/` — `pages.inventory.stock.locations`
- `components/patient-care/plans/` — `pages.patientCare.plans`
**Structure:**
```json
{
"pages": {
"inventory": {
"stock": {
"locations": {
"list": {
"header": "Stock Locations",
"createButton": "Add Location",
"filters": { "searchPlaceholder": "Search locations..." }
},
"form": {
"createTitle": "Create Stock Location",
"editTitle": "Edit Stock Location",
"nameLabel": "Name",
"cancel": "Cancel",
"validation": { "nameRequired": "Name is required" }
},
"toast": {
"create": {
"success": "Stock location created",
"error": "Failed to create"
},
"edit": {
"success": "Stock location updated",
"error": "Failed to update"
},
"delete": {
"success": "Stock location deleted",
"error": "Failed to delete"
}
}
}
}
}
}
}
```
**Usage in components:**
```typescript
// Single translation variable scoped to feature
const t = useTranslation('pages.inventory.stock.locations')
// Access nested keys via dot notation
t('list.header') // "Stock Locations"
t('list.createButton') // "Add Location"
t('form.nameLabel') // "Name"
t('form.validation.nameRequired') // "Name is required"
t('toast.create.success') // "Stock location created"
t('toast.edit.error') // "Failed to update"
```
**Function categories match component folders:**
| Function | Purpose |
| -------- | ----------------------------------------------------------------------------- |
| `list` | Headers, buttons, filters, column labels for list views |
| `form` | Labels, titles, buttons, validation for forms |
| `toast` | Success/error notification messages (nested by action: create, edit, delete) |
| `dialog` | Dialog-specific text (if needed beyond form titles) |
## Edge Cases
| Scenario | Resolution |
| ------------------------------------ | --------------------------------------------------------------------------------- |
| Component used by 2+ domains equally | `shared/[feature]/` |
| Form reused in multiple dialogs | Extract to `[...]Form.vue`, dialog imports form |
| Simple form in single dialog | Keep form inline within dialog component |
| Nested feature | `patient-care/laboratory/results/` — `PatientCareLaboratoryResults[Function].vue` |
| Page-level component | `pages/`, not `components/` |
| Composable | `composables/[domain]/use[Domain][Feature].ts` |
## Common Translations Reference
Use `const tCommon = useTranslation('common')` for reusable strings:
| Key | Values |
| ------------------------ | ------------------------------------------------------------------------------------------------------------------------------------- |
| `generalActions.*` | save, cancel, delete, edit, add, update, archive, retry, search, confirm, restore, back, continue, apply, clear, goBack, share, print |
| `generalStatuses.*` | active, archived, draft, sent, sending, open, created, creating, ready, rejected, updated, ongoing, all, loading |
| `boolean.*` | yes, no |
| `dateAndTime.*` | date, time, hour, startDate, endDate, years_one/other, months_one/other, days_one/other |
| `dataTable.columns.*` | id, date, name, email, phone, status, actions, firstName, lastName, client, veterinarian, clinic |
| `dataTable.emptyState.*` | header, description, descriptionNoMatches, buttonClearFilters |
| `generalFormFields.*` | email, phone, tags, remarks, reasonType, reason, veterinarian, department |
| `enums.*` | invoiceStatus, invoicePaymentStatus, invoiceType, paymentMethod, patientSex, consultationTypes, consultationStatus |
**Example usage:**
```ts
const tCommon = useTranslation('common')
tCommon('generalActions.save') // "Save"
tCommon('generalActions.cancel') // "Cancel"
tCommon('boolean.yes') // "Yes"
tCommon('dataTable.columns.name') // "Name"
```
Related in Design
contribute
IncludedLocal-only OSS contribution command center. Auto-refreshes the user's in-flight PR and issue state on invoke so conversations start with full context — no need to brief Claude on what's in flight. Helps the user find issues to contribute to on GitHub, builds per-repo dossiers of what each upstream expects (CLA, DCO, branch convention, AI policy, draft-first, review bots, issue templates), runs deterministic gates before any external action so AI-assisted contributions don't reach maintainers as slop. State is markdown-only: candidate files at ~/.contribute-system/candidates/, repo dossiers at ~/.contribute-system/research/, append-only event log at ~/.contribute-system/log.jsonl. No database, no cloud calls. Use when the user asks about their PRs / issues / contributions, wants to find new work to take on, claim an issue, build/refresh a repo's dossier, or draft a Design Issue or PR. Trigger with "/contribute", "what's my PR status", "find a contribution", "claim issue X", "draft a Design Issue for Y", "refresh dossier for Z".
architectural-analysis
IncludedUser-triggered deep architectural analysis of a codebase or scoped subtree across eight modes — information architecture, data flow, integration points, UI surfaces, interaction patterns, data model, control flow, and failure modes. This skill should be used when the user asks to "diagram this codebase," "map the architecture," "show the data flow," "give me an ERD," "trace control flow," "find the integration points," "verify the layout pattern," "audit the UX architecture," or any similar request whose primary deliverable is mermaid diagrams plus cited reports under docs/architecture/. Dispatches haiku/sonnet sub-agents in parallel for per-mode exploration, then verifies every citation mechanically before any node lands in a diagram. Not for one-off prose explanations of code (use code-explanation) or for high-level system design from scratch (use system-design).
mcp
IncludedModel Context Protocol (MCP) server development and tool management. Languages: Python, TypeScript. Capabilities: build MCP servers, integrate external APIs, discover/execute MCP tools, manage multi-server configs, design agent-centric tools. Actions: create, build, integrate, discover, execute, configure MCP servers/tools. Keywords: MCP, Model Context Protocol, MCP server, MCP tool, stdio transport, SSE transport, tool discovery, resource provider, prompt template, external API integration, Gemini CLI MCP, Claude MCP, agent tools, tool execution, server config. Use when: building MCP servers, integrating external APIs as MCP tools, discovering available MCP tools, executing MCP capabilities, configuring multi-server setups, designing tools for AI agents.
react-native-skia
IncludedDesign, build, debug, and optimise high-polish animated graphics in React Native or Expo using @shopify/react-native-skia, Reanimated, and Gesture Handler. Use when the user wants canvas-driven UI, shaders, paths, rich text, image filters, sprite fields, Skottie, video frames, snapshots, web CanvasKit setup, or performance tuning for custom motion-heavy elements such as loaders, hero art, cards, charts, progress indicators, particle systems, or gesture-driven surfaces. Also use when the user asks for fluid, glow, glass, blob, parallax, 60fps/120fps, or GPU-friendly animated effects in React Native, even if they do not explicitly say "Skia". Do not use for ordinary form/layout work with standard views.
plaid
IncludedProduct Led AI Development — guides founders from idea to launched product. Six capabilities: Idea (discover a product idea), Validate (pressure-test the idea against fatal flaws, problem reality, competition, and 2-week MVP feasibility), Plan (vision intake + document generation), Design (translate image references into a design.md spec), Launch (go-to-market strategy), and Build (roadmap execution). Use when someone says "PLAID", "plaid idea", "help me find an idea", "product idea", "idea from my business", "idea from my expertise", "plaid validate", "validate my idea", "pressure-test", "is this idea good", "find fatal flaws", "validate the problem", "plan a product", "define my vision", "generate a PRD", "product strategy", "plaid design", "design from image", "translate image to design", "create design.md", "extract design tokens", "plaid launch", "go-to-market", "launch plan", "GTM strategy", "launch playbook", "plaid build", "build the app", "start building", or "execute the roadmap".
nextjs-framer-motion-animations
IncludedAdds production-safe Motion for React or Framer Motion animations to Next.js apps, including reveal, hover and tap micro-interactions, whileInView, stagger, AnimatePresence, layout and layoutId transitions, reorder, scroll-linked UI, and lightweight route-content transitions. Use when the user asks to add, refactor, or debug Motion or Framer Motion in App Router or Pages Router codebases, especially around server/client boundaries, reduced motion, LazyMotion, bundle size, hydration, or route transitions. Avoid for GSAP-style timelines, WebGL or 3D scenes, heavy scroll storytelling, or CSS-only effects unless Motion is explicitly requested.