Web & Frontend

flpbalada Skill

Simplify recently changed code without changing behavior. Use after implementation when working code has excess nesting, repetition, indirection, unclear names, redundant branches, or needless abstraction. Scope stays near touched code and favors guard clauses and readability. For larger planned restructuring use refactoring; for extracting component pieces use decompose.

flpbalada Bundle

Build or refactor React forms with React Hook Form. Use when working with useForm, register, handleSubmit, formState errors, defaultValues, validation rules, Controller, useController, FormProvider, useFieldArray, Zod or other resolvers, server submissions, and TypeScript form values. For simple local input state without React Hook Form use react-use-state.

flpbalada Skill

Use React useState for simple local component state. Use when adding UI state, inputs, counters, selected IDs, active tabs, local arrays or objects, updater functions, initializer functions, or debugging stale reads and mutation bugs. Prefer derived values, useRef, useReducer, context, or server-state libraries when state should not live in useState.

flpbalada Skill

Name code identifiers clearly and consistently. Use when naming or reviewing variables, functions, booleans, classes, files, modules, React hooks, event handlers, props callbacks, error values, and domain concepts; reducing ambiguity, duplicated context, contractions, or misleading singular/plural names. For larger code-quality review use code-reviewer.

flpbalada Skill

Organize React, Next.js, or TypeScript projects with feature-based architecture. Use when starting or reorganizing an app, deciding where files belong, separating app/features/shared layers, preventing cross-feature imports, designing module boundaries, or applying Bulletproof React-style structure. For high-level architecture tradeoffs use architecture-review; for single-component splitting use decompose.

flpbalada Skill

Decide when to use React useCallback. Use when callback identity affects memoized children, dependency arrays, custom hooks, event handlers passed through props, or unnecessary re-renders. Avoid defaulting to useCallback for every function. For state update correctness use react-use-state; for effect dependency alternatives use react-useeffect-avoid.

flpbalada Bundle

Find and abridge important or meaningful diff changes into an HTML reading review. Use for latest commit, staged or working-tree changes, a revision, range, branch diff, or supplied unified diff.

flpbalada Skill

Apply CSS container queries for parent-size responsive components. Use when cards, widgets, panels, sidebars, forms, or component-library elements must adapt to their container width with @container, container-type, container-name, or Tailwind @container variants. Use media queries instead for page-level viewport layout, global breakpoints, or full-page composition.

flpbalada Bundle

Avoid unnecessary React useEffect and choose better alternatives. Use when reviewing effects, derived state, prop-to-state copies, event handling, form resets, extra renders, stale synchronization, or async/server data patterns. Keep useEffect for external systems like subscriptions, timers, browser APIs, third-party widgets, analytics, or document title. For callback identity use react-use-callback.

flpbalada Skill

Write, review, or fix resilient Playwright tests around user-visible behavior. Use for locators, web-first assertions, auto-waiting, fixtures, isolation, test data, mocks, projects, trace debugging, and flaky browser tests. For axe, WCAG, ARIA, keyboard, or accessibility-specific scans use playwright-accessibility-testing.

flpbalada Skill

Place React and Next.js "use client" boundaries correctly. Use when adding client components, hooks, event handlers, browser APIs, client-only libraries, or fixing Server Component errors about hooks, async clients, or event handlers. Keep data fetching on server when possible and remove redundant directives. For generic React state or effects use their dedicated skills.

flpbalada Bundle

Configure Tailwind CSS v4 with the CSS-first setup. Use when installing Tailwind v4, migrating from v3, setting up Vite, PostCSS, CLI, or framework integration, defining @theme tokens, using @source, configuring plugins, debugging content detection, or checking browser support. For component-level utilities, variants, CVA, or tailwind-variants use code-architecture-tailwind-v4-best-practices.

flpbalada Skill

Implement Next.js image art direction with getImageProps(), picture, source, and img. Use when mobile, tablet, or desktop need different image assets, crops, focal points, compositions, or carousel media while keeping Next.js image optimization. Do not use for simple responsive sizing of the same image; use normal next/image sizes for that.

flpbalada Bundle

Scan TypeScript and React code for precise signals and contextual hotspots. Use when listing potential code smells for review.

flpbalada Skill

