Web & Frontend

catcorner22 Bundle

Set up component testing with Playwright using a story gallery — scaffold stories and a gallery dev page driven by the built-in mount fixture, no dedicated component-testing runtime. Use when asked to test React or Vue components in isolation with Playwright, or to migrate off @playwright/experimental-ct-react / -vue. Scope boundary — Playwright-based component testing only; for Jest + React Testing Library component tests in an Adobe App Builder project use `appbuilder-testing` instead.

catcorner22 Bundle

Use when writing or fixing the server-side code of a Workfront App Builder extension — the Adobe I/O Runtime action the React SPA calls to do work the browser can't. Reach for this whenever the user is: structuring or editing action code; deciding what shape an action returns so the frontend can tell success from failure (the {data,error} body); passing the IMS token through and calling an external API from the backend so credentials never reach the browser; calling Workfront's own Public API v21 (search/count, bulk PUT with the updates param, custom DE: field filters); calling Workfront Planning or another Adobe service; or troubleshooting why a deployed action can't read secrets (process.env is empty once deployed — inputs flow .env → config inputs → params). Also covers CommonJS-only structure, require-adobe-auth, and registering actions in app.config.yaml / ext.config.yaml. For generic non-Workfront action templates and SDKs see appbuilder-action-scaffolder.

catcorner22 Bundle

Use when building or editing the React/Spectrum front-end SPA of a Workfront App Builder extension. Reach for this whenever the user is: registering or changing extension points in `ExtensionRegistration` — a Main Menu button, a left-panel (`secondaryNav`) item for a specific Workfront object type (Project, Task, Issue, Portfolio, Program), or a custom-form widget with specific height and width; adding a new route in `App.js` to match an extension point URL; reading the Workfront shared context to get the current user, `objCode`, `objID`, or `hostname`; calling a Runtime action from the SPA via `actionWebInvoke`; or debugging a widget or route that renders blank after being registered. Never call Workfront or Adobe APIs directly from the SPA — all API calls belong in a Runtime action (see `workfront-actions`).

tractorjuice Skill

[COMMUNITY] Assess Austrian digital accessibility obligations — applicability across BaFG (European Accessibility Act, private sector) and WZG (public sector), EN 301 549 / WCAG conformance, Barrierefreiheitserklärung, SMS market surveillance and FFG monitoring

jacob-balslev Bundle

Use when building an artifact whose purpose is to answer a specific question — paper sketch, wireframe, clickable mockup, wizard-of-oz, role-play, service prototype, or code spike — at the lowest fidelity sufficient to produce that learning. Do NOT use for production-grade component construction, design-system contribution, or building the actual ship-ready feature — those are design-module-composition and engineering implementation.

jacob-balslev Bundle

Use when building or reviewing interactive UI, forms, navigation, or dynamic content. Covers semantic HTML, keyboard access, focus management, labeling, state-change announcement, and reduced-motion / high-contrast preferences. Do NOT use for color-palette creation, visual branding, feedback-state staging, or prose reading-level accessibility - those belong to `visual-design-foundations`, `interaction-feedback`, and documentation respectively.

jacob-balslev Bundle

Use when deciding responsive page or screen structure: section order, scan pattern, grid/flex composition, breakpoints, viewport hierarchy, responsive media, and density. Do NOT use for user-goal decomposition (use `task-analysis`), navigation taxonomy (use `information-architecture`), visual polish (use `visual-design-foundations`), or component/token contracts (use `design-system-architecture`).

jacob-balslev Bundle

Use when designing or auditing form structure and validation UX: field grouping, required vs optional inputs, validation timing, client/server validation split, submission lifecycle, recovery, multi-step forms, and high-risk data entry. Do NOT use for labels and announcements alone (use `a11y`), validation-message wording (use `microcopy`), API schema design (use `api-design`), or stored data modeling (use `entity-relationship-modeling`).

jacob-balslev Bundle

