sbnet

nodejs-best-practices

Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.

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".

seo

Optimize for search engine visibility and ranking. Use when asked to "improve SEO", "optimize for search", "fix meta tags", "add structured data", "sitemap optimization", or "search engine optimization".

vite

Vite build tool configuration, plugin API, SSR, and Vite 8 Rolldown migration. Use when working with Vite projects, vite.config.ts, Vite plugins, or building libraries/SSR apps with Vite.

Data & Documents Listed

documentation

In-code documentation, folder READMEs, and code comments. Use when writing README.md files, JSDoc comments, or explaining code organization.

Code & Development Listed

git

Git commit guidelines using conventional commits. Use when creating commits, writing commit messages.

API & Backend Listed

nodejs-backend-patterns

Build production-ready Node.js backend services with Express/Fastify, implementing middleware patterns, error handling, authentication, database integration, and API design best practices. Use when creating Node.js servers, REST APIs, GraphQL backends, or microservices architectures.

spec-interview

Interview the user about a feature they want to build, then write a complete spec to specs/SPEC-<ref>.md (with an index). Use when the user says "I want to build X" or asks for a spec/interview. Once the spec is validated, chain into /gh-issue.

typescript-advanced-types

Master TypeScript's advanced type system including generics, conditional types, mapped types, template literals, and utility types for building type-safe applications. Use when implementing complex type logic, creating reusable type utilities, or ensuring compile-time type safety in TypeScript projects.

writing-voice

Voice and tone rules for all written content. Use when writing prose that should sound human and be suitable for reading aloud.

feature

The single entry point to build anything. Calibrates the process to the change (trivial, standard or full), then drives it end to end (spec, issue, implementation, gates, PR, CI, review triage). Only merging stays human. Use when the user asks to implement, fix or build something.

geo

Audit and improve visibility in generative engines (AI answers, LLM-powered search): GEO, complementary to classic SEO. Use when the user asks about GEO, AI search visibility, llms.txt, or being cited by AI assistants.

gh-pr

Write and open the pull request for the current branch via the gh CLI, linked to its issue and spec. Use when the user asks to create/open/write a PR.

init

Set up flux in the current project: config, gate script for CI, workflows, CLAUDE.md contract, specs index, GitHub label. Use when the user asks to initialize/install flux in a project.

Web & Frontend Listed

ui-review

Heuristic UI/UX review of the running app: screenshots at multiple breakpoints, state coverage, consistency, form ergonomics. Use when the user asks for a UI review, UX feedback, or a design pass on pages or flows.

gh-address-comments

Triage and address review comments on the current branch's PR: the human picks what to fix, the agent fixes it autonomously. Use when the user asks to handle/address review comments on a PR.

gh-issue

Write and create a well-structured GitHub issue via the gh CLI, optionally from a SPEC-<ref>.md spec. Use when the user asks to create a GitHub issue/ticket.

Code & Development Listed

gh-review

Trigger the automated GitHub review for the current branch's PR on demand, instead of waiting for it to fire on push. Use when the user asks to run/launch/trigger the review manually, especially when github.auto_review is false in flux-config.yml.

Code & Development Listed

review

Review the current branch's PR and post the findings as comments on it. Use when the user asks to run/launch/trigger a review, or the feature/gh-pr flow reaches the point where CI is green and a review is worth requesting before merge.