Web & Frontend

kkoppenhaver Bundle

Generate branded blog/social featured images by authoring an HTML "card" and rendering it to a PNG with headless Chromium ("HTML first, then to PNG"). Use when the user wants a featured image, hero/header image, OG or social card, or any branded post graphic for a content project. Handles one-time per-project brand setup (colors, fonts, dimensions), then composing and rendering per-post images. Triggers include "make a featured image", "create a blog header/social card", "og image", "render this to PNG for the post", or branded post graphics for a repo's blog.

tale-project Bundle

Use this skill whenever you write or edit end-user documentation — a page under a docs content tree, a docs navigation or sidebar file, a docs landing or overview page, a screenshot or code example embedded in docs, or a failing docs structural check. It owns the journey-first method — organize every page around what the reader is trying to do, show the UI before describing it, prove behaviour with runnable examples, and use the docs component vocabulary (steps, tabs, code groups, callouts, frames, cards) with discipline instead of walls of prose. Before writing anything, discover the repo's own docs contract — its docs guide, its component registry, its structural test suite — and let that contract override this skill's defaults. Never write a docs page from imagination, never describe a UI you have not driven, and never ship a hand-captured screenshot. Page-type playbooks, component rules, screenshot doctrine, worked examples, and mechanics live in companion files here.

tale-project Bundle

Use this skill any time a spreadsheet file is the primary input or output. This means any task where the user wants to: open, read, edit, or fix an existing .xlsx, .xlsm, .csv, or .tsv file (e.g., adding columns, computing formulas, formatting, charting, cleaning messy data); create a new spreadsheet from scratch or from other data sources; or convert between tabular file formats. Trigger especially when the user references a spreadsheet file by name or path — even casually (like "the xlsx in my downloads") — and wants something done to it or produced from it. Also trigger for cleaning or restructuring messy tabular data files (malformed rows, misplaced headers, junk data) into proper spreadsheets. The deliverable must be a spreadsheet file. Do NOT trigger when the primary deliverable is a Word document, HTML report, standalone Python script, database pipeline, or Google Sheets API connector, even if tabular data is involved.

marve10s Skill

Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".

marve10s Bundle

Best practices for Remotion - Video creation in React

sanity-io Bundle

Anti-patterns and best practices for building Sanity Studio plugins in this monorepo. Use when writing, reviewing, or refactoring plugin code under plugins/ — especially for styling/CSS, component performance, and runtime cost. Triggers on vanilla-extract, raw <style> tags, styled-components, theming, inline styles, or questions about how plugins should be structured here.

sanity-io Skill

Step-by-step procedure for migrating a workspace off styled-components to vanilla-extract (zero-runtime CSS). Use when converting styled() components to .css.ts files, removing a styled-components dependency, adding a ./bundle.css export, or when asked to migrate styling to vanilla-extract. Pair with the sanity-plugin-best-practices styling reference for the underlying patterns.

adamos486 Bundle

Use when turning a repo, pull request, plan/design doc, architecture, article, blog post, book, lecture, or transcript into an interactive learning artifact — a self-contained offline walkthrough.html and/or a deployable learning hub. Triggers include "onboarding guide", "walk me through this PR/codebase/design", "interactive explainer", "teaching site", "publish docs to GitHub Pages".

operately Bundle

Operately frontend data fetching with TanStack Query. Use when adding or changing page loaders, model hooks, Api.* calls, mutations, useLoadedData, Pages.useRefresh, or any web UI backend request. New code must use TanStack. When fixing or extending an existing surface, migrate that surface's API calls to TanStack in the same change.

operately Bundle

Defines where UI components belong in Operately (TurboUI-first). Use when creating, changing, reviewing, or migrating UI components, adding features that need UI, or deciding whether to refactor legacy app UI in app/assets/js/components or app/assets/js/features. Covers pure TurboUI components, component reuse, the app bridge pattern, and legacy migration scenarios.

oubakiou Bundle