Use when designing UI feedback around user actions and system state: loading, skeletons, optimistic updates, progress, success, errors, empty states, retries, disabled/pending states, autosave, undo, and perceived latency. Do NOT use for the words inside feedback (use `microcopy`), accessibility announcement mechanics (use `a11y`), business lifecycle modeling (use `state-machine-modeling`), or performance optimization (use `performance-engineering`).

jacob-balslev Bundle

Use when choosing or auditing UI interaction patterns and controls: tabs vs pages, dropdown vs combobox, stepper vs wizard, modal vs inline edit, disclosure, command menus, selection, filtering, and gesture alternatives. Do NOT use for accessibility compliance (use `a11y`), task decomposition (use `task-analysis`), feedback-state staging (use `interaction-feedback`), or reusable component API design (use `design-system-architecture`).

jacob-balslev Bundle

The architectural discipline of structuring a UI component library — layering, API surface design, headless/styled split, and state contracts — so component APIs survive reuse across products, themes, and teams.

jacob-balslev Bundle

Use when structuring information for findability: navigation, page hierarchy, docs architecture, sitemap shape, labeling systems, wayfinding, and content grouping. Do NOT use for formal category-governance work (use `taxonomy-design`), responsive page composition (use `layout-composition`), component/token architecture (use `design-system-architecture`), or sentence-level UI text (use `microcopy`).

jacob-balslev Bundle

Use when designing reusable component modules — composition patterns, compound components, slot/children APIs, render props, headless component contracts, and the choice between configuration and composition. Do NOT use for application-level architecture, single-use feature components, or visual styling decisions.

jacob-balslev Bundle

Use when designing or extending an application exception-reporting pipeline: error boundary placement, tracker SDK wrappers, sanitized reporting calls, environment gating, user context without PII leaks, breadcrumbs, and verification that each layer reports correctly. Covers component, route, global, and manual capture surfaces plus central `reportError`/`reportMessage` patterns. Do NOT use for the visual error UX shown to users (use `a11y` and interaction skills), chasing one captured error (use `debugging`), or broad privacy and retention policy (use `owasp-security`).

jacob-balslev Bundle

Use when auditing a route, defining a route contract, reviewing onboarding or setup flows, diagnosing why a page feels confusing, or when the user asks about top tasks, time-to-value, branching, dead ends, or task complexity. Provides goal-driven UX analysis that turns vague critique into explicit goal -> task -> subtask decomposition and a primary / secondary / supporting hierarchy contract for the first viewport. Do NOT use for control-pattern choice (use `interaction-patterns`), visual craft (use `visual-design-foundations`), responsive layout (use `layout-composition`), or accessibility-only QA (use `a11y`).

jacob-balslev Bundle

Use when designing or reviewing React ref usage: the distinction between refs (mutable handle that survives renders without triggering them) and state (reactive value that triggers renders when changed), the `useRef` hook for DOM access and mutable instance values, ref callbacks for fine-grained mount/unmount hooks, `forwardRef` for passing refs through component boundaries (and the React 19 ref-as-prop change that retires it for new code), `useImperativeHandle` for exposing a controlled imperative surface to parent refs, ref forwarding through compound-component primitives (the Radix `Slot` / Headless UI pattern), and the design rule that refs are an escape hatch — for DOM access, integration with non-React DOM libraries, focus management, animation, measurement, and exposing imperative APIs sparingly, never as a substitute for state. Do NOT use for the broader hook discipline — Rules of Hooks, dependency arrays, custom hooks (use hooks-patterns), for the cross-product component-layering question — primitive

jacob-balslev Bundle

Use when reasoning about the pattern where a language model emits, as structured output, a description of UI components or a UI sub-tree that an application then renders for the user: the typed-schema component palette, the structured-output mechanism (JSON Schema, function-calling) that constrains emission to renderable specs, the two render substrates (typed-component-tree vs sandboxed-iframe), the application-side render pipeline that turns the spec into pixels, the bidirectional interaction loop (postMessage/JSON-RPC) by which user actions on the rendered UI flow back into the next turn, the security boundary between model-author and application-renderer, and the difference between this and adjacent patterns (chat with markdown, prebuilt-widget routing, RSC streaming, model-emits-code). Do NOT use for the page-level rendering taxonomy (use rendering-models), the protocol cycle of tool calls (use tool-call-flow), the trust boundary against untrusted content (use prompt-injection-defense), or general compon

