The 15 Nuxfire Stack Specialists

The 15 Nuxfire Stack Specialists encapsulate the core architectural patterns and runtime constraints of this repository.

1. fireskill-specialist-nuxt

• Focus: Nuxt 4, Nitro server engine, pages, layouts, route middleware, server routes, plugins, runtime configuration, and auto-imports.
• Key Knowledge: Nuxt 4 directory structure (apps/app), Nitro event handlers (defineEventHandler), useRuntimeConfig(), and multi-app orchestration.
• When to Load: When modifying routing, SSR behavior, Nuxt configuration, or Nitro server endpoints.

2. fireskill-specialist-nuxt-ui

• Focus: @nuxt/ui v4 component library (built on Reka UI and Tailwind CSS v4).
• Key Knowledge: Over 125 accessible components (UButton, UModal, UTable, UForm, UFormField, UInput), design tokens, app.config.ts UI extensions, and composables like useToast() and useOverlay().
• When to Load: When developing or updating .vue files, UI forms, modal dialogs, data tables, or interface layouts.

3. fireskill-specialist-nuxfire-layers

• Focus: Nuxfire domain layer architecture.
• Key Knowledge: Creating, registering, and composing modular domain layers (layers/), config.ts layer toggles, scripts/compose-layers.ts, layer manifests, and dependency boundaries between layers.
• When to Load: When adding a new functional layer or managing cross-layer imports and composition.

4. fireskill-specialist-trpc

• Focus: Type-safe end-to-end APIs via trpc-nuxt (tRPC v10).
• Key Knowledge: Router definition, procedures (publicProcedure, protectedProcedure, abilityProcedure, platformAdminProcedure, defined in apps/app/server/trpc/trpc.ts), input validation via Zod, context creation, and client consumption via useTrpcClient().
• When to Load: When authoring or modifying API procedures, routers, or client-side queries/mutations.

5. fireskill-specialist-drizzle

• Focus: Drizzle ORM with PostgreSQL over Cloudflare Hyperdrive.
• Key Knowledge: Schema declarations (pgTable), relations, migrations (bun run drizzle-kit generate), query building, and per-request useDB() client lifecycle.
• Critical Constraint: useDB() must be instantiated per-request and closed via ExecutionContext.waitUntil(closeDB()). Never cache database clients globally.
• When to Load: When modifying database schema, adding migrations, or writing database queries.

6. fireskill-specialist-nuxt-authorization

• Focus: Role-Based Access Control (RBAC) and permissions.
• Key Knowledge: Defining abilities with defineAbility, securing procedures with abilityProcedure, template protection using <Can>, and platform administrator access with platformAdminProcedure.
• When to Load: When implementing authorization checks, member permission scopes, or admin guards.

7. fireskill-specialist-openauth

• Focus: Independent authentication server via OpenAuth.js.
• Key Knowledge: Password, code, GitHub and Google providers, Cloudflare KV session storage (AuthKV), token verification, callbacks and credential rate limiting in apps/functions/src/auth.ts. The user MFA (TOTP) endpoints live in the app, not in that file; the specialist's reference describes them.
• When to Load: When modifying login flows, session handling, authentication providers, or auth cookies.

8. fireskill-specialist-pinia

• Focus: Client-side reactive state management via @pinia/nuxt.
• Key Knowledge: Store definition (defineStore), SSR hydration safety, storeToRefs, lazy loading, and syncing store state with tRPC queries.
• When to Load: When managing persistent client-side application state across views.

9. fireskill-specialist-cloudflare-workers

• Focus: Cloudflare Workers serverless runtime environment.
• Key Knowledge: Worker resource bindings, Cloudflare KV, R2 Blob storage (@nuxthub/core), Cloudflare Queues, Durable Objects, Cron Triggers, and Hyperdrive connection pools.
• Runtime Constraints: String durations (e.g. "120 seconds"), zero Node.js filesystem access, zero persistent background listeners, Windows path safety (avoid path.resolve() in worker handlers).
• When to Load: When writing background jobs, queue consumers, WebSockets, or Cloudflare resource bindings.

10. fireskill-specialist-sst

