Web & Frontend

lucaszhh Bundle

QA de componentes de @design-system/react con Storybook Test Runner. Valida compilación, a11y automatizado (axe-core WCAG 2.1 AA), paridad visual, variantes y cero tokens hex/px hardcodeados. Usar con "hacé QA del componente", "validá el Button", "corré el test runner".

lucaszhh Bundle

Genera la descripción de PR/MR desde el diff contra develop usando three-dot diff y merge-base. Detecta env vars nuevas (Next.js, LoopBack, Nest, Go, Vite) con alertas críticas, agrupa cambios por capa arquitectónica y escribe a disco. Usar con "generar reporte de PR", "reporte de issue", "describir MR".

lx-wnk Bundle

Generate a Tech Gazette as a self-contained HTML file covering 18+ topic areas relevant to Software Architects and Lead Developers working in Shopware/E-Commerce agencies. Supports daily and weekly editions. Use this skill whenever the user asks to create a tech gazette, generate a tech briefing, write a tech newspaper, or says things like "tech gazette", "Gazette erstellen", "daily tech news", "weekly tech news", "Tech-Briefing", "tägliche Gazette", "wöchentliche Gazette".

lx-wnk Skill

Design low-level component and class structure — classes, interfaces, design patterns, method signatures, aggregates, service contracts, and collaboration within a single module or bounded context. Make sure to use this skill whenever the user asks to design classes, pick a design pattern, define interfaces, model an aggregate, shape a service, or says things like "wie strukturiere ich die klassen", "welches pattern passt", "component design", "class design", "design the service", "model the aggregate". Use this skill for DETAIL DESIGN inside a known module — system-level structure belongs in `architecture-design`.

lx-wnk Skill

Review low-level component and class design — SOLID, cohesion, pattern correctness, interface design, method contracts, aggregate integrity, and domain-model health inside a PR, branch, namespace, or module. Make sure to use this skill whenever the user asks to review class design, check SOLID, audit a component, check if a pattern is used correctly, or says things like "component review", "class review", "prüfe das klassen design", "are these classes clean", "review the service", "solid check". Use this skill for DETAIL REVIEW only — module boundaries and dependency structure belong in `architecture-review`.

lx-wnk Skill

Review system-level architecture of a PR, branch, namespace, or whole project — boundary violations, dependency cycles, layer breaches, ADR compliance, cohesion of modules and bounded contexts. Make sure to use this skill whenever the user asks to review the architecture, audit module boundaries, check for circular dependencies, verify domain structure, or says things like "architektur-review", "prüfe die struktur", "check architecture", "review namespace", "audit boundaries", "are our modules clean". Use this skill for HIGH-LEVEL structural review only — SOLID, class design, and method-level issues belong in `component-review`.

autocss-com Bundle

Modern vanilla CSS is the native, intrinsic superpower driving the AutoCSS Architecture—built in, always active, continuously observing, and instantly reactive. In an air-gapped Separation of Concerns (presentation layer from data layer), declarative-first system, CSS is not simply a styling layer. CSS is the UI runtime. It controls layout, state, themes, transitions, visibility, loading, responsiveness, interaction, and every other form of interface behavior. Each CSS capability is isolated in its own reference file: independent, reusable, composable, and free from JavaScript or any other control. CSS MUST be leveraged to it's maximum potential for writing or reviewing presentation layer UI conditional layout behavior,styles, and/or everything else in the presentation layer aside from API CRUD data transport.

autocss-com Skill

Single-Page-Application rules for projects following the air-gapped, browser-native architecture. Defines the one entry document, radio-driven navigation read by CSS `:has()`, the fetch-once shell, the `oninput` data lifecycle per view change, and same-document content transitions. Use whenever wiring navigation, routing, view switching, deep-linking, or page-to-page behavior. Pairs with the `pwa` skill.

autocss-com Bundle

HTML rules for projects following the air-gapped, semantic-only architecture. Defines the only allowed elements, the only allowed attributes, the only allowed patterns for interactive elements, and the canonical layout shell. Use whenever writing or reviewing markup, defining custom elements, or shaping the DOM.

autocss-com Bundle

JSON rules for projects following the air-gapped, declarative-first architecture. JSON carries data only — no HTML, no CSS, no styling, no presentation hints. The JSON shape drives the UI because CSS reacts to data presence and absence in the DOM. Use whenever shaping API payloads, schemas, or any content data.

autocss-com Bundle

Naming rules for files, custom element tags, skills, functions, and CSS custom properties. Names describe the concern, not the implementation, so they survive refactors. Use whenever creating any new named thing or renaming an existing one.

autocss-com Skill

How to verify AutoCSS work before it ships, in a zero-dependency architecture. Covers the air-gap test, driving the real app in a browser to observe behavior, verifying CSS-only state/visibility, and the accessibility passes. Test tooling is dev-only and never enters the shipped static shell. Use before committing any nontrivial change, or when asked to confirm something works.