jacob-balslev Bundle

Use when designing or reviewing React error boundaries: what an error boundary catches (rendering errors, lifecycle errors, constructor errors) and what it does not (event handler errors, async errors, SSR errors, errors in the boundary itself), why React still requires class components for error boundaries, how to place boundaries by granularity (page / feature / leaf), how error boundaries pair with Suspense, the reset-and-recover pattern (resetKeys, error.reset), the Next.js error.tsx route-segment convention, and how to integrate boundaries with error reporting (Sentry, observability). Covers React 18+ and Next.js App Router. Do NOT use for Suspense boundary placement (use suspense-patterns), for general error-handling discipline (try/catch in async code, validation errors), for backend error contracts (use api-design), or for observability infrastructure (use error-tracking).

jacob-balslev Bundle

Use when reasoning about React Hooks as a discipline: why the Rules of Hooks exist as a call-order invariant, how dependency arrays encode a contract between closure and rerender, when useEffect is the wrong primitive, the distinction between derived state and stored state, when to extract a custom hook, when memoization (useMemo, useCallback, memo) is useful or obsolete, and how React 18/19 semantics (automatic batching, concurrent rendering, Strict Mode effect checks, Effect Events, React Compiler) change the calculus. Do NOT use for general React rendering models (use rendering-models), the client/server boundary (use client-server-boundary), component API architecture (use component-architecture), Suspense boundary design (use suspense-patterns), or application-wide state location (use state-management).

jacob-balslev Bundle

Use when reasoning about how a web UI is produced and delivered: client-side rendering, server-side rendering, static-site generation, incremental static regeneration, React Server Components, streaming SSR, edge rendering, and partial prerendering. Covers the time × place grid (build/request/stream/interaction × server/edge/client), the trade-offs between first-paint latency and time-to-interactive, the relationship between rendering and hydration, and how a route's content profile (dynamic / static / personalized) maps to a model. Do NOT use for organizing the frontend codebase (use frontend-architecture), the serialization frontier between server and client code (use client-server-boundary), the wire protocol itself (use http-semantics), or specific deploy-platform composition patterns (use vercel-composition-patterns).

jacob-balslev Bundle

Use when deciding where state lives, how it propagates, and how it composes: local component state vs lifted/shared state vs application state, server state vs client state, URL as state, persistent state, derived state, and the cross-cutting decision of who owns which piece. Covers state colocation, lifting up, derivation vs duplication, single source of truth, optimistic updates, server-state cache invalidation (React Query/SWR model), URL state for deep-linking, and anti-patterns like prop-drilling, state sprawl, and global-state-by-default. Do NOT use for specific state library choice (Redux vs Zustand — tactical), data fetching mechanics (use api-design or rendering-models), client/server boundary (use client-server-boundary), distributed system state (use replication-patterns), or finite state machines (use state-machine-modeling).

nahisaho Skill

臨床レポート自動生成スキル。検査結果サマリー (SOAP ノート)、バイオマーカー プロファイルレポート、薬理ゲノミクスレポート、臨床試験要約を構造化テンプレート (PDF/LaTeX/HTML) で出力。HL7 FHIR DiagnosticReport 形式にも対応。

eskcti Bundle

Bootstrap do shell web admin Vue 3 com Tailwind CSS v4 — sidebar colapsável, topbar, rodapé, dashboard vazio e rotas de referência. Usar após config-project-vue quando o pedido envolver layout profissional, menu lateral ou shell reutilizável no frontend Vue.

eskcti Bundle

Criar telas (screens) Dioxus com separação UI (component) vs lógica (hook/use case). Usar quando o pedido envolver screen Dioxus, tela mobile Rust, listagem, detalhe, formulário de tela, ou feature Dioxus Mobile.

