Art & Design

Comprehensive macOS development guidance including Swift 6+, SwiftUI, SwiftData, architecture patterns, AppKit bridging, and macOS 26 Tahoe APIs. Use for macOS code review, best practices, UI review, or platform-specific features.

Diagnose, optimize, and maintain Eclipse RCP 4.40 (2026-06) applications using e3, e4, or the compatibility layer; SWT/JFace, OSGi, jobs, startup, UI responsiveness, and memory. Offline documentation included.

Expert guidance for hybrid AppKit-SwiftUI development. Covers NSViewRepresentable, hosting controllers, and state management between frameworks. Use when bridging AppKit and SwiftUI.

Analyze Oracle database schemas, SQL, and execution plans from local sanitized exports without database credentials or a live connection. Document dependencies, review design, and investigate slow queries with evidence.

Design and validate source-grounded synthetic test sets with Curator-style prompt/parse pipelines, provenance, abstention cases, and leakage controls. Use for evaluation dataset curation; not to treat generated answers as ground truth or run paid generation implicitly.

Turn an explicitly consented, sanitized rrweb session into an event-cited SOP and automation requirements. Use to document observed UI workflows with masking and evidence gaps; not to record users covertly or claim backend success from clicks.

Preview, draft, refine, or audit durable, drift-resistant Goal instructions for agents. Use when a task needs a clear observable outcome, a bounded execution loop, measurable acceptance evidence, and explicit complete, blocked, paused, or timeboxed states; do not use for ordinary one-shot prompts.

Design, refine, or review visual interfaces and artifacts using product-specific hierarchy, typography, layout, components, copy, motion, and accessibility. Preserve the existing visual language unless redesign is requested; choose only the relevant design parts.

根据商品图片、商品资料、目标客户及平台，完整澄清需求、设计逐页详情页，经用户确认方案和提示词后，选择 agent 内置生图或远程 ComfyUI 生成画面，再用真实字体自动排版、验收和分类归档。适用于商品详情页信息图策划、提示词编写与制作。

Plan product advertising images through adaptive intake, visual research, distinct creative concepts, individual page designs and review sketches before generating. Use for ecommerce visual direction, product-photo campaigns and revisions from real assets and optional references.

Design systems, layout architecture, subtle gradient stats cards, collapsible sidebars, breadcrumbs, date filters, and TanStack data tables for modern dashboards.

印花集（PRINTSTREAM）印刷美术风格的前端设计规范与母题生成器。当用户要求用印花集、Printstream、印刷母题、纸墨印刷、印刷网点、halftone、模版字体（stencil）风格设计或改造网页、UI 组件、仪表盘、设计系统时使用。提供实测设计令牌（纸 #f4f6f9 / 墨 #0d1117 / 虹带三色）、九大母题的参数化 CSS/SVG 生成器（四角定位标、X 阶梯标尺、密度条码、粗黑条三连、虹带、点阵菱形簇、虚线弧、图标三连、黑白反相分区）、组件配方、12 条铁律与 12 个已被否决过的反模式。This skill should be used when designing web pages, UI components, dashboards or design systems in the Printstream / ink-on-paper / printed-motif aesthetic, or when the user mentions 印花集风格 UI.

Règles pour que chaque page de bytetuto.com soit responsive (mobile d'abord, 320 px → 1920 px, sans défilement horizontal). À utiliser pour toute création ou modification de page, de CSS, de mise en page, d'image ou de composant dans site/, et avant de valider une PR qui touche l'affichage.

The original v1 taste-skill, preserved for projects depending on its exact behavior. The current default is `design-taste-frontend` (v2), which is a new skill. Use this v1 install name only if you need exact backward compatibility.

Builds and updates Vite + Lit Web Components inside the frontend/ directory using OpenAPI-generated TypeScript contracts. Trigger this when creating UI views, web components, styling, or wiring frontend state to backend APIs.

>- Build, migrate, or review static (no server) Svelte 5 apps using runes ($state, $derived, $effect, $props, $bindable) instead of legacy Svelte 4 reactivity (export let, reactive dollar-colon statements, stores-as-default). Use whenever I mention Svelte 5, runes, a "static Svelte site", "Svelte SPA", "SvelteKit static site"/"adapter-static"/prerendered SvelteKit, deploying Svelte to GitHub Pages/Netlify/Cloudflare Pages/S3/any CDN, or converting Svelte 4 code (export let, on:click, writable stores) to Svelte 5. Also use when writing or reviewing .svelte files that must ship with no backend, to flag accidental server-only SvelteKit files (+page.server.js, +server.js, form actions) or exposed secrets, and to apply the bundled XSS/CSP/secrets security checklist. Trigger even for a bare pasted .svelte file or a vague "make this a static site" request.

>- Expert guidance for building type-safe, performant i18n apps with Paraglide JS 2.x (compiler-based, tree-shakable) and Svelte 5 (runes). Covers setup, message authoring, locale strategies, i18n routing, SSR/SSG, rich-text markup with Svelte 5 snippets, reactivity patterns, testing, and troubleshooting. Use when I mention Paraglide, inlang, paraglide-js, SvelteKit i18n, locale switching, localized URLs, or Svelte 5 runes in an internationalization context.

>- Build, migrate, or review server-rendered Svelte 5 apps using runes ($state, $derived, $effect, $props, $bindable) with SvelteKit SSR (adapter-auto/node/cloudflare/vercel/netlify) or plain Vite SSR using svelte/server render() and hydrate(). Use whenever I mention Svelte 5 SSR, server-side rendering, SvelteKit load functions, +page.server.js, +layout.server.js, hooks.server.js, form actions, streaming SSR, CSP nonces, hydration mismatches, or request-scoped state. Also use to review .svelte and server files for SSR-safety bugs: effects that never run on the server, module-level state leaking between users, non-deterministic render values, and secrets reaching the client. Trigger even on a bare pasted component that "renders differently on the server and client".

Implement or update a frontend page, section, or component from a Figma URL in the current repository, including asset reuse and browser verification. Use for Figma-to-code implementation requests, not design-only analysis or writing designs into Figma.

Frontend prototype screenshot to static page implementation workflow. Use when the user provides or references a page image, screenshot, mockup, or prototype and explicitly asks Codex to generate, recreate, restore, convert, or implement the related frontend page. Focus on extracting layout, visible elements, implied interactions, local theme alignment, efficient production-style code, and CSS-first rendering without unnecessary JavaScript.

Implement and review the Cursor BYOK React/Tauri desktop frontend. Use for changes under apps/desktop involving routing, page layout, window chrome, settings UI, scrolling, virtualization, charts, themes, or frontend component architecture.

Use this skill to add a new TTS engine to Voicebox. It walks through dependency research, backend implementation, frontend wiring, PyInstaller bundling, and frozen-build testing. Always start with Phase 0 (dependency audit) before writing any code.

Analyze portfolio holdings or screenshots for concentration, shared market exposure and transparent BTC crash scenarios. Use for portfolio risk checks and diversification reviews. Explain as Robin the Quant. Exclude individual project due diligence and trade execution.

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.