Art & Design

Use when a change is likely to exceed ~300 changed lines, when work spans several commits or stages, when opening a pull request, when receiving or responding to review feedback on any pull request, or when rebasing or landing a stack of dependent PRs. Covers the PR size budget and what counts toward it, how to split and stack PRs, sequential stage-by-stage review, and how to handle review findings by verifying each one, then fixing it or pushing back.

Score a product draft (listing, template, guide, landing page or any artifact) against its brief's success criteria with harsh, concrete fixes ranked BLOCKER / MAJOR / MINOR, then recommend REBUILD or ADVANCE TO TESTER. No vague praise. Critique only; never edits live products or publishes.

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.

Use when writing, rewriting, reviewing, or optimizing copy for a website, landing page, homepage, hero section, product page, feature page, onboarding flow, headline, or CTA. Clarify who the site is for, express the visitor's real problem or desired outcome, explain how the product solves it, and make the writing sound natural, specific, appealing, and credible rather than generic or AI-generated. Also use for website messaging, positioning, and copy audits.

Elite frontend image-direction skill for generating premium, conversion-aware website design references. CRITICAL OUTPUT RULE — generate ONE separate horizontal image FOR EVERY section. A landing page with 8 sections produces 8 images. Never compress multiple sections into one image. Enforces composition variety (not always left-text / right-image), background-image freedom, varied CTAs, varied hero scales (giant / mid / mini minimalist), narrative concept spine, second-read moments, and a single consistent palette across all images. Optimized for landing pages, marketing sites, and product comps that developers or coding models can accurately recreate.

Use this skill to generate well-branded interfaces and assets for se7en (Download Everything & Upscale), either for production or throwaway prototypes/mocks/etc. Contains essential design guidelines, colors, type, fonts, assets, and UI kit components for protoyping.

Make a finished image, or a set of them, from a plain prompt. Posters and flyers, social posts and carousels, YouTube thumbnails, banners, link previews, logos and wordmarks, app icons and favicons, infographics and charts, diagrams, app store screenshots and UI mockups, 3D product shots, ads, slide backgrounds, illustrations. Designs in HTML, SVG and WebGL, renders pixel-exact in headless Chromium, measures the result on real pixels (contrast, clipping, platform safe areas, missing glyphs) and exports PNG, JPG, WebP, AVIF, SVG, print-ready PDF and icon sets with alt text. Free local tools only, with no paid APIs, accounts or watermarks, in any language including right-to-left. Use it whenever someone wants an image, poster, thumbnail, banner, logo, mockup, graphic or illustration made, even when they only describe the thing.

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.

Design, implement, and audit accessible UI to WCAG 2.2 Level AA across Web, iOS, and Android — semantic ARIA roles and labels, accessibility traits and hints, focus management, contrast, target size, and screen-reader support. Use when building or auditing UI for accessibility compliance, keyboard navigation, or screen-reader support.

Export the enclosure's printable parts (STL/3MF) and CAD (STEP/F3D) from Fusion 360. Use when the user wants files to print, slice, share, or archive a design revision.

Choose architecture styles from measurable quality requirements. Use when comparing a modular monolith, service-based design, microkernel, event-driven architecture, or microservices, and when turning decisions into fitness checks.

Review replication, consistency, partitioning, transactions, and message processing. Use when writes can be retried, consumers can crash, replicas can lag, or a design claims exactly-once effects.

Optimizes database queries and improves performance across PostgreSQL and MySQL systems. Use when investigating slow queries, analyzing execution plans, or optimizing database performance. Invoke for index design, query rewrites, configuration tuning, partitioning strategies, lock contention resolution.

Design implementation-ready, safe change plans for the Treatment Django backend, including Django APIs, ORM, migrations, Celery, integrations, security, and cross-app refactors. Use before substantial implementation or when architecture or change impact needs evaluation.

Reliability is the discipline of staying up when things around you fail — because they will. Design for partial failure first; happy paths take care of themselves.

You can't fix what you can't see. Observability is designed-in, not bolted on after an incident. If a question about production needs a code change to answer, instrumentation is wrong.

Performance is a feature. Design for the P99, not the average. Measure before you optimize — intuition is almost always wrong about where the time is going.

微信公众号文章排版引擎，将 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.

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.

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.