Art & Design

微信公众号文章排版引擎，将 Markdown 转换为可直接粘贴到公众号编辑器的 HTML。主题风格从 references/theme-index.md 注册的自定义主题库中选取，自动章节编号、关键词下划线标记、引言卡片、目录导航、代码块、图片/GIF、作者签名。支持 Markdown / Word(.docx) / PDF / 纯文本输入（非 Markdown 先自动归一化），也支持"一键自动排版"（自动推断结构+选主题），还支持根据用户描述/参考图生成自定义主题组件库并保存本地复用。触发场景：(1) 用户提到"公众号排版""公众号文章""微信排版""gzh"，(2) 用户想把文章（md/docx/pdf/纯文本）转成公众号 HTML，(3) 用户说"自动排版""一键排版"公众号内容，(4) 用户想为公众号排版"生成新主题/自定义风格/按这张图做一套组件库"。不用于生成普通网页/落地页/PPT（用前端或 PPT 类 skill）。

Author or change screens of an AINDF design system through its DS-MCP only. Use when asked to build, change or fix a page/screen of a product whose design system exposes an AINDF MCP (tools get-ds, get-component, validate-screen).

Create, refine, or review system analysis and software architecture diagrams from requirements or code, including UML, ERD, DFD, C4, BPMN, and workflows. Use for diagram selection, notation checks, cross-diagram consistency, and editable Draw.io deliverables.

Test whether software satisfies its requirements. Use for QA reviews, acceptance testing, requirements traceability, test plans, exploratory testing, API/database/UI checks, defect reproduction, regression, fix verification and release readiness. Compare expected and actual behavior with evidence; existing passing tests alone are insufficient. Apply implementation fixes only when the user's task authorizes them.

Turn a requested feature, change, or established fix into a repository-grounded implementation plan before coding. Use for implementation sequencing, affected-file and contract analysis, migration risks, and test acceptance planning. Planning does not authorize implementation; unexplained failures belong to debug-and-refactor and architectural modeling to system-design when needed.

Apply DizgiDEX and YAMATAI editorial, design, multilingual, and publishing-engineering standards to Lovable workspace projects. Use when planning, designing, implementing, reviewing, or publishing websites, digital magazines, editorial platforms, content pipelines, and publishing automation; adapt brand-specific conventions to each project.

Set up or manage Iris (Flowlith's AI agent for a business's Instagram, WhatsApp, Messenger and website chats). Use when the user wants to onboard their business to Iris, check its status, change what Iris knows, teach it, launch it, test it, or buy credits.

Publish or refresh the live copy of the "Tool use sin abstracciones" deck at h1sort.com/claude4aieng by syncing a public build into the h1sort-website repo. Use after any edit to the deck, or when asked to publish, deploy, refresh or update the slides on the site.

Guides stable API and interface design. Use when designing APIs, module boundaries, or any public interface. Use when creating REST or GraphQL endpoints, defining type contracts between modules, or establishing boundaries between frontend and backend.

>- Helm chart rules for Nuvraxis Next.js apps — one chart per app in charts/ (named after the app), published to oci://ghcr.io/nuvraxis/charts and synced by Argo CD; Chart.yaml version/appVersion set only by release.yaml; Deployment with startup/liveness/readiness probes on /api/health, non-root read-only security context, emptyDir for .next/cache, ConfigMap + existing Secret via envFrom, Service, Ingress with cert-manager, HPA, PDB, ServiceAccount, topology spread; no Helm hooks; helm lint --strict + kubeconform. Use when the repo has charts/, Chart.yaml, values*.yaml, templates/*.yaml with Helm syntax, or an Argo CD Application, or when asked to deploy, scale, expose or configure the app on Kubernetes.

Creates Senro test cases for a WebMCP website by inspecting the website repository, understanding its user journeys, and writing an import-ready test-case suite. Use when generating or expanding a Senro test suite from a website codebase.

>- Production rules for Next.js 16 App Router apps at Nuvraxis — Server/Client Component boundaries, Cache Components ("use cache", cacheLife, cacheTag, updateTag), Server Actions, route handlers, env handling, instrumentation, output standalone and the /api/health route. Use when the project has "next" in package.json, an app/ or src/app/ directory, next.config.ts, proxy.ts, instrumentation.ts, or files named page.tsx, layout.tsx, route.ts, loading.tsx, error.tsx.

Guidance for distinctive, intentional visual design when building new UI or reshaping an existing one. Helps with aesthetic direction, typography, and making choices that don't read as templated defaults.

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

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.

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.

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.