pohlai88

Enforces correct use of AFENDA design tokens, the L0–L4 premium elevation architecture, semantic lanes, and generous spatial rhythm. Use when editing styles, themes, layouts, or visual states.

Complete Neon Auth integration setup for AFENDA, addressing gaps in current codebase. Covers provisioning, server SDK, client SDK, bearer token verification, and security module integration.

Practical NextAuth/Auth.js development and implementation playbook with end-to-end debugging workflows for Next.js apps.

Build AFENDA Treasury as an AP-grade full-stack ERP sub-domain (contracts, db, core, api, worker, web, tests, gates). Use when: treasury module, cash management, bank account, bank statement, reconciliation, liquidity forecast, cash position, payment factory, bank transfer, treasury controls, treasury architecture review, AP-style enterprise workflow.

Quality assurance for web accessibility and usability, particularly for users with disabilities. Use when involved in any web project.

Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

This skill provides guidance for implementing security features that span across Better Auth, including rate limiting, CSRF protection, session security, trusted origins, secret management, OAuth security, IP tracking, and security auditing. These topics are not covered in individual plugin skills.

Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.

Google Labs shadcn/ui skill — component discovery via MCP, installation, customization, blocks. Use with shadcn MCP tools.

Next.js best practices - file conventions, RSC boundaries, data patterns, async APIs, metadata, error handling, route handlers, image/font optimization, bundling

Quality assurance for web accessibility and usability, particularly for users with disabilities. Use when involved in any web project.

Skill for integrating Better Auth - the comprehensive TypeScript authentication framework.

This skill provides guidance for implementing security features that span across Better Auth, including rate limiting, CSRF protection, session security, trusted origins, secret management, OAuth security, IP tracking, and security auditing. These topics are not covered in individual plugin skills.

Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.

ClawHub reputation checker for ClawSec suite. Enhances guarded skill installer with VirusTotal Code Insight reputation scores and additional safety checks.

Security advisory feed with automated NVD CVE polling for OpenClaw-related vulnerabilities. Updated daily.

Type-safe SQL ORM for TypeScript with zero runtime overhead

TypeScript-first schema validation library with static type inference for form validation, API validation, and runtime type checking with compile-time types.

Official ESLint + typescript-eslint + boundaries best practices for enterprise monorepos (flat config, typed linting, architectural boundaries, CI quality gates).

Official ESLint and typescript-eslint performance tuning for large monorepos (cache strategy, concurrency, typed-linting scope, profiling).

Official Pino logging best practices - structured JSON logging with child loggers, serializers, transports, and request-scoped logging for production applications.

Changesets for versioning and changelog management in monorepos. Use when managing package versions, generating changelogs, or publishing packages. Use for changesets, versioning, changelog, semver, monorepo-versioning, release, publish, bump.

Data modeling with Entity-Relationship Diagrams (ERDs), data dictionaries, and conceptual/logical/physical models. Documents data structures, relationships, and attributes.

Supply chain security, license compliance, and dependency health monitoring for monorepos. Use when auditing dependencies, detecting version drift, checking licenses, scanning for vulnerabilities, or analyzing transitive dependencies. Covers npm audit, Snyk, Socket.dev, and license compliance tools.

Vitest with Vite in the Afenda monorepo — shared defaults from @afenda/vitest-config, RTL patterns, and troubleshooting. Use when configuring Vitest, writing or debugging unit tests, coverage, or mocks.

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Deploy applications and websites to Vercel. Use when the user requests deployment actions like "deploy my app", "deploy and give me the link", "push this live", or "create a preview deployment".

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Turborepo monorepo build system guidance. Triggers on: turbo.json, task pipelines, dependsOn, caching, remote cache, the "turbo" CLI, --filter, --affected, CI optimization, environment variables, internal packages, monorepo structure/best practices, and boundaries. Use when user: configures tasks/workflows/pipelines, creates packages, sets up monorepo, shares code between apps, runs changed/affected packages, debugs cache, or has apps/packages directories.