Write, review, or fix Playwright accessibility tests with @axe-core/playwright. Use for axe scans, WCAG A/AA tags, ARIA names, roles, labels, keyboard/focus checks, accessibility audit failures, exclusions, and critical page or flow a11y coverage. For general Playwright locator, assertion, fixture, or flake guidance use playwright-best-practices.

flpbalada Skill

Handle expected Next.js Server Action errors with TanStack React Query mutations. Use when server actions, mutationFn, useMutation, onError toasts, throwOnError, QueryBoundary, ActionResult discriminated unions, translated error codes, or production-safe client error messages are involved. Do not use for generic React Query data fetching or unrelated form validation.

flpbalada Skill

Decide whether to abstract, duplicate, inline, or split code. Use when creating shared utilities, components, facades, hooks, service wrappers, or DRY/WET refactors; reviewing parameter-heavy helpers, option flags, shallow facades, or premature abstractions. For broad behavior-preserving restructuring use refactoring; for component extraction use decompose.

flpbalada Skill

Choose Tailwind CSS v4 component styling patterns. Use when building Tailwind components, buttons, cards, variants, slots, state styles, or design tokens; choosing utilities vs CVA vs tailwind-variants; avoiding @apply; or migrating v3 component patterns. For project-level Tailwind installation, PostCSS/Vite setup, @source, plugins, or browser support, use tailwind-v4-configuration instead.

jayden-dang Bundle

Use when a screen or feature's look and feel needs deciding with the user before it is specified or built — "what should this look like", "show me a few design directions", "make some variants and let me pick", a UI mockup exploration clicked through in the real browser. Produces 2–5 divergent real-HTML variants behind a floating switcher (embedded in the running app, or standalone pages when no app exists), a review-and-amend loop with the user, and a locked ui-brief.md that design-solution's UI design section lifts instead of re-deciding. Not for judging an already built diff (inspect-ui), logic or state spikes (run-spike), or a standalone document page (craft-page).

jayden-dang Bundle

Produces a team-shared HTML pitch-and-map packet under docs/explainers/ for a git range. Run it with /brief-team.

jayden-dang Bundle

Use when a diff or branch touching browser-rendered surfaces (HTML, CSS/styling, JSX/TSX/Vue/Svelte components, templates) needs its visual and interaction quality judged in the real running app before merge — the live design review invoked by `inspect-change`'s UI lane, or when the user asks to design-review a change, check how it looks, responsive breakage at mobile widths, focus visibility, contrast, dark mode, or off-token styling. Produces a screenshot-backed UI finding set across desktop/tablet/mobile viewports, interaction and composed states, and design-contract conformance — settling cascade and severity questions by driving the app, never by inference from the diff. Not for asserting spec'd behavior e2e (validate-ui), authoring a human product walk (write-flow-guide), or styling a standalone page (craft-page).

jayden-dang Bundle

Build one self-contained HTML teach packet for a finished build — the journey (waves, deviations) plus how the feature operates inside the surrounding system. Run it with /teach-build.

jayden-dang Bundle

Produces a single HTML comprehension packet for a code change — Background, Intuition, Code, Quiz. Run it with /study-change.

wangjs-jacky Bundle

通过简洁的 Markdown 表格、Mermaid 图或自包含 HTML，以可视化方式解释比较、映射、流程、结构、数据关系、交互和 UI。用于用户说“展示给我看”“画出来”“可视化一下”，调用 $show-me，指定 markdown table、mermaid 或 html，或需要把最近对话中的复杂关系直观呈现时。

wangjs-jacky Bundle

把文章、数据或素材制作成单个自包含、零外部依赖、双击即开的精致 HTML 成品，适用于动效长文、仪表盘、数据故事、对比页、时间线和分步图解。当用户明确要求单文件 HTML、可离线打开或嵌入文档平台时使用。不用于需要部署的完整站点项目，该场景使用 web-flow。

wangjs-jacky Bundle

将一句话产品意图落地为真实、带动效、可部署的前端站点，通过 research/prototype/design/build/deploy 子 Skill 渐进执行，并在每阶段交接调用 web-flow-benchmark 做有限评测；每个子 Skill 独立维护自己的错误 memory。用于仿做网站、建设官网或落地页、产出项目代码并部署到真实 URL；不处理纯后端、纯 CLI 或非可视产物，单文件 HTML 成品应使用 crafted-web。

