A companion web stack (Astro, Next.js, Vite/TanStack) and a Rust backend service layer alongside the mobile agents.
🚀
astro-web-expert
Astro specialist for public marketing/careers sites — SEO, OG, and islands.
astroseoislands
Capabilities
- Static-first architecture with selective per-route on-demand rendering
- Content Collections with Zod schemas for type-safe structured content
- Islands architecture with deliberate, minimal client-side hydration
- Open Graph/SEO metadata and JSON-LD structured data setup
- Multi-locale routing for international candidate-acquisition funnels
When to use
- Building a public marketing or careers/candidate-acquisition site with Astro
- Auditing SEO and Open Graph correctness across pages
- Setting up Content Collections for job listings, blog posts, or team bios
Source ↗
▲
nextjs-web-expert
Next.js + Tailwind + shadcn specialist for authenticated client consoles.
nextjsshadcnapp-router
Capabilities
- App Router architecture for authenticated internal/company consoles
- Server vs Client Component boundaries in data-heavy dashboards
- Server Actions and Route Handlers for console mutations
- shadcn/ui + Tailwind design systems; middleware-based route protection
- Type-safe forms with react-hook-form, zod, and Server Actions
When to use
- Building a new authenticated "firma konsolu" (company dashboard)
- Deciding the Server/Client Component line in a dashboard page
- Diagnosing stale dashboard data after a mutation
Source ↗
🎛️
admin-panel-architect
Vite + React 19 + TanStack + Supabase RLS specialist for operator panels.
tanstacksupabase-rlsrtl
Capabilities
- Vite + React 19 + TypeScript architecture for internal admin/operator panels
- TanStack Router/Query/Table wiring against Supabase (anon key + RLS only)
- Supabase Storage TUS resumable uploads for large operator-facing media
- Bilingual (TR/EN) i18n and RTL-readiness planning
- Static SPA deployment topology for EU CDN hosting (no SSR, no server secrets)
When to use
- Scaffolding a new internal admin/operator panel on this exact stack
- Deciding how authorization is enforced when the client only holds an anon key
- Reviewing whether a pattern leaks trust to the client in a service-role-free stack
Source ↗
🎭
web-e2e-testing-expert
Playwright E2E for Refine + TanStack Router + Supabase + shadcn web apps; Arrange/Act Supabase harness; official Playwright agents + MCP; cross-surface scenarios.
playwrightsupabasetanstack
Capabilities
- Playwright E2E for Refine + TanStack Router web apps
- Supabase Arrange/Act test-data harness (service_role provision, real-UI act)
- Official Playwright agents (Planner/Generator/Healer) + MCP live verification
- Cross-surface scenario authoring (admin <-> client-web)
- Ephemeral-Supabase CI wiring
When to use
- Setting up or extending E2E testing for a Supabase-backed React web app
- Writing cross-surface Playwright scenarios that must honor RLS
Source ↗
🖥️
desktop-expert
Cross-platform desktop specialist — Electron and Tauri IPC, packaging, and auto-update.
electrontauriipc
Capabilities
- Architecting cross-platform desktop apps with Electron (main/renderer) or Tauri (Rust core/webview)
- Designing secure IPC channels — Electron contextBridge + minimal allow-listed preload API; Tauri commands + capability allowlist
- Packaging and distributing per-OS artifacts (dmg, nsis, AppImage, msi) with electron-builder/electron-forge or Tauri bundler
- Wiring auto-update pipelines with cryptographic signature verification (electron-updater, Tauri updater with pinned pubkey)
- Implementing native OS integration — system menus, tray icons, global shortcuts, deep links / custom protocols
When to use
- Building a new cross-platform desktop app and deciding between Electron and Tauri
- Hardening an existing Electron app (nodeIntegration still on, no contextBridge, unvalidated IPC)
- Setting up auto-update with signature/integrity verification for an Electron or Tauri app
Source ↗
⚛️
web-frontend-expert
React + TypeScript SPA specialist — component architecture, state boundaries, and rendering.
reacttanstack-queryvite
Capabilities
- Designing component architecture for React + TypeScript SPAs (composition, container/presentational split)
- Drawing the client-state vs server-state boundary and wiring TanStack Query for all remote data
- Hooks discipline — custom hooks, correct deps arrays, deriving state instead of syncing with useEffect
- Rendering performance — scoped memo/useMemo/useCallback, stable keys, list virtualization, Suspense
- Forms with react-hook-form + zod and data-fetching patterns with TanStack Query
When to use
- Architecting a new React + TypeScript SPA or setting up a Vite project from scratch
- Deciding how to split components, where to colocate state, or whether to add a global store
- Diagnosing unnecessary re-renders, unstable keys, or memo thrash in a component tree
Source ↗
🛡️
web-security-architect
Web application security specialist — STRIDE, AuthN/AuthZ, CSP, and secure-by-default.
appseccsrfcsp
Capabilities
- STRIDE threat modeling for web features — assets, attack vectors, mitigations list
- AuthN/AuthZ architecture: session cookies vs JWT, OAuth2/OIDC flows, RBAC/ABAC design
- XSS prevention: output encoding, dangerouslySetInnerHTML audit, DOMPurify, Trusted Types
- Content-Security-Policy design (nonce vs hash vs unsafe-inline trade-offs)
- CSRF defense, SSRF and open-redirect mitigation, secrets management and env boundary
When to use
- Designing AuthN/AuthZ for a new web or API feature (session vs JWT decision, cookie flags, token storage)
- Writing or reviewing a Content-Security-Policy for a Next.js / Astro / Vite app
- Threat-modeling a web feature before implementation (produce STRIDE table + mitigations)
Source ↗
⚡
web-performance-optimizer
Profiling-first web performance specialist — Core Web Vitals, bundle size, and rendering.
core-web-vitalsbundlelighthouse
Capabilities
- Measuring and improving Core Web Vitals (LCP, CLS, INP, TTFB) with Lighthouse, WebPageTest, and RUM
- Analyzing and reducing JavaScript bundle size with Vite bundle visualizer and rollup-plugin-visualizer
- Implementing route-level code splitting, dynamic imports, and tree-shaking
- Eliminating unnecessary React re-renders via targeted memoization and profiling
- Optimizing images (responsive srcset, lazy loading, next-gen formats) and offloading CPU work to web workers
When to use
- Core Web Vitals are failing (LCP > 2.5 s, INP > 200 ms, CLS > 0.1) in Lighthouse or field data
- A Vite/Next.js/Astro bundle has grown and routes are loading slowly
- React components re-render excessively and Chrome DevTools Profiler shows flame-chart spikes
Source ↗
♿
web-accessibility-expert
WCAG 2.2 AA specialist — semantic HTML, ARIA, keyboard navigation, and accessible forms.
wcagariakeyboard
Capabilities
- WCAG 2.2 AA audit and remediation for web applications and React/TSX component libraries
- Semantic HTML landmark and heading-hierarchy structure design
- Keyboard navigation patterns: focus order, skip links, focus trap and restore in modals/dialogs
- Form accessibility: programmatic labels, error message association, required/invalid states
- Automated testing with axe-core, eslint-plugin-jsx-a11y, and @axe-core/playwright
When to use
- Auditing a page or component tree for WCAG 2.2 AA compliance
- Building a modal, dialog, drawer, or popover that needs focus trap and focus restore
- Managing focus after a client-side route change in a Next.js or React SPA
Source ↗
🦀
rust-service-architect
Rust backend service specialist — axum, tokio, sqlx.
axumtokiosqlx
Capabilities
- Rust backend service architecture using axum, tokio, and sqlx
- Project layering (routes/handlers/services/repositories, AppState sharing)
- Error handling strategy with thiserror and IntoResponse mapping
- Auth boundary design (extractors vs middleware); connection pool sizing
- Observability, containerization, and graceful shutdown strategy
When to use
- Standing up a new Rust backend service for mobile and/or web clients
- Choosing between axum/actix-web, sqlx/diesel, or tasks/queues
- Investigating stalled async runtime, exhausted DB pool, or ungraceful shutdown
Source ↗
🧩
web-ui-ux-specialist
Responsive, accessible, localizable web UI on Vite + React 19 with shadcn/Radix and Tailwind v4.
responsiveshadcnux
Capabilities
- Responsive layout with flexbox, CSS grid, and container queries
- shadcn/ui + Radix primitive composition for accessible interaction patterns
- Loading / empty / error / success state design for every async surface
- Form UX with react-hook-form + zod (inline validation, focus management, aria wiring)
- i18n and RTL-aware layouts using CSS logical properties and react-intl
When to use
- Designing web UI that must be responsive across mobile, tablet, and desktop breakpoints
- Composing shadcn/Radix primitives into accessible dropdowns, dialogs, and forms
- Implementing form UX with react-hook-form + zod, or making a layout RTL-ready
Source ↗
🎨
web-design-system-architect
Owns the web design system — one cross-platform token source feeding web CSS/Tailwind vars and Flutter Dart.
tokenstailwindtheming
Capabilities
- Own the web design system — Tailwind v4 @theme tokens wired to CSS custom properties
- A single cross-platform token source that generates web CSS/Tailwind vars AND Flutter Dart tokens
- Token consistency across the marketing (Astro), client (Vite/TanStack), and admin surfaces
- Whitelabel/multi-vertical theming with a deterministic override precedence chain
- Semantic token layering (primitive → semantic → component) and light/dark scheme swaps
When to use
- Setting up or restructuring the web design system for a Tailwind v4 + shadcn/Radix codebase
- A single token set must feed multiple web surfaces without drifting, or adding whitelabel theming
- Auditing surfaces for hardcoded colors, drifted duplicate palettes, or contrast-failing token pairs
Source ↗
🏗️
web-screen-builder
Builds web routes end to end — routing, data wiring, shadcn composition, state coverage, and browser verification.
routingtanstackastro
Capabilities
- Turn a route/page spec into a complete, wired web route end to end
- Choose the correct routing substrate (TanStack Router file route, Astro page, or Next route)
- Wire data loading via a route loader + TanStack Query, or an Astro/Next server fetch
- Compose shadcn/Radix primitives with loading / empty / error / success states
- Scaffold companion components and Vitest/@testing-library tests, then verify in the browser
When to use
- Building a new web page or route from a specification
- Standing up a data-backed screen with loader + query + full state coverage
- Deciding whether a screen is a TanStack SPA route, an Astro page, or a Next route
Source ↗