Art & Design

Use when the user wants a prototype, mockup, clickable demo or "something to show" for an item with approved behaviour trees. Step 4 of the one-shot pipeline - builds a self-contained clickable HTML prototype where every tree branch can be demonstrated, and proves that coverage with the checker.

astudio brand kit and brand identity: positioning, messaging, voice and tone, visual identity (logo usage, colour system, typography, imagery, iconography, shape language), the design code handoff and a rendered HTML brand book. Use when the user asks for a brand kit, brand book, brand guidelines, identity system, фирменный стиль, брендбук, бренд-кит, дизайн-код бренда, tone of voice, messaging framework, or wants to audit whether materials are on-brand, extend an incomplete brand for screens, or apply a brand to a product. Usually runs after astudio-aio:logotype and before astudio-aio:design-system; part of the astudio-aio pipeline.

本を仕上げる組版の担当。日本語の縦書きの本（紙の PDF、固定レイアウトの EPUB）を主に扱う。 頁の収まり、1 字だけはみ出した行、頁の頭に残る短い行、見出しの高さや行取り、引用の下げ、括弧やダッシュの見え方、 写真と文の切れ目、原本との見比べ、柱とノンブルの位置、を測って判断し、文字を変えずに余白と空きで解決する。 これから本を組むときや組み替えるときは、用途、サイズ、組み方向、形式を先に聞いて、組みの仕様を一緒に決める。 Word の見本があれば、そこから読む。 「ここ詰められない？」「この位置でいいのかな」「収まりが悪い」「はみ出してる」「高さをそろえたい」「組み直して」 「原本ではどうなってた？」「本にしたい」「どう指示すればいいか分からない」のように、 組みや版面の話が出たら、組版という言葉が無くても使う。 誤植や表記の点検だけなら校閲の担当へ。文章そのものの書き換えはしない。 Typesetter for Japanese books, in any language the user speaks. Use it when someone working on a Japanese book asks about stray characters at the end of a paragraph, short lines at the top of a page, heading position, vertical text, kinsoku, punctuation spacing, or comparing a layout with a scanned original, even if they read little Japanese. When a book is about to be laid out and nothing is decided, it first asks about use, size, direction and format, and can read these from a Word sample.

用户提出任何与 PPT / 演示文稿相关的内容时使用：要汇报框架、要大纲、 要把文档变成 PPT、要封面或内页配图提示词、要静态图动起来做背景。 按输入类型自动选用四套模板之一（主题定框架 / 文档梳逻辑 / 配图反推 / 图生视频），预填占位符直接产出可用成品，而不是把空模板丢回给用户。 触发词：PPT、幻灯片、演示文稿、汇报大纲、路演、答辩、述职、封面配图、 配图没重点、废图补救、双重曝光、图片转视频、PPT 背景动效。

Plan and time a 4MAT talk backward from the audience outcome: two narrative options, explicit bridges, a format-specific shape (incl. nested workshop cycles), realistic minutes.

Build someone their own personal daily dashboard as a claude.ai Artifact. It covers to-dos, schedule, habits, custom trackers, sleep, exercise, spending with bank-alert import, and deadlines, plus an optional morning brief email. A short interview picks a preset (student, office worker, job seeker, freelancer, health, family/older user), the user ticks which blocks to show, and needs outside the presets become custom trackers or new blocks. Use when the user says "set up a personal dashboard", "帮我搭个人面板", "make me a daily planner/tracker page", "I want a dashboard like X's", or asks to change blocks, trackers or the brief on a dashboard made with this skill.

Design, build, write, and review sites people come to read - documentation, developer docs and API references, help centers and knowledge bases, blogs, editorial and news articles, guides, changelogs, and personal or company writing - so readers find the answer fast and agents can read, cite, and navigate them. Use when someone says "build a docs site", "set up our help center", "make my blog", "our docs are hard to navigate", "restructure the knowledge base", "nobody finds anything with search", "write this page so people understand it", "make our docs work for AI coding agents", or when choosing page structure, headings, navigation, search, typography for long reading, or llms.txt and Markdown versions of pages. Not for marketing or launch pages meant to convert (use landing-page-design), app screens (use web-app-design), or visual identity (use brand-identity).