token cost の削減を第一目標として、汎用の文章（技術記事・リリースノート・README・議事録・説明文など）の 生成・改稿・推敲・リライトを subagent に委譲するスキル。 ユーザーが「文章を書いて」「記事にして」「推敲して」「リライトして」といった形で、 文章自体を成果物として求める場合に使う。 Notion / docs / README / issue など後から読まれる文書へ、日本語 200 文字以上（英語 100 words） または箇条書き 3 項目以上の説明文を書く場合は、分析・実装が主目的でもこの skill を通す。 HTML 成果物は delegate-htmldoc、コード実装は delegate-implement、調査は delegate-explore を使う。 コード・構造化データ・表構造の変更・リンクや番号の差し替え・1〜2 文修正には使わない。 prose の作業を委譲する場合は、この skill を使う。generic な subagent で代替しない。

oubakiou Bundle

token cost の削減とデザインの一貫性確保を目標として、固定デザインテンプレートに沿った 自己完結型 HTML ドキュメントの生成を安価な subagent に委譲するスキル。 調査結果・レポート・issue まとめ・技術資料・議事録などを「HTML で」「ドキュメントにして」 「レポート化して」といった形で文書化する要求に使う。 同梱テンプレートの CSS と component 語彙に content を流し込むため、実行ごとのデザイン揺れがない。 対象は静的文書のみ。ダッシュボードなどインタラクティブ・JS を要する成果物、 デザインの新規設計、Web アプリの UI 実装には使わない（delegate-implement を使う）。 htmldoc の作業を委譲する場合は、この skill を使う。generic な subagent で代替しない。

pegasystems Skill

Rules and guidelines for creating components in the core Kotlin module

pegasystems Skill

Rules and guidelines for writing unit tests for JavaScript components in the scripts/ bridge layer

pegasystems Skill

Rules and guidelines for creating component renderers in the ui-renderer-cmp Kotlin module

pegasystems Skill

Rules and guidelines for creating Compose Multiplatform UI components in the ui-components-cmp module

pegasystems Skill

Rules and guidelines for overriding UI field components in the Compose Multiplatform SDK

peternicholls Bundle

Verify, record, and polish Charm terminal user interfaces with automated and manual terminal UX checks. Use when Codex needs to test Bubble Tea update/view behavior, run Go tests, capture screenshots or videos with VHS, inspect terminal rendering at multiple sizes, validate keyboard-only workflows, accessibility/plain-output paths, error/loading/empty states, or produce completion evidence for Charm CLI/TUI work.

peternicholls Bundle

Add, configure, test, and compose Charm Bubbles components in Bubble Tea applications. Use when Codex needs text input, text area, table, list, viewport, spinner, progress, paginator, timer, stopwatch, help, key bindings, file picker, focus management, or reusable Bubble Tea component patterns.

pingidentity Skill

Use when a user asks for help with Ping Identity SDK, ForgeRock SDK, or Ping Orchestration SDK integration without specifying a platform — phrases like "help me add Ping auth", "I want to use PingOne", "get started with the Ping Orchestration SDK", "add Ping login to my app", "integrate the ForgeRock SDK", "use the pingidentity SDK". Probes the project to detect Android, iOS, JavaScript, or React Native, asks if ambiguous, and routes to the matching umbrella skill (ping-orchestration-android-sdk, ping-orchestration-ios-sdk, ping-orchestration-javascript-sdk, ping-orchestration-react-native-sdk) or to forgerock-to-ping-journey-migration when ForgeRock SDK references are present (forgerock-android-sdk, forgerock-ios-sdk, @forgerock/javascript-sdk).

pingidentity Bundle

Guide for building React Native apps that integrate with the Ping Identity React Native SDK (npm scope: `@ping-identity`; packages: `@ping-identity/rn-journey`, `@ping-identity/rn-oidc`, `@ping-identity/rn-fido`, `@ping-identity/rn-push`, `@ping-identity/rn-oath`, `@ping-identity/rn-binding`, `@ping-identity/rn-device-client`, `@ping-identity/rn-device-profile`, `@ping-identity/rn-external-idp`, `@ping-identity/rn-core`). Use this skill whenever the user is: (1) building any React Native app that authenticates against PingOne, PingOne Advanced Identity Cloud (AIC), or PingAM using Journey or OIDC flows; (2) rendering Journey callbacks (NameCallback, PasswordCallback, FIDO, DeviceBinding, etc.) in React Native components; (3) configuring `createJourneyClient` or `createOidcClient`; (4) using `useJourney`, `useJourneyForm`, `JourneyProvider`, `useOidc`, or `OidcProvider`; (5) handling node types (ContinueNode, SuccessNode, FailureNode, ErrorNode); (6) wiring OIDC browser redirect URIs for iOS and Android; (7) a

