Art & Design

从用户简历、人物动作视频和机构 Logo 复刻交互式个人简历网站。适用于下载本项目后收集素材、分析履历、提炼双语文案并替换模板内容的任务。

Design and build motion-first creative websites — page design (structure, type scale, palette, spacing) plus interaction choreography: scroll animation, Framer Motion, GSAP, and light 3D via Three.js/R3F. Use for animated landing pages, creative portfolios, product showcases, WebGL-lite scenes, and motion audits. Also use when tuning interaction handfeel (手感差/太生硬/不跟手), replicating motion from a video or URL reference (复刻), building 3D depth from flat image assets (伪3D/抠图), diagnosing dead scroll-timeline stretches, mixing scene audio, auditing discoverability (点不开/没人会发现), building headless verification probes, or fixing a page that moves well but looks generated (不好看/像AI做的/没设计感). Equally for building a whole site from nothing (从0到1做个网页/落地页/官网/作品集): stack choice, sections and copy, components (导航/hero/表单/卡片/定价表), and production polish (favicon/OG/404/空状态/暗色模式). Not for dashboards, admin UI, or full 3D scene generation.

Audit raw portfolio-project materials into an evidence-backed publishing brief. Use before writing a case study, project card, or factual portfolio copy.

Build or update an evidence-backed portfolio case study in an existing website. Use after narrative facts and media have been approved.

Rebuild existing web pages as working local code, matching their real content, assets, responsive layout, and interactions. Use for website cloning, replication, or reverse engineering, including Framer sites and animated pages.

Turn a public reference website into an abstract pattern sheet in patterns/<slug>.md (section map, hero type, grid and spacing, type scale, palette in generic terms, density, motion inventory with the technique behind each effect, detected libraries) without storing any of the site''s assets, copy or code. Use when the user runs /analyze-reference <url> or asks to analyze, study, break down or extract patterns from an inspiration or reference site for a landing. Checks robots.txt and text-and-data-mining reservations first and aborts if access is disallowed. Not for cloning or rebuilding a site.

Use when the user wants to design, redesign, shape, critique, audit, polish, simplify, harden, animate, or otherwise improve a frontend interface: websites, landing pages, dashboards, product UI, components, forms, settings, onboarding, empty states, and native iOS or Android screens. Handles UX review, hierarchy, layout, typography, color, motion, UX copy, accessibility, responsive behavior, edge cases, and capturing or documenting design systems (DESIGN.md, tokens). Also for making bland UI bolder, loud UI quieter, or ambitious visual effects. Not for backend-only or non-UI tasks.

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML/CSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, "AI-made", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.

Apply error-handling principles when designing or reviewing failures, recovery, retries, background tasks, and user-visible error reports.

Use when deciding whether to write an Agent Note (a durable design decision or proposal record), when adding, moving, consolidating, auditing, pruning, archiving, or reviewing Agent Notes under .agents/notes/, and for the supersession check every new note requires.

Use when writing or changing a model-facing tool definition (name, description, parameter schema, or its system-prompt section), and when designing skills, context loading, or multi-step agent workflows, to make information discoverable and use context efficiently.

UI and visual skill for antislop. Use when building or editing any interface: color, layout, components, motion. Load with the core.

Create pixel art (game sprites, characters, items, tiles, tilesets, icons, scenes, sprite sheets) with pxl, a compact JavaScript DSL that renders PNGs and lets the user watch the painting live in a browser. Use when asked to draw, design or iterate on pixel art or game assets.

Production Go playbook. Use when writing or reviewing Go: errors, goroutines, byte payloads, parsers, and switches on external input. Worked cases are in references/bad-vs-good.md. Do not use for JavaScript, TypeScript, or API-contract design.

Rigorous, severity-ranked review of a diff, PR, or file. Use when you want a thorough check of correctness, security, performance, design, readability, and test coverage with actionable feedback.

Guide, evaluate, and architect fullstack applications covering modern Frontend UI component design, state management, and robust Backend architecture. Use when designing end-to-end features, refactoring component hierarchies, decoupling API/data access layers, reviewing PRs for architectural debt, or solving frontend-backend integration friction.

Production data-access playbook for the N+1 query problem. Use when code queries a database inside a loop, an ORM lazy-loads a relation per row, or a list endpoint is fast at 5 rows and slow at 50. Worked cases are in references/bad-vs-good.md. Do not use for HTTP contract design or for Go/JavaScript language style.

Design or review REST/RPC API contracts that are consistent, evolvable, and hard to misuse. Use when defining new endpoints, reviewing an API surface, or resolving naming/versioning/error-shape questions.

Turn a committed intent.md into spec.md (requirements and design in one artifact), with policy concerns and open decisions flagged inline. Use after capture-intent and before plan mode.

Best practices for linking tools to interactive frontend widgets using @Widget and @nitrostack/widgets SDK (including state sync, tool calling, display modes, media queries, and chat actions).

>- Comprehensive guide and workflow for modern full-stack web application development using TypeScript and JavaScript. Covers frontend UI (React, Vite, Next.js, component architecture, modern CSS, accessibility, state management) and backend services (Node.js, Express, Fastify, REST/GraphQL APIs, database modeling, authentication, security, and end-to-end type safety). Use this skill whenever scaffolding, developing, refactoring, or reviewing full-stack web applications.

Generate high-utility, tool-agnostic ASCII diagrams and flowcharts within code comments or documentation, following the formal "Design Space of ASCII Drawings" (Hayatpur et al., 2024). Use when the user asks to "visualize," "diagram," "flowchart," or "map out" a process, data structure, or system architecture using plain text.

Use after system-architect to generate specs/DESIGN_SYSTEM.md, specs/CODE_STYLE.md, and specs/TESTING.md from specs/PRD.md, specs/ARCHITECTURE.md, specs/DATABASE.md, and specs/SECURITY.md. Supports both TypeScript and Python stacks, headless/CLI products, and LLM evaluation harnesses.