autocss-com Skill

The foundational engineering principles every AutoCSS effort obeys, one section per principle. These sit beneath the concern skills (html/css/javascript/json/…) and decide trade-offs when a task could be solved more than one way. Use when choosing an approach, justifying a design, resolving "which tool", or reviewing whether a change earns its place.

autocss-com Skill

Entry point for projects following the air-gapped, browser-native, declarative-first architecture. Defines the layer separation (html, css, javascript, json) and routes to the concern skill for any task. Use when starting any work, when in doubt which concern owns a task, or when about to mix concerns.

autocss-com Skill

D7460N Architecture — zero-dependency, CSS-only, JAMstack-based, browser-native starter template. Use when modifying HTML, CSS, or JS files in this project. Enforces CSS-driven UI state, semantic HTML, no frameworks, no dependencies, and strict separation of concerns between presentation and data layers.

autocss-com Bundle

Specialized knowledge for writing modern high-quality CSS. Trigger this skill when starting a new CSS project/file, when the user asks about new CSS features (e.g. Masonry, View Transitions, Container Queries, Scroll-driven animations), or requests refactoring of legacy styles to modern standards.

bongsuchoi Bundle

Codex-first fallback for reading blocked or degraded public web content. Use when normal web access returns 402/403, WAF or bot challenges, empty or JavaScript-only HTML, or when public content from X/Twitter, Reddit, YouTube, GitHub, Mastodon, Medium, Substack, Stack Overflow, Threads, Naver, Coupang, LinkedIn, and similar platforms needs an alternate public access path. Uses public endpoints, feeds, yt-dlp, Jina Reader, URL transforms, guarded transport, and explicit browser handoff. Do not use for ordinary web searches or permission-gated content.

bongsuchoi Bundle

Guide broad product UI direction, redesign, design-system extraction and UX structure for web or mobile interfaces. Use when a task changes visual language, layout grammar, component patterns or an end-to-end product flow; do not use for a small style, copy or single-component edit.

bongsuchoi Bundle

Navigate and interact with real browser pages, fill forms, inspect accessibility snapshots, capture screenshots or traces, and reproduce browser state. Use for browser interaction and evidence capture; final visual judgment belongs to cx-visual-qa.

bongsuchoi Bundle

Analyze unfamiliar codebases and agent harnesses into an evidence-backed architecture knowledge graph with an optional interactive local HTML dashboard. Use for repository onboarding or handoff, studying a new codebase, tracing harness logic and architecture, mapping components and dependencies, refreshing an existing graph, asking graph-backed questions, explaining a file or function, assessing change impact, building a learning tour, extracting business domains, or opening the interactive visualization. Do not use for a narrow source lookup, runtime root-cause diagnosis, or formal acceptance; use ordinary repository search, cx-debugging, or cx-acceptance-qa instead.

impertio-studio Bundle

Use when starting a PDF.js project, understanding PDF.js internals, or reasoning about the rendering pipeline. Prevents the common mistake of misunderstanding the three-layer model (Core/Display/Viewer) and worker thread architecture. Covers component hierarchy, pdfjs-dist 5.x package structure, and rendering pipeline overview. Keywords: PDF.js, pdfjs-dist, architecture, worker, PDFDocumentProxy, PDFPageProxy, layers, how PDF.js works, PDF rendering pipeline, what is pdfjs-dist.

impertio-studio Bundle

Use when integrating pdfjs-dist with webpack, Vite, Rollup, Next.js, or Nuxt.js build systems. Prevents worker loading failures caused by incorrect bundler configuration for the pdf.worker.mjs file. Covers webpack worker-loader/asset module config, Vite import.meta.url pattern, Rollup config, CMap/font file copying, and tree-shaking considerations. Keywords: webpack, vite, rollup, Next.js, bundler, worker-loader, import.meta.url, PDF.js with Vite, PDF.js with webpack, worker not loading, bundler configuration, Nuxt.js.

impertio-studio Bundle

Use when generating a complete PDF.js project from scratch, scaffolding a new PDF viewer application, or setting up the full rendering pipeline with all layers. Prevents incomplete project setup by ensuring worker, canvas, text layer, and annotation layer are all properly configured. Covers bundler-specific worker config, HTML/CSS templates, TypeScript setup, package.json with correct pdfjs-dist version, and full rendering pipeline. Keywords: scaffold, project setup, boilerplate, PDF viewer template, TypeScript, pdfjs-dist, new PDF viewer, create PDF app, start PDF.js project, build PDF reader.

kin9zeus Bundle