pingidentity Bundle

Use when building ReactJS web authentication with the Ping Orchestration JavaScript SDK (DaVinci) using `@forgerock/davinci-client` — scaffolds a complete React SPA authentication flow against PingOne DaVinci. Handles DaVinci client configuration, OIDC token exchange, dynamic DaVinci collector rendering in React (text, password, social login, MFA, FIDO2/passkeys, PingOne Protect), protected routes, user profile, and logout. Invoke when the user asks to "use @forgerock/davinci-client in React", "render DaVinci collectors in a React app", "set up PingOne DaVinci authentication in React", "build a React SPA with DaVinci", "add DaVinci login to my React app", or "use the DaVinci SDK with Vite and React". Also covers migrating a React app from `@forgerock/javascript-sdk` to `@forgerock/davinci-client`.

pingidentity Bundle

Use when building ReactJS web authentication with Ping Identity — scaffolds a complete React SPA authentication flow using the Ping Orchestration JavaScript SDK (`@forgerock/journey-client`, `@forgerock/oidc-client`) against PingOne Advanced Identity Cloud (AIC) or PingAM. Handles Journey client configuration, OIDC token exchange, dynamic Journey callback rendering in React, protected routes, user profile, and logout. Invoke when the user asks to "use @forgerock/journey-client in React", "render Journey callbacks in a React app", "set up Journey authentication with React and Vite", "add PingAM login to my React SPA", "integrate AIC Journey in React", or "build a React app with Ping Identity Journey". Also covers migrating a React app from `@forgerock/javascript-sdk` to `@forgerock/journey-client`.

pipelex Skill

Bump the pinned `@pipelex/mthds-ui` (and `elkjs`) version that the generated ReactFlow HTML loads from jsDelivr. Re-fetches the bundle, recomputes SRI hashes, and updates the Python constants in `standalone_assets.py`. Use when user says "update graph ui", "bump mthds-ui", "update graph viewer", "new version of mthds-ui", or any variation of updating the CDN-pinned graph viewer assets.

platform-blocks Bundle

Build forms with the @platform-blocks/ui React Native library. Use when composing form screens with Form/Form.Field/Form.Input/Form.Submit or FormLayout/ControlField, wiring input components (Input, PasswordInput, TextArea, NumberInput, Select, AutoComplete, Checkbox, Switch, RadioGroup, SegmentedControl, Slider, PinInput, PhoneInput, DatePickerInput, TimePickerInput, ColorInput, FileInput), implementing validation (validationSchema, validationRules, validateValue, on-submit/on-blur with React state), choosing controlled vs uncontrolled inputs (value/onChangeText vs onChange, defaultValue/defaultChecked), or handling keyboards (KeyboardAwareLayout, KeyboardManagerProvider) and form accessibility.

platform-blocks Bundle

Install and configure the @platform-blocks/ui React Native library in an Expo or React Native app. Use when installing @platform-blocks/ui, wiring PlatformBlocksProvider, fixing peer-dependency or Metro "Unable to resolve module" bundling errors, setting up flash-free dark mode (including static web output), or configuring Jest/jest-expo in a consumer app.

platform-blocks Bundle

Add data visualization to a React Native or Expo app with @platform-blocks/charts. Use when installing the charts package, choosing among its 25 chart types (line, bar, area, pie/donut, scatter, sparkline, heatmap, candlestick, sankey, and more), theming charts to match the app via ChartThemeProvider and hostThemeBridge, wiring tooltips/crosshairs/pan-zoom interactions, or rendering streaming/live data.

platform-blocks Bundle

Build screen layouts with the @platform-blocks/ui React Native library. Use when composing screens with Flex/Row/Column/Grid, building responsive breakpoint-based layouts (GridItem span={{base, sm, md, lg, xl}}, useBreakpoint), applying spacing system props (p, px, py, m, mt, gap), assembling app shell / navigation chrome (AppShell, defineAppLayout blueprints), or laying out content in Cards, Surfaces, and Blocks.

platform-blocks Bundle