Start a Webflow project and build its Figma design as a localhost prototype that mirrors Webflow, before anything is written to Webflow. Covers setting up the repo and workspace from wf-template (pnpm new-project, or Bench's Add client from a Figma design), collecting the inputs, reading the Figma file, taking the Webflow snapshot, building the style guide and then each page with the site's own variables and class names, and the handoff pack for the Webflow build. Use for "New project: Webflow site <name>, Figma <link>", setting up a repo and workspace, reading a Figma file, starting or continuing a localhost prototype, proposing variables and classes, or preparing the handoff to the Webflow build. For building in Webflow, use webflow-build.

Build a private-practice website with Astro + PagesCMS + Cloudflare Pages. Use when a therapist wants (1) a fast static practice website (home, about, provider profiles, services, fees & insurance, FAQs, blog/resources, contact) generated by Astro from Markdown content validated by a schema; (2) non-technical editing through PagesCMS, whose .pages.yml config turns content folders into web forms (with the filename-template rule that makes saves work); (3) free hosting on Cloudflare Pages under the practice's own domain and accounts; (4) dynamic features (booking, directories, forms) embedded by iframe from existing systems rather than built into the site; and (5) therapy-site essentials — crisis line on contact paths, no clinical information collected by the site, practice/provider/article structured data, sitemap, RSS, and llms.txt.

Build a Webflow site in Webflow from its approved localhost prototype (built first from the Figma design, in Bench or by Claude), with the Webflow MCP and this wf-template repo: variables, tag styles, classes and CMS, the repo port and loader, the style guide page, the media page, components, then pages section by section, each verified against the prototype at four widths, up to the build handoff. Use when building prototype pages from Figma frames, starting or continuing a Webflow build (Designer through the MCP plus JS/CSS in the repo), building components or pages, comparing Webflow staging with the prototype, checking anchors, page transitions, load flicker or the published HTML, or wrapping up a build session. For project setup, the inputs and the Webflow snapshot, use webflow-prototype; for launch, webflow-launch; for a site that is already live, webflow-audit.

Work on a Webflow site that is already live, without breaking it: a read-only audit first (visual baselines, speed as the median of several runs, accessibility, links, SEO and schema, CMS, custom code and interactions), a status tracker from the client's own checklist, a rollback point, then small batches that go to staging, are verified, and reach the live domain only when the person types "publish". Use when auditing or improving an existing live Webflow site (speed, SEO, accessibility, cleanup), moving a live site's custom code onto wf-template, or doing a one-off fix on a live site (a broken link, a carousel, a form). For a new site, use webflow-build.

Take a finished Webflow build live and through its first month: the SEO plan and schema, pre-launch QA (content, function, devices, accessibility, speed, SEO and tracking), launch day (publish, release, redirects, noindex off), handoff to the client and the 30-day follow-up. Use when a Webflow site built with wf-template is signed off and heading for launch, on launch day, when handing the site to the client, or for after-launch checks.

astudio schema.org structured data (JSON-LD): choose types that still matter in 2026 (Organization, LocalBusiness, Product + Offer + AggregateRating, Article, BreadcrumbList, VideoObject, Event, JobPosting, Course, QAPage), write them to match the visible page, lint them, and flag retired rich results (FAQPage, HowTo and the 2025 batch). Covers Google Rich Results Test and the Yandex microdata validator. Use for "микроразметка", "schema.org", "JSON-LD", "rich snippets", "расширенные сниппеты", "разметка товара", "разметка организации". Part of astudio-ai-seo.

Design and build marketing pages that people remember and understand, and that agents can read accurately - product and launch pages, homepages for a product or studio, pricing pages, waitlists, feature pages, one-pagers, event and campaign pages. Covers art direction (a concept drawn from the subject, one memorable idea, composition), message and page structure, honest proof, pricing, sign-up and waitlist flows, and speed. Use whenever someone asks for a landing page, "a site for my app", "a page to announce X", "make our homepage less generic", "a pricing page", "a coming-soon page", or wants an existing marketing page redesigned or critiqued, even if they only say "make it look good". Consumes brand tokens from `brand-identity` and does not invent logos, palettes or type systems; run that skill first when no brand exists. Not for product UI behind a login (`web-app-design`), docs or blogs (`content-site-design`), storefronts and checkout (`ecommerce-design`), or HTML email (`email-design`).

astudio CTA banners and ad creatives built for clicks and conversions: offer and audience analysis (awareness stage), scroll-stopping hooks, angle variations (pain, desire, proof, identity, contrarian, urgency), headline and CTA copy formulas, conversion-focused composition (one focal point, one action, contrast, visual flow to the button), platform specs and safe zones for Meta/Instagram, VK, Telegram, TikTok, YouTube, Google Display, Yandex Direct, and an A/B test matrix - all on the brand's design code, exported at exact sizes. Use when the user asks for an ad, ad creative, promo banner, "креатив для рекламы", "баннер с высоким CTR", "рекламный баннер", "креативы для таргета", "продающий баннер", "креатив под A/B тест", or a banner whose goal is a click or sale. Builds on astudio-aio:banner-design.

논문·강의 영상·코드·기술 블로그를 읽고 인터랙티브 HTML 해설(설명) 페이지를 새로 만들거나 기존 해설 페이지를 크게 고칠 때 쓴다. 자료 확인, 독자 수준 인터뷰, 구성, 작성, 검증 절차와 설명문·시각화·영상 클립·스타일 규칙을 담는다. "X 해설 페이지 만들어줘", "이 논문 설명 페이지", "explain this paper as an interactive page", "해설을 전면 개편" 같은 요청에 해당한다. 오타·문장 몇 개 수정에는 쓰지 않는다.

Turn design references (screenshot, live website, Pinterest pin, Figma frame, game UI, drawing, moodboard) into a measured UI style (palette, typography, spacing and design tokens), written to a style guide and shown on a visual board. Use when the user shares references and wants a look defined from them, says "in the style of", "get inspired by", "make it look like this" or "extract the colours and fonts", or says a design copies a reference too closely, feels generic, or doesn't fit the subject. Also use when the user asks to apply a style saved in design/styles/ to the app or site, such as "apply <style> everywhere".

Build or change landing pages and marketing sites that people can find and that say one thing clearly. Use whenever the user wants a landing page, marketing page, product or app website, homepage, waitlist page, download page, pricing page, comparison page, or a site for a local business or personal brand, or asks to rewrite, restructure or improve the SEO of one, even if they only say "a site for this project". Do not use for docs sites, app screens or dashboards (use the ultrahand skills for app UI).

Use when 要做一块只有美术、没有电路的 PCB（生日卡、纪念牌、校徽板、异形展示板、挂饰挂绳牌），或要复用某块现成纪念板的视觉语言与工艺（哑黑阻焊 + 沉金、编织纹、白丝印），在嘉立创 / EasyEDA 专业版上从零做到能下单；也适用于"参考板看起来是金/黑/白，我复刻出来不像"这类排查。不适用于需要 BOM、布线、贴片的功能板。

Build an "agent swarm" page-build animation for React / Next.js. A crew of role-colored cursors (planner, coders, designers, layout, tester, reviewer, deployer) assembles each section as it scrolls into view. They frame cards, type headings and swap fonts, drag images in, duplicate list items, pick colors from a wheel, box out grids, then review and approve. Comes with a working engine (canvas overlay, GSAP, Lenis) and a data-attribute DOM contract. Use this skill whenever someone wants agent cursors building the page, a build-on-scroll or "assemble itself" animation, multiplayer-style cursors constructing a portfolio or launch page, a page that looks like AI agents are designing it live, or wants to tune, debug or extend an existing swarm build. It also applies when they describe the effect without naming it, e.g. "cursors that draw the boxes and type the text as you scroll".

Hand-drawn paper-wireframe template — white paper background, monochromatic ink palette, SVG turbulence "wobble" filters for pen-quiver authenticity, handwritten fonts (Caveat / Kalam / Ma Shan Zheng / Long Cang), wavy dividers, sketch-rect overlays, marginalia annotations. For PRD illustrations, IA flow docs, low-fidelity layout exploration, "draft / not final" stakeholder communication. Three skeletons (single-page editorial / app multi-screen flow / IA sitemap) — pick one up front based on the artifact, do NOT inherit only the brush strokes.

Design or redesign a product surface, from the design system up. Use when building, redesigning or modernising a SaaS screen, dashboard, data platform, landing page, onboarding flow or any customer-facing interface, and when the user says a product looks dated, generic or AI-generated. Writes a DESIGN.md design system when the project has none, proposes visual directions and gets one picked, builds a mock for approval when the user wants one, then builds the real thing and verifies it in a browser. Companions: ui-find, ui-review.

Orchestrates automated service-based website generation with local SEO optimization. Creates 200+ service+location pages using parallel agents, Unsplash images via Jina AI, NextJS with dynamic routing, and PostgreSQL database. Use when building service business websites (plumbers, electricians, pressure washing, HVAC, etc.) targeting multiple locations.

Use when designing or building a world-class website for a hotel, resort, lodge, inn, guest house, restaurant, bar, venue, catering, or food-service brand.