Web & Frontend

peterbamuhigire Bundle

Use when an interface flow needs a proven behaviour, navigation, action, layout, or data-display pattern selected from task and context. Do not use for visual styling or per-component state fidelity; route those to practical-ui-design or component-states.

peterbamuhigire Bundle

Use when existing design-audit findings must become a prioritised remediation plan, redesign, re-test, and measured before/after result. Use design-audit or product-design-audit to diagnose problems and design-qa-and-pre-launch-review for the final release verdict.

peterbamuhigire Bundle

Use when an Android phone, tablet, foldable, or Compose screen needs native Material navigation, components, states, accessibility, and adaptive behaviour. Do not use for iOS conventions or cross-platform unify/diverge decisions; route those to iOS design or parity.

peterbamuhigire Bundle

Use when designing, building, or debugging HTML email and newsletters across Outlook, Gmail, Apple Mail, dark mode, mobile, image-off, and limited-CSS conditions. Use ux-writing-and-microcopy for subject, preheader, and CTA wording, and responsive layout skills for non-email surfaces. copy).

peterbamuhigire Bundle

Use when designing beyond the WCAG floor for cognitive, visual, motor, assistive-technology, temporary, or situational ability ranges. Unlike accessibility-wcag-2-2-compliance, this creates inclusive adaptations rather than certifying criteria.

peterbamuhigire Bundle

Use when a page, screen, flow, or component is done and needs a final design go/no-go gate across implementation parity, browsers, devices, accessibility, performance, and anti-slop checks. Use design-audit for diagnosis before release.

peterbamuhigire Bundle

Use when a browser-rendered page, component, dashboard, or email must adapt across widths using intrinsic layout, fluid values, breakpoints, or container queries. Do not use to establish the base grid or for fixed-canvas documents; route those to layout-grid-and-spacing.

peterbamuhigire Bundle

Use when defining, naming, mapping, or exporting primitive, semantic, and component design tokens for colour, type, space, radius, elevation, motion, themes, or brands. Use component-library-architecture for component APIs and design-handoff-and-dev-spec for screen delivery.

peterbamuhigire Bundle

Use when designing or auditing an interactive UI for WCAG 2.2 AA, keyboard and focus behaviour, accessible names, screen readers, target size, reflow, authentication, or reduced motion. Use inclusive-and-assistive-design for needs beyond the compliance floor.

peterbamuhigire Bundle

Use when a single interactive control needs complete hover, focus-visible, pressed, selected, read-only, and transition fidelity. Do not use for aggregate data-region lifecycle handling or API architecture; route those concerns to system-state design or component-library architecture.

peterbamuhigire Bundle

Use when a game needs its player fantasy and interaction loop routed into HUD, art direction, feedback, camera, input, accessibility, testing, and engine handoff. Use ordinary app UI skills for non-game software and the four game specialists for focused craft.

peterbamuhigire Bundle

Use when a UI or document must support multiple locales, scripts, RTL direction, bidi text, string expansion, pluralisation, or locale formatting. Unlike responsive-layout work, this owns language-driven adaptation; translation wording remains with content design.

peterbamuhigire Bundle

Use when verifying or fixing text, UI, focus, border, status, or data colours for contrast and colour-vision accessibility. Unlike color-system-and-palette, this is the focused WCAG/APCA and non-colour-cue gate, not palette creation.

peterbamuhigire Bundle

Use when handing a design to engineering through token-referenced redlines, component and screen behaviour, states, breakpoints, accessibility notes, edge cases, and testable acceptance criteria. Use design-tokens-and-naming to define tokens and design-qa-and-pre-launch-review for final release.

peterbamuhigire Bundle

Use when auditing or redesigning consent, urgency, pricing, subscription, checkout, or retention flows for deception and coercion. Unlike product-design-audit, this is the focused ethics gate; conversion optimisation remains with its surface skill.

peterbamuhigire Bundle

Use when auditing this design engine or any rendered product for continuous improvement, evidence quality, visual readability, accessibility, AI trust, or repeatable remediation. Use design-audit for a single diagnostic without the Kaizen portfolio loop.

peterbamuhigire Bundle

Use when page speed, loading perception, Core Web Vitals, asset budgets, image or font weight, FOIT/FOUT, or layout shift must be treated as design constraints. Use engineering performance skills for code-level profiling and remediation.

peterbamuhigire Bundle

Use when producing or formatting an editable DOCX report, proposal, plan, specification, memo, or letter with named styles, contents, headers, footers, tables, figures, pagination, embedded fonts, and accessibility. Use pdf-proposal-and-bankable-document-design for final fixed-layout PDF craft.

peterbamuhigire Bundle

Use when facilitating a live or asynchronous design critique that needs a clear ask, safe feedback, a decider, and recorded outcomes. Unlike design-audit or heuristic evaluation, this runs the human review session rather than producing expert findings.

peterbamuhigire Bundle

Use when AI-slop definitions, banned fonts, visual tells, product-slop patterns, or anti-slop doctrine may have changed and the design engine needs a self-review pass coordinated with the digital-research engine before updating guidance.

peterbamuhigire Bundle

Use when defining or repairing a content inventory, taxonomy, sitemap, URL hierarchy, navigation system, labels, search, filters, or wayfinding. Use landing-page-and-conversion-design for page persuasion and practical-ui-design for visual component styling after structure is settled.

sidchaudhary Bundle

Designs a conversion-focused landing page: the copy framework matched to traffic source and awareness stage, section order, form length, proof placement, and prototype-ready HTML with Tailwind. Use for a lead capture page, a signup page or a launch page that does not exist yet. Boundary: builds a new page from scratch. `product-page-optimization` reviews an existing product detail page, and `checkout-optimization` reviews cart and checkout.