Theme the @platform-blocks/ui React Native library. Use when customizing the Platform Blocks theme (brand colors, ramps, spacing, radii, shadows), implementing dark mode or light/dark/auto color-scheme switching, defining custom color palettes, working with surfaces/elevation, resolving variant colors (filled/outline/light/subtle/surface/gradient), reading theme tokens in custom components, or styling web output via the injected --platform-blocks-* CSS variables and html classes.

platform-blocks Bundle

Display data with the @platform-blocks/ui React Native library. Use when rendering tabular data with DataTable (sorting, filtering, pagination, selection, bulk actions, server-side/manual pagination) or the low-level Table compound (Table.Thead/Tbody/Tr/Th/Td), building label/value detail lists with DataList, hierarchical Tree views with expansion/checkboxes/lazy loading, event feeds with Timeline, expandable sections with Accordion/Collapse/Spoiler, list rows with ListGroup, or status and identity chrome with Badge, Chip, Avatar/AvatarGroup, Indicator, Rating, Gauge, QRCode and Markdown.

platform-blocks Bundle

Show feedback and overlays with the @platform-blocks/ui React Native library. Use when raising notifications with Toast/ToastProvider/useToast, opening modals, bottom sheets or confirm prompts with Dialog/DialogProvider/useDialog/useSimpleDialog, attaching anchored overlays (Popover, Menu/MenuDropdown/MenuItem, Tooltip, ContextMenu), rendering inline messages with Alert, or showing loading and progress state (Loader, LoadingOverlay, Overlay, Progress, Ring, Skeleton), including open-state management with useDisclosure.

poooi Skill

poi-specific UI constraints and patterns — why hidden tabs and fleet decks must stay mounted, how to capture a previous value for CSS transitions, and why backdrop-filter must keep its external SVG filter. Use when editing views/components/**, assets/css/**, assets/svg/ui/**, when optimizing rendering of hidden panes, when adding a CSS transition driven by a changing selector value, or when touching blur/vibrancy styling.

poooi Skill

Building and launching poi locally — Babel 8 constraints that must not be regressed, the ELECTRON_RUN_AS_NODE trap, gulp build limitations, and the glob v13 Windows path flag. Use when editing babel.config.js, babel-hook.js, babel-register.config.js, gulpfile.js, build/**, app.ts, index.html, or package.json build config; when running `gulp build` or launching Electron; or when a build/plugin/i18n load silently produces nothing.

poooi Skill

Capture window-scoped before/after screenshots of the running poi UI over the Chrome DevTools Protocol to verify a visual change. Use when asked to screenshot poi, to show what a UI change looks like, or to confirm a CSS/layout/theme change actually renders — anything needing a picture of the app rather than a test result.

andyelessar Bundle

Microsoft WebUI Framework expertise — a language-agnostic server-side rendering framework where templates compile to a binary protocol and interactive Web Components hydrate as islands. Use when authoring, reviewing, or debugging WebUI components (`.html` + `.css` + `.ts` triplets), wiring up routes, hydrating with `WebUIElement`, configuring `webui build` / `webui serve`, or integrating SSR into a backend. Also trigger when the user mentions `@microsoft/webui`, `@microsoft/webui-framework`, `@microsoft/webui-router`, `WebUIElement`, `@attr` / `@observable` decorators, `protocol.bin`, `Router.start`, `Router.navigate`, `Router.ensureLoaded`, `<route>` / `<outlet>` tags, `keep-alive`, `pending`, `cache-tags`, or shadow-DOM scoped components from Microsoft. Do NOT use for unrelated UI libraries (React, Vue, FAST standalone, Lit, Blazor, or generic Web Components projects).

basic-xyz Bundle

当 Codex 需要为 Baku/Basic-XYZ 个人品牌构建 HTML 页面、个人网站、教程页、介绍页、landing page、App 型页面、作品集、图文卡片、小红书卡片，或需要根据品牌 DNA 与多套页面风格设计/更新个人虚拟形象、头像和视觉规范时使用。适用于前端视觉设计、品牌页面、Notion 风格暖白文档页、Baku workbench 工作台页、复古未来/主机终端/暗色技术作品集页面、图文转卡片、个人 IP 形象、设计系统复用和模板化 HTML 交付。