Art & Design

>- Dockerfile rules for Next.js standalone apps in a pnpm + Turborepo monorepo — multi-stage build (turbo prune → pnpm fetch/offline install → turbo build → minimal runner), pinned Node 26 Alpine by digest, checksum-verified pnpm binary, non-root uid 1001, read-only root filesystem with a writable .next/cache, HEALTHCHECK on /api/health, build args only for NEXT_PUBLIC_* values, BuildKit secrets and cache mounts, multi-arch, OCI labels and .dockerignore. Use when the repo has a Dockerfile, .dockerignore, compose file, or next.config with output "standalone", or when asked to containerise, shrink, harden or debug an image.

>- Biome 2.5 setup and rules for Nuvraxis monorepos — root biome.json with pinned $schema, VCS ignore, formatter settings, the recommended preset with a11y and the react/next domains, nursery policy, organize imports, overrides, nested per-package configs ("extends": "//"), biome check --write locally, biome ci in CI, VS Code settings, and migrating from ESLint/Prettier. Use when the repo has biome.json or biome.jsonc, @biomejs/biome in package.json, .eslintrc*/eslint.config.*/.prettierrc* to migrate, or when fixing lint and formatting errors.

Check readiness from a working diff, PR URL, release target, or full repository audit. Use when asked to review changes, assess release readiness, or find backend and frontend issues with evidence.

UI design workflow for React and Tailwind interfaces: hierarchy, design tokens, accessibility, interaction states, and UI copy. Use when designing, building, or restyling a screen, component, or flow; reviewing or auditing UI or accessibility; editing theme tokens; or writing interface text.

Render ảnh preview/mockup giao diện TRƯỚC khi sửa code UI (preview, mockup, xem trước giao diện, design, phác thảo, demo ảnh, duyệt thiết kế). Use when the user wants to see or approve a UI design before implementation, or when proposing UI changes - render offscreen to PNG, open for approval, then apply. Use this whenever a change touches views/layout/colors.

Run automated post-deploy UI verification with a browser automation MCP (claude-in-chrome, Playwright, or Puppeteer): console-error and Core Web Vitals smoke checks, form and auth-flow interaction tests, screenshot visual regression across three breakpoints, and axe-core accessibility audits ending in a SHIP / DO-NOT-SHIP verdict. Use when testing a deployed feature on staging or preview, before shipping frontend changes, reviewing a frontend PR, or checking responsive layout and accessibility.

Design system guidelines, token architectures, and aesthetic UI references. Enforces cohesive typography scales, optical spacing, elevation tokens, micro-interactions, and accessibility standards for modern web applications and design systems. Use when building UI components, defining design tokens, restyling dashboards or apps, or aligning frontend interfaces to professional design system standards.

Shared vocabulary for designing deep modules. Use when the user wants to design or improve a module's interface, find deepening opportunities, decide where a seam goes, make code more testable or AI-navigable, or when another skill needs the deep-module vocabulary.

Run a full pre-launch audit on a web app before it goes public. Use when the user says "am I ready to launch", "pre-launch check", "audit my app before launch", "what am I missing before shipping", or asks for a launch checklist. Produces a scored report with blockers, fixes, and a go/no-go verdict.

Audit and write SaaS landing-page copy using MicroConf customer-research and emotional-copy methods. Use for a landing-page URL, pasted copy, local website code, or a blank-slate SaaS page when the founder wants a rigorous copy review and an iterative interview to resolve customer, positioning, proof, and CTA gaps before drafting or rewriting.

Write, rewrite, or critique conversion copy for homepages, landing pages and search-driven pages (service pages, comparisons, glossary and "what is" pages, guides, cost guides, integration and use-case pages), and the templates or LLM prompts that generate them at scale. Covers hero headlines, subheads, section headings, proof, CTAs, FAQ, form microcopy, title tags and meta descriptions, especially for B2B services firms, agencies, consultancies and technical products sold to expert buyers. Use this whenever the user asks for website copy, a homepage or landing page rewrite, a value proposition, headline or CTA options, SEO page copy, programmatic page templates, "make this page convert", or "our copy sounds generic / AI-written", even if they never say "copywriting". Not for blog articles, emails, ads, or social posts.

Draft one landing page as one https URL, one offer, and one action, then score it. Use when someone asks for a landing page, a single-offer page, or a page with one call to action. Refuses a sitemap or a list of pages. Not for writing the value line (use evp), setting price tiers (use pricing), or the emails after opt-in (use email-sequence).

>- GitHub Actions conventions for Nuvraxis Next.js apps — exactly three workflows: pr.yaml (every PR to any branch: Biome, stylelint, typecheck/test/build with turbo --affected, Docker build + health check, helm lint + kubeconform; publishes nothing), main.yaml (push to main: one multi-arch image to GHCR tagged sha-SHORTSHA and main, provenance + SBOM, gha cache), release.yaml (tag vX.Y.Z: verify on main, retag the existing image without rebuilding, package and push the Helm chart to OCI, GitHub Release with chart, digest and SBOM). Minimal permissions per job, GITHUB_TOKEN only, pinned action majors. Use when editing .github/workflows/*, adding a CI step, or debugging a failed run or release.

审查主题辨识、构图、字面与完整入退场；按当前需求修订，避免把旧反馈变成全局禁令。

Splits the copy of a web page into blocks (hero, benefits, how it works, testimonials, pricing, FAQ, CTA and others) and writes 1 reusable prompt per block. Each prompt writes the same kind of text for a different product and has an example checked against it. Copy only; the design is ignored. Use when the user gives a URL and asks to break down or reverse-engineer the copy of a landing page, make prompts per section, write a similar block for their site, or see how a competitor's page is written.

按用户主题创作完整字效作品，保护明确锁定项，统一随包指导与真实动效验收。

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.

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

Postgres best practices maintained by Supabase, for Postgres running anywhere. Load this skill BEFORE writing or changing anything that lives in a Postgres database: creating or altering tables and columns (including choosing column types), schema design, migrations and declarative schema files, RLS policies and the tests that verify them, indexes, triggers, database functions, queues and scheduled jobs (pg_cron, pgmq), vector/semantic search (pgvector), and restoring dumps (pg_restore) or importing data. Also load it when diagnosing slow queries, high CPU, timeouts, EXPLAIN plans, connection exhaustion, locking, bloat, or rows visible to the wrong user or tenant. This is not just a performance guide — schema, migration, security, and SQL authoring tasks need these rules too, even for a one-column change or a single query.

Add or review an accessible portfolio project-preview reader for ordered long images, document pages, or staged visual modules.

Validate a statically exported portfolio website for GitHub Pages release readiness. Use before publishing or diagnosing deployment regressions.

Prepare, optimize, and register portfolio images and documents while preserving provenance, accessibility, and responsive rendering contracts.

Review or implement portfolio UI motion against an existing motion system, including reduced-motion, keyboard, performance, and responsive constraints.

Validate Chinese and English portfolio routes, content states, metadata, and fallbacks. Use when adding or reviewing localized portfolio content.