sidchaudhary Bundle

Uses the three Quality Score component ratings, expected click-through and ad relevance and landing-page experience, to find the weak link behind a keyword worth keeping, then drafts the smallest credible test, treating the score as a diagnostic rather than a number to chase. Use when valuable keywords show below-average components. Boundary: `product-page-optimization` audits a product page for on-site conversion and `responsive-search-ads` rewrites the assets; this only names which of the three links is weakest.

sidchaudhary Bundle

Reviews an existing product detail page, using the page itself, reviews, and buyer questions, to find clarity, trust, proof, and objection gaps, then returns a prioritized edit brief. Use when a product page isn't converting or before sending more traffic to it. Boundary: differs from `landing-page`, which generates new landing pages as HTML/Tailwind; this reviews a page that already exists and returns an edit brief, it doesn't generate new page code.

lloyd3126 Bundle

Inspect public AnnualReports.com company profiles and retrieve or verify current and archived annual report links through the Codex in-app browser. Use when the user names a company, ticker, company profile, annual report year, PDF/HTML/Form 10-K format, archive, report download, or sustainability-report link.

luyu2026 Bundle

从数据现象出发，生成可执行的产品决策建议，并以可视化 HTML 报告输出。当用户说"分析一下这组数据"、"这个指标为什么跌了"、"帮我做个留存分析"、"用户流失原因是什么"、"看看漏斗哪一步掉了"、"给我出个数据分析报告"时触发。 也适用于：用户上传了 CSV/Excel 数据文件并要求分析洞察；用户提供了 SQL 查询结果要求解读；用户要求做指标拆解、归因分析、分群对比、A/B 实验分析；用户提到"指标树"、"漏斗"、"留存"、"转化率"、"DAU 下降"、"分群"、"归因"等数据分析关键词。 不适用于：纯 BI 看板搭建（用 xlsx）、纯 SQL 编写（直接写）、纯数据清洗（直接写脚本）。

luyu2026 Bundle

Clone live web pages into a local Next.js + Tailwind CSS project for rapid prototyping. Use this skill whenever a user shares a URL or screenshot and wants to replicate, redesign, or iterate on that page locally — whether they say "clone this site", "make a prototype based on this page", "recreate this UI", "build something that looks like this", or simply paste a link and ask you to turn it into code. Also trigger when the user wants to add new pages, modify existing pages, or extend a prototype project that was previously created by this skill. Even if the user just says "I want to build a page like X" with a reference link or image, this skill applies.

luyu2026 Bundle

Screenshot-to-HTML prototype generator with iterative refinement and learning memory. Use this skill whenever the user provides a screenshot, mockup, wireframe, or image of any UI and wants it reproduced as a working HTML prototype — or when they want to modify an existing prototype they previously generated. Also triggers on: "照这个做原型", "参考这个图", "把这个页面画出来", "this UI needs to be prototyped", "replicate this design", "convert this mockup to HTML", "帮我出个原型", "根据截图输出 HTML", or any image attachment combined with requests like "输出 HTML", "做成页面", "帮我实现". Even if the user just sends a screenshot with a brief instruction like "加一个字段" or "这个也一样", this skill applies — it means they want you to modify or replicate the UI shown. When in doubt, if there's a UI screenshot in the conversation, use this skill.

nvidia-nemo Skill

Switch into Studio development mode for working on the NeMo Studio frontend in web/. Use when starting frontend work, building UI features, or working on React components.

nvidia-nemo Bundle

Reference hub for implementing UI changes in Studio. Use whenever building or modifying Studio frontend UI — pages, components, tables, panels, empty states, and other shared patterns. Routes to the standardized references below.

nvidia-nemo Skill

Unit testing workflow with Vitest and React Testing Library. Use when writing, running, or debugging unit tests for Studio components and utilities.

tfcbot Bundle

Discover viral TikTok and Instagram creator UGC for any mobile or web app, verify each candidate against the creator's profile bio (where affiliate CTAs hide) plus the video itself, then synthesize the shared pattern across confirmed top performers and propose a concrete format the user can film. Takes an app name (e.g. "Her75", "Cluely", "Cal AI"), runs keyword fan-out via Scrape Creators, ranks by engagement rate, watches the top 10 with VidJutsu using the bio as decisive context, and renders a sortable HTML report with inline video playback. Solves the gap that Kalodata / Fastmoss leave for non-TikTok-Shop apps — there is no closed-loop attribution for App Store / Play Store / web apps, so creator UGC for apps is currently uncatalogued. Bio-aware verification handles the case (Her75-style) where affiliate creators park CTAs in the bio and never mention the brand in any individual post.

memi-design Bundle

Vue 3 Composition API code generation — transforms Mémoire component specs into Vue SFCs with script setup, Tailwind styling, and composable patterns

memi-design Bundle

Design engineering principles for making interfaces feel polished. Use when building UI components, reviewing frontend code, implementing animations, hover states, shadows, borders, micro-interactions, enter/exit animations, or any visual detail work. Triggers on UI polish, design details, "make it feel better", "feels off", stagger animations, border radius, optical alignment, image outlines, box shadows.

memi-design Bundle

Flutter and Dart widget generation — transforms Mémoire component specs into Flutter widgets with Material 3, Riverpod state management, and responsive layouts

memi-design Bundle

Linear integration for Mémoire — sync design issues, component specs, and project tracking between Linear and the Mémoire registry