Perdolique
- 18 skills
- 0 followers
- 10 hours ago last updated
- ▌ Nuxt App · perdoliqueNuxt conventions for framework routing, middleware, SSR data fetching, Nitro handlers, request cancellation, runtime config, and typing. Use whenever work touches a Nuxt app or APIs such as `useFetch`, `useAsyncData`, `useRequestFetch`, `$fetch`, or `definePageMeta`, including requests framed only as Vue SSR or typed internal API work.
- ▌ Equipment Backend · perdoliqueEquipment and catalog backend conventions for the Perd project. Use this skill whenever the task touches `server/api`, `server/utils/validation`, `server/database/schema.ts`, Drizzle write paths, equipment reference data, contributions logging, or equipment API tests, even if the user does not explicitly mention the backend skill.
- ▌ Perd Vue Components · perdoliquePerd-specific Vue SFC conventions for imports and responsive styling. Use whenever creating or reviewing `.vue` files in Perd. Excludes framework routing and app-level data fetching.
- ▌ Pr Creator · perdolique bundleCreate or update GitHub pull requests from complete branch changes, or generate copyable PR content in chat. Use for requests to create, open, submit, show, draft, or write a PR or merge request.
- ▌ Code Review · perdolique bundleOrchestrate evidence-based code reviews through one compact reviewer or focused specialists. Use when the user or an automated process requests a code review.
- ▌ Drizzle Orm · perdolique bundleDrizzle ORM v1 beta query patterns for TypeScript. Use when writing, reviewing, or debugging Drizzle queries on `drizzle-orm@1.0.0-beta.1+`, especially with Relations v2, Relational Query Builder v2 (`db.query.*`), dynamic filters, SQL builder fallbacks, relation loading, and query-shape type mismatches. Also apply during code review when code contains non-trivial `drizzle-orm` usage.
- ▌ Markdownlint · perdolique bundleConfigure, manage, and troubleshoot markdownlint in projects. Use when user wants to setup/install/configure markdownlint, add/remove/modify linting rules, fix markdown validation issues, customize .markdownlint.yaml, update ignore patterns, integrate with tools (Husky, CI), or troubleshoot markdown linting errors. Use even when user mentions markdown formatting problems, quality issues, or style consistency without explicitly saying "markdownlint".
- ▌ Commit Creator · perdolique bundleCreate English conventional commit messages and commits from the current changes. Use when the user wants to commit code, asks for a commit message, or needs monorepo scopes and dependency updates represented accurately.
- ▌ Github Release · perdoliqueCreate or draft GitHub releases from existing tags and repository history. Use this whenever the user asks to publish a GitHub release, create release notes for a new version, mirror previous GitHub releases, release a tag/version, or says they have already released a new package version and need the matching GitHub release.
- ▌ Vue Components · perdolique bundleVue 3 + TypeScript component conventions for `.vue` SFC work. Use for Vue UI tasks that change component APIs/templates/styling/accessibility/composables/template refs/v-model or related component behavior. For Nuxt/Pinia/routing/E2E/Vitest tasks apply only to component-layer code and combine with the more specific local skill.
- ▌ CSS Conventions · perdoliqueCSS conventions for authoring and reviewing CSS, SCSS, CSS Modules, design tokens, and responsive layouts. Use whenever a task changes or reviews styling, regardless of framework.
- ▌ Repository Updater · perdolique bundleAnalyze repositories for available dependency, tooling, runtime, and infrastructure updates, aggregate changelogs across every version from the current version through each target, and report every direct candidate in structured Markdown with major-release highlights and repository-specific impact. Use for update discovery, dependency update analysis, release-impact and breaking-change review, or requests to update repository dependencies, tooling, runtimes, or infrastructure versions.
- ▌ Instructions Master · perdolique bundleCreate, edit, review, or evaluate reusable skills and other agent instructions. Use when changing what an agent should do, when guidance should apply, or how instruction sets interact. Do not use merely to follow existing instructions or edit ordinary documentation.
- ▌ Vitest Unit Testing · perdolique bundleWrite and maintain Vitest unit tests for TypeScript code. Use when the user needs unit coverage for utilities, services, or stores, or asks for Vitest-based tests with mocks, spies, and assertions.
- ▌ Cost Aware Development · perdolique bundleUse when planning, implementing, or reviewing a change that can materially affect infrastructure cost, metered usage, plan allowances, or subscription requirements in a project using Cloudflare, Neon, HIBP, or GitHub Actions. Confirm the provider is actually used or proposed from repository evidence and read only its matching reference. Skip unrelated changes and projects without covered services. Preserve correctness and user experience, and present material cost trade-offs before implementation.
- ▌ Playwright E2e Testing · perdolique bundleWrite and maintain Playwright end-to-end tests for web apps. Use when the user asks for browser or E2E coverage, or for tests covering pages, routes, redirects, navigation, dialogs, authentication, or multi-step user flows, even if they do not explicitly mention Playwright. Also use for API mocking, fixtures, and Playwright-specific assertions.
- ▌ Typescript Conventions · perdoliqueTypeScript coding conventions for writing, reviewing, and refactoring typed code. Use when working on `.ts`, `.tsx`, or files that embed TypeScript such as Vue, Astro, or Svelte components. Also use for TypeScript snippets, typed refactors, and review comments about code organization or function structure.
- ▌ Implementation Workflow · perdolique bundleUse when non-trivial coding work needs discovery or phased execution. Trigger for risky multi-file features, cross-cutting fixes, refactors, migrations, recovery, iteration plans, and PR-sized task splits. Skip simple edits and publication-only or review-only requests. Domain conventions belong to a more specific skill.