eskcti Bundle

Criar ou revisar formulários Angular 17+ com Reactive Forms (FormBuilder, Validators), PrimeNG inputs e feedback de erro inline. Usar quando o pedido envolver formulário Angular, ReactiveFormsModule, FormGroup, FormBuilder, inputs PrimeNG (InputText, Dropdown, Calendar), validação de campos ou formulário de cadastro/edição em Angular.

eskcti Bundle

Criar ou revisar páginas/componentes Angular 17+ standalone no padrão do projeto, usando signals, PrimeNG para UI, UseCase (camada de aplicação) para lógica de negócio e lazy loading por feature. Usar quando o pedido envolver componente Angular, página, listagem, detalhe, tabela PrimeNG, ou feature Angular standalone.

eskcti Bundle

Inicializar ou continuar um projeto full-stack com backend NestJS e frontend Angular 17+ (standalone components, signals) com Tailwind CSS, em monorepo com estrutura separada apps/backend + apps/web-angular. Usar quando o pedido envolver bootstrap de projeto Angular, setup NestJS + Angular, ou padronização de estrutura full-stack com Angular.

eskcti Bundle

Criar entidades de domínio Leptos em Rust puro (sem leptos::*), com shared_kernel::Result e validações que acumulam erros. Usar quando o pedido envolver entidade de domínio Leptos, modelo de domínio Rust no frontend ou validação de domínio no crate web-leptos.

eskcti Bundle

Criar entidades de domínio Angular em TypeScript puro (sem Angular/HttpClient), com tipo Result<T, E> e validações que retornam Result em vez de lançar exceções. Usar quando o pedido envolver entidade de domínio Angular, modelo de domínio TypeScript, Result type ou validação de domínio no frontend Angular.

eskcti Bundle

Criar a implementação do repositório Vue com fetch/axios, DTO de API e mapeamento para entidade de domínio, retornando Promise<Result<T>>. Usar quando o pedido envolver repository Vue, fetch wrapper, DTO-to-entity mapping, ou implementação de ICustomerRepository no Vue 3.

eskcti Bundle

Criar casos de uso Leptos em Rust puro (struct + execute async), orquestrando entidades e ports com shared_kernel::Result. Usar quando o pedido envolver use case Leptos, regra de aplicação no frontend Rust ou orquestração domain+repository no crate web-leptos.

eskcti Bundle

Orquestrar a criação de um projeto full-stack completo com backend (NestJS/Spring Boot Kotlin/Spring Boot Java/ASP.NET Core/Axum Rust), frontend (Next.js/Angular/Vue/Leptos SSR com Tailwind CSS) e mobile opcional (Flutter/Android). Integrar OpenSpec para gerenciamento de mudanças ao longo do ciclo. Usar quando o pedido envolver criar um projeto do zero com múltiplas camadas, ou quando o usuário não sabe por onde começar.

eskcti Bundle

Bootstrap do shell web admin Leptos SSR com Tailwind CSS v4 — sidebar colapsável, topbar, rodapé, dashboard vazio e rotas de referência. Usar após config-project-leptos quando o pedido envolver layout profissional, menu lateral ou shell reutilizável no frontend Leptos.

eskcti Bundle

Criar serviços Angular que encapsulam casos de uso (application services) com retorno Promise<Result<T>>. Usar quando o pedido envolver use case Angular, application service, lógica de negócio no frontend Angular, ou orquestração entre repository e entidade em Angular.

eskcti Bundle

Bootstrap do shell web admin Angular 17+ com Tailwind CSS v4 — sidebar colapsável, topbar, rodapé, dashboard vazio e rotas de referência. Usar após config-project-angular quando o pedido envolver layout profissional, menu lateral ou shell reutilizável no frontend Angular.

eskcti Bundle

Criar repositório HTTP Leptos com reqwest, DTO serde e mapeamento para entidades de domínio com Result. Usar quando o pedido envolver repository Leptos, adapter HTTP no frontend Rust ou integração com API Axum no crate web-leptos.