wangjs-jacky Bundle

在设计、开发或交付 Happy/Paws App 与 PC Web 时按需参考 Happy/Paws 经验，包括移动端架构、React Native/Expo 取舍、PC Web 视觉基线、验证、OTA、安装包与 Release 边界。用于用户明确要求参考 Happy/Paws，或当前问题与这些真实工程经验高度匹配时；它只提供上下文，不是 Workflow，也不强制复制 Happy 的技术栈或具体尺寸。

wangjs-jacky Bundle

web-flow 内部的原型设计阶段：以 wireframe 和 prototype 两种模式，把源接地内容转成低保真草图与可观察的视觉或交互原型；运行时按需复用外部能力，缺失时降级为 HTML/CSS。仅在 web-flow 主 Skill 明确调用时使用。不要因普通用户请求单独触发。

wangjs-jacky Bundle

终端 Claude Code ⇄ Obsidian 的上下文桥。① 卸货：把工作产物(md/html/图片)+可选完整会话 transcript 落到 vault 的 _inbox 暂存区；② 接手：在新会话/新 AI 里查询 _inbox、列出可恢复的会话与文件结构、读 transcript 恢复全量上下文继续。触发词：ob-bridge、落地到 obsidian、卸货到 inbox、从 obsidian 恢复、继续之前的工作、接手 inbox。

halojerry Bundle

妙搭（Spark/Miaoda）应用开发与托管：应用创建、HTML静态站点发布、本地全栈开发、云端生成迭代。当用户要开发/新建一个系统·工具·平台·应用，或要本地开发 / 云端开发 / 修改 / 部署 / 发布 / 上线 / 拿可分享链接，或用 HTML 做页面·网站给人看，或提到妙搭/Spark/Miaoda、应用数据库、可见范围时使用。不负责普通云盘文件上传（lark-drive）、飞书文档编辑（lark-doc）、原生幻灯片创建（lark-slides）。

halojerry Bundle

独特吸睛、审美好、有特色、美观全面的前端设计。当任务涉及前端界面、项目展示页、系统演示、大屏可视化、可视化平台、微信小程序 UI、移动端界面、设计系统、Tailwind v4、shadcn/ui、Next.js、React、Vite、可访问性、动效、重设计审计时使用。不只是能用，而是好看、统一、清晰、有亮点、有视觉记忆点，适合展示/答辩/演示/落地。按主题选风格：科技感、学术感、农业智慧化、数据可视化、极简、玻璃拟态、卡片式、大屏、管理系统、移动端、小程序等。

ariadoss Skill

Accessibility audit for frontend changes — WCAG 2.2 AA, screen-reader compatibility, keyboard navigation, focus management, ARIA correctness, color contrast, and reduced-motion. Static diff-scoped analysis (safe to auto-run) plus an optional dynamic axe pass against a running app. Use when asked to "check accessibility", "a11y audit", "screen reader check", "WCAG", "is this accessible", "keyboard navigation", "ARIA review", or after heavy frontend work.

ariadoss Skill

Full per-feature QA pipeline: audit → fix → verify. Runs the complete multi-dimensional fan-out (tests, correctness, security, DB, frontend perf, browser QA, design, accessibility, coverage) scoped to the current branch's diff, FIXES what each check finds, re-verifies the fixes, then emits a pass/fail ship-readiness verdict on the repaired branch. Run it when a feature is finished, before /finish-branch and /ship. Use when asked to "run full QA", "qa-full", "feature done — check it", "is this ready to ship", "pre-ship check", "full quality gate", or "fix everything before ship".

ariadoss Skill

Turn any folder of code, docs, papers, or images into a queryable knowledge graph — interactive HTML, GraphRAG-ready JSON, and a plain-language audit report.

ariadoss Skill

iOS and Swift development expert covering Swift best practices, SwiftUI patterns, Human Interface Guidelines compliance, accessibility audits, navigation patterns, and app architecture. Use when building iOS apps, reviewing Swift code, or planning app architecture.

ariadoss Skill

Expert UI/UX design collaboration for creating unique, accessible interfaces. Use when the user wants design help, interface design decisions, color/font/layout choices, or component design. ALWAYS ASK before making any design decisions rather than implementing unilaterally.