dotfusion-docs

These instructions apply to AI agents writing or editing engineering documentation for Dotfusion team.

Our team skills are distributed as a Claude Code plugin from this repo

This document defines how documentation should be written and maintained.

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Practical, copy-paste-ready patterns for common accessibility requirements. Each pattern is self-contained and linked from the main [SKILL.md](../SKILL.md).

Audit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".

Authoritative pointer to Dotfusion's engineering standards. Use before writing or changing application code, before opening a pull request, when adding or changing environment variables, when editing CI/CD or deployment config, when wiring observability, when recording an architecture decision, when changing UI (accessibility), when adding a dependency, or when a developer asks "what's our standard for X", "check this against our rules", or "is this the Dotfusion way". Lists every engineering standard, where to find it, and the non-negotiable rules that apply to every change.

Finish setting up a project cloned from the Dotfusion Next.js and AgilityCMS boilerplate. Use when the developer says "let's finish the install", "finish the setup", "set up this project", or right after cloning the template. Configures AgilityCMS environment variables, brand colors, fonts, and site metadata, then verifies the install.

Finish setting up a project cloned from the Dotfusion Next.js and Storyblok boilerplate. Use when the developer says "let's finish the install", "finish the setup", "set up this project", or right after cloning the template. Configures the Storyblok region, tokens, secrets, brand colors, fonts, and site metadata, then verifies the install.

Use when writing Playwright tests, fixing flaky tests, debugging failures, implementing Page Object Model, configuring CI/CD, optimizing performance, mocking APIs, handling authentication or OAuth, testing accessibility (axe-core), file uploads/downloads, date/time mocking, WebSockets, geolocation, permissions, multi-tab/popup flows, mobile/responsive layouts, touch gestures, GraphQL, error handling, offline mode, multi-user collaboration, third-party services (payments, email verification), console error monitoring, global setup/teardown, test annotations (skip, fixme, slow), test tags (@smoke, @fast, @critical, filtering with --grep), project dependencies, security testing (XSS, CSRF, auth), performance budgets (Web Vitals, Lighthouse), iframes, component testing, canvas/WebGL, service workers/PWA, test coverage, i18n/localization, Electron apps, or browser extension testing. Covers E2E, component, API, visual, accessibility, security, Electron, and extension testing.