Operate as a senior engineering organization (principal engineer, senior fullstack, senior DBA, senior DevOps/SRE, security, QA, accessibility and privacy leads) for any non-trivial software work. Use when the user asks to audit, review, assess, harden, refactor, architect, scaffold, plan, build or ship a project or feature; when they say "is this production ready", "review my project", "build me a", "start a new project", "make this professional", "senior level", "best practices", "what am I missing", "enterprise grade", "at scale", "code smells", "technical debt", "tech stack" or "architecture"; or whenever a change touches auth, payments, personal data, migrations, deploys or public-facing pages. Routes to the specialised skills in this suite and enforces the non-negotiable quality bar. By Devleck.

kin9zeus Bundle

The go/no-go gate before shipping — a structured launch checklist across security, data, legal, operations, performance, accessibility and rollback, producing an explicit ship or do-not-ship decision with named blockers. Use when the user says "ready to launch", "go live", "ship it", "pre-launch", "launch checklist", "release checklist", "production ready", "deploy to production", "v1", "MVP launch", "are we ready" or "what's left before we ship"; and after any project audit, to convert findings into a gate. By Devleck.

kin9zeus Bundle

Audit and build interfaces to WCAG 2.2 AA — keyboard operability, focus management, semantic structure and landmarks, accessible names, colour contrast, forms and error handling, ARIA patterns, reduced motion, zoom and reflow, and testing with real assistive technology. Use when the user says "accessibility", "a11y", "WCAG", "screen reader", "keyboard navigation", "contrast", "ARIA", "focus", "alt text", "accessible", "ADA", "Section 508", "EAA" or "European Accessibility Act"; when building or reviewing any UI component, form, modal, menu or data table; and as a mandatory pass in any audit of a project with a user interface. By Devleck.

kromatic-innovation Skill

RED-phase role for writing failing tests before implementation — supports both frontend (React/Next.js) and backend (Python/pytest).

kromatic-innovation Skill

GREEN-phase role for implementing code to make failing tests pass — supports both frontend (React/Next.js) and backend (Python/FastAPI).

microlinkhq Skill

Retrieve normalized HTML from URLs with fetch or headless prerender for JS pages, absolute URL rewriting, and metadata extraction pipelines.

microlinkhq Skill

Turn URLs into product results with microlink.io — metadata, markdown/html/text, screenshots, PDFs, logos, embeds, video/audio, page collections, Google search, and remote JS functions. Use when the user mentions Microlink, microlink.io, taking screenshots, generating PDFs, extracting page content, scraping without browser infra, or the microlink CLI/MCP.

microlinkhq Skill

Automate browserless/Puppeteer headless Chrome for screenshots, PDFs, HTML/text extraction, status checks, Lighthouse audits, and browser pipelines.

microlinkhq Skill

Extract metadata from HTML with metascraper rules for link previews, Open Graph, Twitter Cards, JSON-LD, titles, images, authors, and custom parsers.

microsoft Skill

Guide for the visual style, structure, and shared building blocks used by Semantic Link Labs interactive UI tools (HTML widgets and anywidget-based widgets). Use this when adding a new interactive UI, modifying an existing one, or adding shared visual components.

mrhinkle Bundle

Runs a unified pre-launch or post-update quality-assurance pass on a website — the holistic "does this actually work?" gate. Walks pages, forms, navigation, third-party integrations, cross-browser and mobile behavior, JavaScript console health, accessibility basics, HTTPS/security, and a performance smoke test. Produces a QA report with issues rated by severity, reproduction steps, and a launch recommendation; supports regression testing after fixes. Stack-agnostic. Trigger on "QA my site," "test my site," "does everything work," "smoke test," "test before launch," "regression test," "check all pages," "test my forms," "check mobile," "cross-browser test," "broken links," or "is my site ready to launch."

mrhinkle Bundle

Write and run automated browser tests for a web app using Playwright — smoke tests, critical user journeys (sign-up, login, contact/checkout forms), navigation, and console/network-error checks — then report pass/fail with screenshots and repro steps. Scaffolds Playwright if the project doesn't have it, uses resilient role/text selectors, and can wire tests into CI. Complements a manual QA pass with real automation. Works with any stack the browser can load (React, Next.js, Vue, Svelte, plain HTML, WordPress). Trigger on "write tests for my site," "add Playwright tests," "test this user flow," "end-to-end tests," "e2e," "browser tests," "test my signup/checkout," or "set up automated testing."

mrhinkle Bundle

Audits and fixes web page load performance. Analyzes images, CSS, JavaScript, fonts, and third-party assets, then produces a prioritized before/after report with concrete optimization steps and copy-paste code. Targets Core Web Vitals (LCP, INP, CLS) and Lighthouse scores. Stack-agnostic — plain HTML, WordPress, React, Next.js, Vite, Astro, or a hosted builder; uses free tools only (Lighthouse, ImageMagick, cwebp/AVIF, PurgeCSS, bundle analyzers). Trigger on "my site is slow," "speed up my site," "improve page load," "optimize performance," "Core Web Vitals," "LCP/INP/CLS," "Lighthouse score," "reduce bundle size," "optimize images," "why is my site slow," or "performance audit."