• Focus: Infrastructure as code via SST 4 (sst.config.ts, infra/*.ts).
• Key Knowledge: sst.config.ts, Cloudflare provider configuration, secret management, stage deployments, and custom domain routing.
• When to Load: When provisioning new Cloudflare infrastructure, configuring secrets, or diagnosing deployment pipelines.

11. fireskill-specialist-billing

• Focus: Payments and subscriptions in layers/billing, with Stripe and Paddle both active.
• Key Knowledge: Stripe Checkout (subscription mode) and the restricted cancel-only portal, Paddle.js checkout in the browser, webhook verification with a KV idempotency ledger, syncStripeSubscription, the exhaustive Stripe status map, and the Plan and Subscription tables.
• Not in the code: invoice history, plan change with proration, seat-limit alerts, LemonSqueezy (enum value only).
• When to Load: When changing checkout, webhooks, subscription status, plans, prices or the /admin/plans console.

12. fireskill-specialist-content-seo

• Focus: Blog posts, docs pages and their translations in apps/web, and the SEO metadata every page carries.
• Key Knowledge: The blog frontmatter contract in content.config.ts (lang, translations, updated, ogImage, authorType), the pure builders in app/utils/seo/content-seo.ts, hreflang and sitemap consistency, raster social covers generated from SVG (bun run generate:og), the bun run check:seo gate over the built HTML, and the rule that every post exists in en, pt-br and es (the blog index shows one card per post in the active language).
• Not in the code: per-locale blog URLs, single-language posts (the gate rejects them), runtime OG image generation, an RSS feed, lastmod for docs pages.
• When to Load: When writing or translating a post or a docs page, changing a page title, description, structured data, hreflang or sitemap, or adding a locale.

13. fireskill-specialist-web-performance

• Focus: What the browser downloads and runs on the public pages: JavaScript, images, fonts, third-party code and the Core Web Vitals (LCP, INP, CLS).
• Key Knowledge: The Nuxt 4.5 noScripts route rule and the defineLazyHydrationComponent strategies, the byte budgets and dated baselines of perf-budgets.json (a baseline only shrinks), the bun run check:perf gate over the built HTML, and the lab protocol for LCP (Lighthouse with applied throttling), because a byte gate cannot measure timings.
• Not in the code: field data for the site, an INP measurement, a page declared js: none (the shared header needs JavaScript), lazy hydration of the landing sections, and a CI job that runs the gate.
• When to Load: When changing what a public page ships to the browser (scripts, images, fonts, routeRules, hydration), when a page feels slow, or before adding a browser dependency.

14. fireskill-specialist-seo

• Focus: What Google and Bing require of any page so it can be crawled, indexed, shown and cited, as distinct from how posts and docs are authored (that is fireskill-specialist-content-seo).
• Key Knowledge: 301 lines in apps/web/public/_redirects instead of meta refresh pages, the drop-trailing-slash handling of the Web Worker, one canonical URL, a sitemap lastmod with date and time, structured data chosen per page and never dishonest (no FAQ or rating markup without grounds), the bun run check:seo gate with its --live audit of a running server, and IndexNow through bun run indexnow (a dry run unless the owner authorizes the submission).
• Not in the code: an IndexNow key file, Search Console or Bing Webmaster data, a production audit of the redirect fix, and Organization or SoftwareApplication markup on the home page.
• When to Load: When a URL is created, moved or removed, when a route rule, _redirects line or sitemap option changes, or when a page head or its structured data changes.

15. fireskill-specialist-copywriting

• Focus: Every text a human reads in the apps: landing and pricing copy, interface labels and buttons, errors, empty states, emails, notifications and legal text.
• Key Knowledge: The workflow (brief, voice of customer, messaging hierarchy, draft, claims, localisation in en, pt-br and es, a separate review), a library of 44 original patterns in classes A (no proof needed), B (needs a ledger record) and C (forbidden), the claim ledger .fireskills/CLAIMS.yml for numbers, testimonials and deadlines, and the bun run check:copy gate with its dated, owned baseline.
• Not in the code: a proven claim (the ledger is empty), voice-of-customer data, verified testimonials, and any test of the copy on real visitors.
• When to Load: When writing or changing any string a person reads, when a template contains a literal text, or when a page names a number, a comparison, a guarantee, a deadline or a person.