Design and implement website pages, landing sections, shared UI elements, and optional Storybook stories in Afenda's Vite app. Use when working on website or marketing design in `apps/web`, especially with Tailwind CSS v4, `@afenda/design-system/ui-primitives` shadcn-style components, responsive layouts, image blocks, feature cards, CTA sections, or `*.stories.tsx` deliverables.

React composition patterns that scale. Use when refactoring components with boolean prop proliferation, building flexible component libraries, or designing reusable APIs. Triggers on tasks involving compound components, render props, context providers, or component architecture. Includes React 19 API changes.

React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.

Quality assurance for web accessibility and usability, particularly for users with disabilities. Use when involved in any web project.

Release automation for Claw skills and website. Guides through version bumping, tagging, and release verification.

ClawHub reputation checker for ClawSec suite. Enhances guarded skill installer with VirusTotal Code Insight reputation scores and additional safety checks.

Security advisory feed with automated NVD CVE polling for OpenClaw-related vulnerabilities. Updated daily.

ClawSec suite manager with embedded advisory-feed monitoring, cryptographic signature verification, approval-gated malicious-skill response, and guided setup for additional security skills.

Community incident reporting for AI agents. Contribute to collective security by reporting threats.

Complete Drizzle ORM documentation in markdown format. Use when working with Drizzle ORM - covers schema definition, queries, migrations, database connections (PostgreSQL, MySQL, SQLite), integrations (Neon, Supabase, PlanetScale, Cloudflare D1, Turso), column types, relations, transactions, and framework usage (Next.js, SvelteKit, Astro).

Example skill showing how to create deployment workflows with safety checks and rollback procedures

Afenda metadata-driven EUI polish workflow. Use automatically when implementing, reviewing, or refining governed renderers (packages/governed-surface/src/metadata/renderers), surface builders (packages/kernel/src/modules/list-surfaces.ts), Pattern A/B/C ERP pages, or the dev metadata-renderer-gallery. Composes shadcn-metadata, governed-renderer contracts, and Vercel web-design/composition skills. Do not invoke sibling skills separately for the same task.

Refactor And Fold duplicate Afenda feature areas into a canonical module. Use when the user invokes /raf, asks to merge duplicate system-admin sections, consolidate overlapping routes, or remove a feature folder after folding its unique fields into the surviving area. No redirects unless explicitly requested.

Use when the user asks about libraries, frameworks, API references, or needs code examples. Activates for setup questions, code generation involving libraries, or mentions of specific frameworks (React, Next.js, Drizzle, Tailwind, etc.).

Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately.

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

Find unused functions and dead code in the codebase

Use when documentation drift is detected. Comprehensively audits codebase and creates/updates Swagger, features docs, and general documentation to achieve full sync.

Knip dead code detection best practices for JavaScript and TypeScript projects. Use when configuring Knip, analyzing unused code, setting up CI integration, or cleaning up codebases. Triggers on knip.json, dead code, unused exports, unused dependencies, bundle optimization.

Accessibility for React UIs in AFENDA-HYBRID: semantic HTML, ARIA, keyboard support, focus management, and testing. Use for grids, dialogs, bulk selection, notifications, and command surfaces.

React and Next.js App Router architecture for AFENDA-HYBRID: Server vs Client Components, composition, state placement, package layering (ui-core → view-engine → erp-view-pack → apps/web). Use when designing components, fixing import/layer violations, or RSC boundaries.

Implementation patterns for AFENDA-HYBRID React code: custom hooks, compound components, error boundaries / error.tsx, forms, server actions, and optimistic updates.

React performance for AFENDA-HYBRID: runtime rendering (re-renders, keys, virtualization) and build-time delivery (bundles, tree-shaking, code splitting, compiler directives). Use when fixing slow lists, grids, or large client bundles.

Meta-skill: React Quality Orchestrator for AFENDA-HYBRID. Coordinates architecture, performance, accessibility, and design-pattern skills for audits, scoring (Component Quality Index), and confidence-tiered refactors. Use for full-route reviews, legacy refactors, and governance checks.

Official Storybook AI workflow — MCP server, manifests, MCP toolsets (development, docs, testing), and documentation best practices. Use when writing or fixing stories, connecting agents to Storybook, using design-system components without guessing props, or running Storybook tests from an agent. Sources are linked inline.

