Web & Frontend

juspay Skill

Critique and polish an existing interface by finding hierarchy, consistency, usability, content, accessibility, and visual-quality defects before delivery.

juspay Skill

Add purposeful interaction and motion to HTML designs, including state transitions, feedback, navigation, disclosure, and reduced-motion behavior.

juspay Skill

Validate a Design Studio HTML artifact in the sandbox browser, fix rendering and runtime defects, then deliver exactly the tested file.

juspay Skill

Implement polished self-contained HTML interfaces with semantic structure, maintainable CSS, realistic content, and purposeful visual hierarchy.

juspay Skill

Make Design Studio artifacts responsive, keyboard operable, semantically correct, and readable across common viewport and input conditions.

juspay Skill

Structure a codebase/schema explanation as a self-contained HTML document ordered for a READER — mental model and flows first, deep per-component reference last — not in the order you explored it.

juspay Skill

Author architecture, ER, and flow diagrams as hand-written inline SVG inside a self-contained HTML page — no mermaid, no scripts, no CDN.

labspangaea Bundle

Import and normalize existing test-case data — xls/xlsx, CSV/TSV, PDF tables, or a pasted/markdown table — into this project's canonical test-case CSV and render it into the offline HTML console. Fuzzy-maps foreign headers onto the schema, standardizes Type (POS/NEG/VAPT), Outcome (TN/TP/FP/FN!) and the Priority scales, keeps source IDs (or generates them), infers missing tag fields, and flags uncertain ones for review. Use whenever someone has test cases in a sheet, CSV, PDF, or table and wants them in the project format or in the console — e.g. "convert this QA spreadsheet", "map this test matrix to our format", "normalize this testcases xlsx", "turn this PDF of test cases into the CSV", or pasting a table and asking to "add these to the matrix". Do NOT use it to author brand-new cases from a feature/flow (that's the testcase-architect agent), to import non-test-case data such as a customer or sales CSV into a database or chart, to edit/restyle the console, or to query an existing canonical CSV.

foxgeeek Skill

Consolidated performance dashboard across Meta, Google, and LinkedIn Ads. Aggregates spend, clicks, conversions, CTR, CPC, CPA into a single HTML report with spend/conversion share donut charts. Triggers on prompts about overall performance, cross-channel reports, or "how are we doing this month".

foxgeeek Skill

Detect Meta Ads creative fatigue before CTR collapses. Compares current vs previous window insights, flags ads with CTR drops above threshold or frequency cap breaches. Returns an HTML report with sorted fatigue list. Triggers on prompts about creative fatigue, CTR decay, frequency checks, or rotating stale creatives.

foxgeeek Skill

Google Ads period-over-period performance audit. Compares impressions, clicks, CTR, spend, CPC, conversions, CPA between current and previous window of same length. Generates HTML executive report. Triggers on prompts about performance audits, period comparisons, or "how is the account doing".

freecodecamp-universe Skill

Guidelines for working on Astro projects. Use whenever you detect an Astro project e.g. the project contains one or more .astro files or has astro as a dependency.

freecodecamp-universe Bundle

Add a dev-only, in-place curriculum authoring studio to a Vite or Astro web app whose curriculum is stored in Markdown, MDX, or JSON. Use when users want visual curriculum editing on the real learner page, source-backed autosave, hidden metadata forms, or draggable curriculum components. The studio runs inside the existing dev server, never a second one.

freecodecamp-universe Bundle

Most common WCAG 2.2 AA patterns for UI development. Load when writing, modifying, or planning any component, page, form, dialog, overlay, or interactive element. Does not substitute for runtime testing with assistive technology.

freecodecamp-universe Skill

Guidelines for how to test React components. Use whenever reading, creating or updating tests for React components. E.g. .jsx or .tsx files.

full-stack-skills Bundle

Python design patterns including KISS, Separation of Concerns, Single Responsibility, and composition over inheritance. Use this skill when designing a new service or component from scratch and choosing how to layer responsibilities, when refactoring a God class or monolithic function that has grown too large, when deciding whether to add a new abstraction or live with duplication, when evaluating a pull request for structural issues like tight coupling or leaking internal types, when choosing between inheritance and composition for a new class hierarchy, or when a codebase is becoming hard to test because of entangled I/O and business logic.

gagip Bundle

프로젝트 루트에 DESIGN.md — AI 코딩 에이전트가 UI를 일관되게 만들도록 브랜드의 시각 언어 (컬러·타이포·스페이싱·컴포넌트)를 실행 가능한 결정값으로 박은 "디자인 시스템 SSOT" — 를 생성하는 스킬. 기존 코드베이스를 스캔해 실제 값을 추출(현실 기술)하고, 스캔으로 못 채운 부분만 대화로 보완한다(하이브리드). 코드가 없으면 대화 중심으로 폴백한다. 산출 끝에는 프로젝트 지침 파일에 "UI 생성 전 DESIGN.md 읽기" 참조 줄 추가를 반드시 안내한다(DESIGN.md는 자동 로드되지 않기 때문). 그린필드거나 사용자가 육안검증·공유를 원하면 자기완결 preview.html(스와치·타입스케일·컴포넌트 갤러리, 라이트/다크 토글)을 조건부로 함께 생성한다. "미리보기도 만들어줘", "preview.html", "디자인 시스템 미리보기 페이지" 같은 표현에도 반응한다. 다음 표현이 나오면 반드시 이 스킬을 사용한다: "DESIGN.md 만들어줘", "design.md 생성", "디자인 시스템 문서 만들어줘", "디자인 가이드 문서 만들어줘", "디자인 토큰 문서화", "AI가 UI 일관되게 따를 문서 만들어줘", "브랜드 스타일 가이드 마크다운", "UI 컨벤션 문서", "우리 앱 디자인 규칙 문서로 박아줘". 사용자가 "AI/에이전트가 우리 앱 스타일을 일관되게 따르게 하고 싶다"거나, 프로젝트의 색·폰트·간격·컴포넌트를 문서로 고정해 매 UI 생성이 흔들리지 않게 하려 할 때는, 명시적으로 "DESIGN.md"라고 부르지 않아도 이 스킬을 쓴다.

