AGilbertDev
@AGilbertDev
Public Skills
new-project
by AGilbertDev
Start a new personal project from the right template. Use when creating a new repo or bootstrapping a project from scratch.
a11y-checklist
by AGilbertDev
WCAG 2.2 AA checklist for Nuxt pages and Vue components, covering keyboard, focus, ARIA, contrast, media, forms, and structure. Use when a page or interactive component ships, or when keyboard or screen-reader behaviour is broken.
backend
by AGilbertDev
AGilbertDev's backend conventions for personal Nuxt/Nitro projects — database, validation, server routes, auth, and email. Use when working on server routes, the database layer, schemas, or auth in a personal project. Starting defaults, adjust per project.
frontend
by AGilbertDev
AGilbertDev's frontend conventions for Nuxt/Vue projects — component and composable choices, solution priority, icons, and page performance. Use when building UI, components, or pages in a personal Nuxt project, or when a page is slow and you need to find what is actually costing the time. Pairs with nuxt-conventions:styling for Tailwind and theming.
review-checklist
by AGilbertDev
How to review a diff against the Nuxt-stack conventions, with the severity scheme and the review-only quality items. Use alongside /code-review before a pull request, or when the user asks whether Nuxt code looks right.
seo-checklist
by AGilbertDev
On-page SEO checklist for Nuxt pages, covering useSeoMeta, structured data, sitemap, robots, Core Web Vitals hints, and hreflang. Use when a public page ships or the user asks to improve search visibility.
styling
by AGilbertDev
AGilbertDev's styling conventions and visual identity for Nuxt/Tailwind projects — semantic-token theming, Hanken Grotesk type, fluid clamp() sizing, dark mode, and accessible Nuxt UI components. Use when styling components or pages, building responsive layouts, matching the brand, or setting up a theme. Pairs with nuxt-conventions:frontend.
commit
by AGilbertDev
Commit and open a pull request the AGilbertDev way. Use when reviewed work is ready to land, at the last stage of the pipeline, or when the user says commit, push, or open a PR.
compliance
by AGilbertDev
AGilbertDev's universal privacy, security, and minimum-legal baseline for every project — Québec Law 25 + Charter of the French Language (Law 101/96), PIPEDA, GDPR/UK GDPR, US state laws, COPPA, CASL/CAN-SPAM, consumer protection, accessibility (WCAG/EAA), IP & asset licensing, and digital-sales tax. Security baseline — secrets, encryption, auth, dependency & input hygiene. Use when building anything that collects data, sends email, sells to consumers, uses third-party IP/assets, or needs legal pages/consent. REQUIRED baselines. Store-specific rules (Google Play, App Store) are PROJECT-level — see the project's PLAYSTORE.md, not this skill.
pipeline
by AGilbertDev
Build one feature through the spec-driven pipeline. Use for any feature, page, route, or non-trivial fix in a personal project. Spec approved in plan mode, then tests first, a hands-off build, browser verification, review, and an open pull request. Not for small fixes.
spec
by AGilbertDev
How to write and maintain a feature spec, with the template and the design principles every spec must check. Use at the spec stage of the pipeline, when the user asks for a spec, or when a feature changes and its spec must follow.
quebec-french
by AGilbertDev
Rules for writing Québécois French copy, including the U+00A0 no-break space before ? ! : ; and how to check it. Use before writing or reviewing any French UI copy, locale file, or French prose.
tutorial-mode
by AGilbertDev
Collaboration mode for learning-by-building. Use when AGilbertDev wants to learn a project rather than have it built for him. Teach step by step, point at the right tools, and do NOT write or edit the code for the user. This is an opt-in per-project mode, not an always-on convention.