Vitest (Vite-powered) testing — Jest-compatible API, vi mocks, coverage, environments, projects/workspaces. Use when writing or fixing tests, vitest.config.ts, coverage, or monorepo test commands in AFENDA-HYBRID (@afenda/db, @afenda/ui-core, view-engine, erp-view-pack). Prefer https://vitest.dev for Vitest 4.x when reference snippets disagree.

Upgrade Tailwind CSS from v3 to v4 in monorepos and Next.js projects. Use when upgrading Tailwind, migrating tailwind.config to CSS @theme, replacing @tailwind directives, switching to @tailwindcss/postcss or @tailwindcss/vite, or troubleshooting v4 migration issues.

You are a code refactoring expert specializing in clean code principles, SOLID design patterns, and modern software engineering best practices. Analyze and refactor the provided code to improve its quality, maintainability, and performance.

Afenda metadata-driven EUI polish workflow. Use automatically when implementing, reviewing, or refining governed renderers (components2/metadata/renderers), surface builders (*-surface-builders.server.ts), Pattern A/B/C ERP pages, or the dev metadata-renderer-gallery. Composes shadcn-metadata, governed-renderer contracts, and Vercel web-design/composition skills. Do not invoke sibling skills separately for the same task.

Afenda Ask-Docs Quality Standard workflow. Use automatically when authoring, reviewing, or improving content/ask-docs MDX. Composes documentation-audit (code-verified accuracy) and technical-writing (internal-guide prose) with the six-dimension ADQS rubric. Do not invoke sibling skills separately.

Write internal technical documentation for engineers and operators: technical specs, architecture docs, ADRs, runbooks, migration plans, and developer-facing implementation guides. Use when the main job is capturing a technical decision, system boundary, operating procedure, or rollout path for builders and maintainers. Triggers on: tech spec, design doc, architecture doc, ADR, runbook, migration guide, implementation guide, rollout doc, operational guide, and internal technical writing. Route API portals to `api-documentation`, end-user help/tutorials to `user-guide-writing`, release notes to `changelog-maintenance`, decks to `presentation-builder`, and GTM messaging to `marketing-automation`.

Manages shadcn components and projects — adding, searching, fixing, debugging, styling, and composing UI. Provides project context, component docs, and usage examples. Applies when working with shadcn/ui, component registries, presets, --preset codes, or any project with a components.json file. Also triggers for "shadcn init", "create an app with --preset", or "switch to --preset".

Applies MorphoFeed commercial website doctrine—reframe pages as market-facing decision surfaces (not documents), layer brand then product architecture then scientific proof, translate prose into interface (hero, grids, proof strips, CTAs), and run strategic/design/brand critique loops. Use when designing or upgrading marketing routes, home or documented-science pages, or when the user rejects documentation-style layouts, generic biotech/SaaS templates, science-as-whole-identity, or stock-brochure aesthetics.

Refines MorphoFeed marketing UI for a calm, editorial, industrial tone. Use when the user asks for design polish, layout fixes, “better visuals,” or criticizes the home page as busy, cheap, generic, or template-like. Prefer restraint, typography, spacing, and token discipline over decorative placeholder diagrams. Works with tailwind.config.ts and src/styles/index.css; copy stays in src/content/morphofeed.ts.

GangOf4 Adapter SDK — a metadata compiler that ingests ERPNext app metadata losslessly, normalizes it into a versioned Canon schema, and generates a standalone stack (Drizzle DB + Zod contracts + API routes + React UI + OpenAPI spec) targeting Neon serverless Postgres. Use for any task involving ERPNext refactoring, Canon schema, code generation, or the go4 pipeline.

Guides and best practices for working with Neon Serverless Postgres. Covers getting started, local development with Neon, choosing a connection method, Neon features, authentication (@neondatabase/auth), PostgREST-style data API (@neondatabase/neon-js), Neon CLI, and Neon's Platform API/SDKs. In the gangof4 repo, use the practiced workflow (go4 generate + neon target, push-to-neon script, Drizzle). Use for any Neon-related questions.

Comprehensive workspace optimization using Cursor's full capability stack