gagip Bundle

근거를 읽고 판단하거나 공유하기 위한 짧은 단일 HTML 문서를 만든다. 사용자가 “내부 의사결정 문서”, “대표 전달용 HTML”, “조사 결과를 HTML 보고서로”, “나를 위한 개발 보고서”, “출처가 있는 HTML 정리”를 요청할 때 사용한다. 랜딩 페이지·제품 UI·웹앱 구현이나 단순 Markdown 변환에는 사용하지 않는다.

gitt510 Skill

Build a standalone, self-contained HTML document using the Holy Grail layout — a full-width masthead on top, then three columns: a sticky auto-generated contents-tree (TOC) that tracks scroll on the left, the body in the center, and a manual Related links rail on the right. Writes the result to {slug}.html in the directory the skill is invoked. Use whenever the user wants a navigable reference, guide, explainer, or spec as an HTML file that would benefit from in-page navigation. It owns the navigation structure; for visual direction it invokes frontend-design, and for up-to-date HTML/CSS practice it invokes modern-web-guidance. Triggers on "holy grail layout", "3-column reference html", "doc with a table of contents", "scroll-tracking TOC".

gordon1210 Bundle

Add and debug native window materials in Tauri 2 desktop apps on macOS and Windows. Use when implementing macOS vibrancy or Liquid Glass, Windows Mica or Acrylic, a translucent sidebar or titlebar, transparent WebView content, platform-specific opaque fallbacks, or diagnosing a native effect hidden behind gray, white, black, Canvas, or other opaque frontend backgrounds.

greenpau Bundle

Build, customize, or update AuthCrunch authentication portal themes using Go HTML templates, CSS, logos, favicons, banners, and backgrounds. Use for filesystem template overrides and their UI/static-asset configuration; the embedded React profile application has a separate build.

ytvee-dev Bundle

Define user goal, scope, constraints, and done criteria before standard or deep frontend work. Skip micro-fixes, obvious type errors, tiny styling changes, and isolated direct edits.

ytvee-dev Bundle

Verify rendered frontend evidence after implementation, including screenshot comparison, responsiveness, overflow, visible states, and scoped visual regression. Use available browser tooling only; exclude static lookup, routine code review, lint, builds, onboarding, and tool detection.

ytvee-dev Bundle

Detect frontend tool capabilities, report gaps, verify official setup sources, plan approval-gated MCP changes, or update project/mcp-profile.md. Prefer capabilities over provider names; never install or configure without approval.

ytvee-dev Bundle

Turn user-supplied screenshots, copied inspect values, exports, assets, or design notes into a strict frontend Design Implementation Spec. Live design links alone are insufficient.

ytvee-dev Bundle

Create, resume, analyze, or converge standard and deep frontend execution plans with traceable slices, evidence, and stop/resume state. Skip lightweight isolated edits.

ytvee-dev Bundle

Run scoped frontend lint verification, repair related lint failures, or plan explicitly requested lint setup. Prefer existing commands; dependencies, scripts, and config changes require approval.

ytvee-dev Bundle

Refresh local-only project/** facts and frontend path indexes after stack, routing, styling, asset, verification, docs/tool, design-reference, pattern, or ownership changes. Do not put project facts in reusable skills.

ytvee-dev Bundle

Diagnose and fix frontend defects from evidence, including unclear UI/runtime errors, broken routes, styling regressions, and hydration or client issues. Reproduce before editing; exclude planned refactors and backend-only debugging.

ytvee-dev Bundle

Set subject-grounded visual direction for standard or deep UI work, redesign, polish, critique, anti-template review, or design handoff. Skip technical micro-fixes and isolated code edits.

ytvee-dev Bundle

Review frontend quality from evidence across code, UI, architecture, TypeScript, security, performance, verification, decomposition, UX, and anti-slop concerns. Returns pass, concerns, or fail without implementing unrequested fixes.

ytvee-dev Bundle

Perform bounded, behavior-preserving frontend refactors such as component extraction, file moves, prop or interface cleanup, state simplification, and TypeScript tightening. Excludes bugfixes, features, redesign, packages, and unapproved behavior changes.

ytvee-dev Bundle

Plan a new frontend project or first vertical slice from a product idea, with approval gates before scaffolding. Excludes existing-project micro-fixes, automatic scaffolds, package installation, UI libraries, and test setup.

ytvee-dev Bundle

Adapt this .agents bundle to a frontend project using approved native pointers, local-only overlays, stack detection, skill applicability, tool capabilities, client and verification facts, optional loop memory, and context cache. Do not create app code or overwrite instructions.

ytvee-dev Bundle

Implement an approved Design Implementation Spec or screenshot-derived spec in React/Next.js using existing CSS Modules, Redux, TanStack, and Axios conventions. Excludes unrelated stacks, live design tools, and new styling systems.

ytvee-dev Bundle

Ground standard or deep UI work in product category, page pattern, design dials, domain UX risks, and anti-patterns before visual direction. Produces a brief, not code or tool setup.