thedaviddias

Review frontend code and live pages against the Front-End Checklist (380+ rules for accessibility, performance, SEO, security, HTML, CSS, JavaScript, images, i18n, privacy, testing) using the `frontendchecklist` CLI. Use when writing, reviewing, or shipping…

Use when auditing or improving any frontend codebase against the full Front-End Checklist rule corpus through one entry point.

Use when reviewing templates, rendered HTML, or shared components related to Create a custom 404 error page. Validate the final browser-facing markup, not just the source framework abstraction.

Use when auditing metadata, crawlability, structured data, or indexability related to Create a dedicated About page. Verify the rendered HTML and HTTP response rather than relying only on source files.

Use when reviewing component libraries, page flows, or CI pipelines that need repeatable accessibility checks. Automated testing is strongest at catching structural and attribute-level issues; it does not replace keyboard, screen reader, and manual UX testing.

Use when reviewing sign-in, sign-up, MFA, CAPTCHA, recovery, and re-auth flows. Evaluate the full authentication path, including error handling and backup methods, not just the primary login form.

Use when reviewing templates, rendered HTML, or shared components related to Make notifications accessible. Validate the final browser-facing markup, not just the source framework abstraction.

Use when reviewing rendered HTML, interactive components, or design-system patterns related to Use semantic table markup for screen readers. Check native semantics first, then inspect keyboard behavior, focus flow, accessible names, and screen-reader output…

Use when implementing help users understand their current location.

Use when implementing expand and collapse content sections.

Use when implementing user account configuration and preferences.

Use when implementing social activity and updates stream.

Use when implementing conversational AI chat interfaces.

Use when implementing handling AI-specific errors.

Use when implementing loading states for AI operations.

Use when implementing aI-powered autocomplete and suggestions.

Builds simple Three.js web apps with scene setup, lighting, geometry, materials, animation, and responsive rendering. Use when creating or prototyping 3D web scenes with modern Three.js (r150+).

Comprehensive guide for developing WebGPU-enabled Three.js applications using TSL (Three.js Shading Language). Covers WebGPU renderer setup, node materials, compute shaders, post-processing, and WGSL integration. Use when working with Three.js WebGPU, TSL…

Use when working with the 1Password CLI (`op` command) for secrets management, retrieving API keys, injecting secrets into development environments, or any task involving 1Password vault operations. Triggers on: "1password", "op command", "secrets…

Create algorithmic art using p5.js with seeded randomness and interactive parameter exploration. Use when users request generative art, algorithmic art, flow fields, or particle systems. Create original works rather than copying existing artists.

Helps users discover and install agent skills. Use when they ask "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities with installable skills.

A set of resources for writing internal communications in company-preferred formats. Use when asked to draft status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, or project updates.

Use when the user wants to work with PDF files, including text/table extraction, merging, splitting, rotation, watermarking, creation, form filling, encryption/decryption, image extraction, or OCR for scanned PDFs.

Use when designing or improving prompts, commands, hooks, skills, or sub-agent instructions, including output quality, reliability, and token efficiency.

Browser automation CLI for AI agents. Use when the user needs to interact with websites, including navigating pages, filling forms, clicking buttons, taking screenshots, extracting data, testing web apps, or automating any browser task. Triggers include…

Use when starting creative work (features, components, functionality, or behavior changes) to clarify user intent, requirements, and design before implementation.

Interact with GitHub using the `gh` CLI. Use when managing issues, PRs, workflow runs, or advanced API queries via `gh issue`, `gh pr`, `gh run`, and `gh api`.

Use when implementing features or fixing bugs with strict Test-Driven Development (TDD). Activate for coding tasks that require new functionality, refactoring, or comprehensive test coverage, especially when the user mentions TDD or Test Driven Development.

Use when testing invalid slug format validation.

Use when testing broken reference links.

Use when testing mismatched name validation.

Use when testing failures for bad slug formatting and mismatched names in intentionally broken fixtures.

Create or improve SOUL.md files for OpenClaw agents. Use when the user wants to design an agent personality, rewrite an existing soul, align SOUL.md with IDENTITY.md, or prepare a soul for publishing on souls.directory with optional frontmatter.

Discover public Goshuin Atlas temple, shrine, and goshuin catalogue records and plan culturally respectful visits in Japan. Use for saved-place reading, sacred-place discovery, nearby-place comparisons, goshuin research, named-site visit briefs, pilgrimage…