Art & Design

调试 Gosim、SAC 等天文观测或仿真调度 agent 的协议、反馈状态、物理估计、预算、模型流程及实验验收问题；依据历史失败设计最小可证伪修复。用于同类问题排查与复盘，不自动启动评分矩阵或外部 API。

This document captures hard-won lessons from building the AstroVille Design System on Penpot via the MCP server. The goal is to **avoid re-discovering these Penpot quirks** in future projects. Many of these behaviors are undocumented and only show up at runtime when elements are exported or grouped.

>- Wire a web or React Native frontend to OpenApps: the @bounded-sh/client SDK (reads, writes, subscriptions, queries), hosted static frontends, and end-user auth UI (email OTP, OAuth, browser guest/anonymous accounts and upgrade). Use when building the client of an OpenApps app or handling how end users sign in. Part of the OpenApps skill family; server-side rules, functions, and the actor model live in the openapps-backend skill, and deploy/hosting config in openapps-deploy.

Official daisyUI component-library skill for Tailwind CSS. When you write HTML or JSX code, you must use it. Even if the user does not request it, use it.

Skill to generate Open Graph images for Catalyst Bridge using headless Chrome.

Usage rules that you must use with daisyUI 5

Configuration options for daisyUI 5

Color rules that you must use with daisyUI 5

Installation instructions for daisyUI 5

Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices. Use when building or reviewing React or Next.js components, state, or render performance.

Next.js App Router expert guidance. Use when building, debugging, or architecting Next.js applications — routing, Server Components, Server Actions, Cache Components, layouts, middleware/proxy, data fetching, rendering strategies, and deployment on Vercel.

shadcn/ui expert guidance — CLI, component installation, composition patterns, custom registries, theming, Tailwind CSS integration, and high-quality interface design. Use when initializing shadcn, adding components, composing product UI, building custom registries, configuring themes, or troubleshooting component issues.

Integrate data visualizations into React and Next.js applications. Use when the user needs chart components, UML-like or architecture diagram components, React integration patterns, Next.js client or server boundaries, hydration-safe rendering, lazy loading, framework-aware performance, scroll-driven visual stories, or export guidance.

v0 by Vercel expert guidance. Use when discussing AI code generation, generating UI components from prompts, v0 CLI usage, v0 SDK/API integration, or integrating v0 into development workflows with GitHub and Vercel deployment.

Makes websites, landing pages and UI look designed by a person with taste instead of generic "AI slop". Bans the tells every AI-built site shares (purple/blue gradients, gradient text, neon accents, glow shadows, glassmorphism, Inter/Poppins-by-default, sparkle emojis, the hero → logo cloud → 3 feature cards → pricing template, "Unlock the power of" copy) and replaces them with a short design process that produces deliberate, specific choices. Use this skill whenever you build, redesign, restyle or review any website, landing page, portfolio, web app UI, HTML/CSS page, React/Vue/Svelte component, Tailwind layout, email template or artifact page, even if the user never says "design" or "AI slop". Also use it when the user says a page "looks AI-generated", "looks like every other site", "too generic", "make it look human/handmade/real", or "de-slop this", or asks which fonts suit a business or niche.

Extract a website's observed design system from a URL and deliver a validated ZIP containing design.md, token.json, variables.css, and theme.css. Use for website style references, design-token extraction, or RICOUI-compatible design packages; not for redesigning a website.

Creates and improves Astro, Tailwind CSS, and Wagtail websites with nontechnical users. Use for Website Builder setup, preparing or refining a website, and reviewing recorded feedback about the Website Builder workflow.

Use when testing, debugging, or making targeted improvements to rendered frontend apps through the Build Web Apps or web dev plugin: local dev servers, UI regressions, interaction bugs, console errors, responsive layout, and visual QA. Check whether the Browser plugin is available and use it first when it is; otherwise use regular Playwright with the recorded reason.

Design UI surfaces for browser games. Use when the user asks for HUDs, menus, overlays, responsive layouts, or visual direction that must protect the playfield.

Use for new frontend applications, dashboards, games, creative websites, hero sections, and visually driven UI from scratch, or when the user explicitly asks for a redesign/restyle/modernization. Builds from clean, airy, high-taste, readable image-generated concept design with section-specific references, faithful implementation, and browser testing.

Set up Tailwind CSS v4 in Expo with react-native-css and NativeWind v5 for universal styling

Guide for building, configuring, and deploying microfrontends on Vercel. Use this skill when the user mentions microfrontends, multi-zones, splitting an app across teams, independent deployments, cross-app routing, incremental migration, composing multiple frontends under one domain, microfrontends.json, @vercel/microfrontends, the microfrontends local proxy, or path-based routing between Vercel projects. Also use when the user asks about shared layouts across projects, navigation between microfrontends, fallback environments, asset prefixes, or feature flag controlled routing.

Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex/grid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3/v4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML/CSS component, CSS file audits, build tool configuration, and vanilla CSS.

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.