Web & Frontend

learningmatter-mit Bundle

Predict synthetic accessibility and retrosynthetic pathways for novel molecules using the IBM RXN API.

alpayc Skill

Frontend and cross-repo defect diagnosis — observe it in the browser, make it repeatable, find the first wrong value, lock the fix behind a regression test. Use it for a bug report, something throwing, a regression, a console error, or something slow.

cristianomafrajunior Skill

OWL component and website-theme conventions across Odoo 14-19, including the OWL 1→2→3 migration shape and SCSS variable conventions. Use when asked to build/fix a JS widget, an OWL component, or a website theme/snippet.

learningmatter-mit Bundle

Calculate and plot multi-component temperature-composition phase diagrams from Thermodynamic Database (.tdb) files using CALPHAD methods.

alpayc Skill

Documents how a system is put together, as an arc42 document under docs/architecture/ — generates the chapters derivable from code, marks the ones that are not, drift-checks the generated ones. Run it when asked what talks to what, where a component sits, or how the system is deployed; when the architecture documentation is missing, stale or being set up; or as a CI check.

alpayc Skill

Finds the holes in a spec before code exists — works a fixed set of frontend dimensions for the unstated state, the missing permission case, the timezone bug, the thing that breaks at 10,000 rows. Run it on a spec draft before implementation, on an architecture decision you are about to commit to, or when a plan needs holes found rather than agreement. Findings go back into the spec.

alpayc Skill

Establishes and enforces frontend performance budgets — bundle size per app, Core Web Vitals, render cost — measured identically every time so a regression is visible the day it lands. Use it when a bundle grew, a page feels slow, or to set up the gate.

emanuelegreco29 Bundle

General testing strategy and quality gates - testing pyramid, TDD workflow, mocking and test data, and CI quality gates. Use whenever following TDD, deciding what test level to use, or deciding what should block a merge (for frontend-specific test scope, see codexpiator-frontend/frontend-testing.md).

alpayc Skill

Extracts the codebase's own convention before building something new — finds the three closest existing examples, reads them fully, derives what they agree on. Run it before creating any component, service, store slice, test, route or form.

alpayc Skill

Test-first discipline for UI work — the seam comes from the spec, the failing test comes before the code, the assertion describes what the user experiences. Use it when a step's behaviour is specifiable before it is built.

alpayc Skill

Follows one feature end to end across both repos — UI event through component, state, HTTP, backend endpoint, service, persistence — naming every file and line. Use it to find where a change must land, where data comes from, or where a value gets lost between frontend and backend.

alpayc Skill

Behaviour-preserving change at scale — establish the safety net, move in small green committed steps, prove nothing changed. Use it for renames, extractions, moving code between projects, replacing a pattern across many files, or splitting a component.

grzmol Bundle

Covers building Lightning Web Components on the Salesforce platform - bundle anatomy and js-meta.xml targets/targetConfigs, the reactivity model, @api/@wire/@track decorators, Lightning Data Service and imperative Apex, CustomEvent and Lightning Message Service communication, lifecycle hooks, template directives (lwc:if, for:each, iterator, lwc:ref, lwc:dom="manual", slots), SLDS styling hooks, shadow vs light DOM, NavigationMixin, toasts, labels and i18n, static resources and third-party JS, Lightning Web Security constraints, and performance/accessibility rules. Use this skill whenever work touches force-app/**/lwc/**, a *.js-meta.xml file, a wire adapter such as getRecord or graphql, an @AuraEnabled(cacheable=true) method consumed from JavaScript, refreshApex, a LightningMessageChannel, or when a component must be exposed to a Lightning App Page, Record Page, Flow screen, quick action, or Experience Cloud site.

grzmol Bundle

Covers unit testing Lightning Web Components with @salesforce/sfdx-lwc-jest - jest.config.js setup and the sfdx-lwc-jest preset, createElement/appendChild test anatomy, DOM cleanup, flushing async rerenders, querying shadow and light DOM, asserting dispatched CustomEvents, mocking Apex methods and @salesforce scoped imports with jest.mock, driving wire adapters with createApexTestWireAdapter/createLdsTestWireAdapter/createTestWireAdapter, stubbing lightning/navigation, lightning/messageService, toasts and base components, coverage configuration against the jestCoverageMin gate, and debugging failing suites. Use this skill whenever a __tests__ directory under force-app/**/lwc/** is created or changed, when vf-check jest fails, when a component test needs wire or Apex data, or when deciding what an LWC test should assert.

grzmol Bundle

Configure Salesforce Setup from a session when the Metadata API has no route for it - decide deploy vs scratch-org definition vs browser, gate the decision on the org's own describeMetadata, hand a headless browser one single-use authenticated session without leaking a frontdoor URL, drive Setup from the accessibility tree, and prove the change with SetupAuditTrail. Use for org preferences and feature switches with no metadata type, never for configuration a deploy can carry.

grzmol Bundle

Covers the Salesforce development loop that runs before any deployment - Live Preview (formerly Local Dev) via sf lightning dev app, sf lightning dev component and sf lightning dev site, what hot-reloads versus what needs a redeploy and server restart, which checks genuinely run offline (prettier, ESLint, Code Analyzer, sfdx-lwc-jest) versus which need an org (Apex compilation and tests, Flow, permissions, SOQL), source-tracking hygiene with sf project deploy preview, --dry-run and sf project retrieve start, watch loops, anonymous Apex probes, VS Code and devcontainer setup, and the exact composition of the vf-check local gate. Use this skill when starting work on a component before deploying, when deciding whether a change can be verified without an org, when the preview server does not pick up a change, when source tracking reports conflicts, or when a contributor asks how to iterate quickly on LWC or Apex.

grzmol Bundle

Second-generation packaging (2GP) and unlocked packages as a release mechanism - deciding between org-based deployment, unlocked packages and managed packages, the sfdx-project.json packaging attributes (package, versionName, versionNumber with NEXT and LATEST, ancestorVersion, dependencies, seedMetadata, unpackagedMetadata, apexTestAccess), the sf package command surface from create through version create, promote, install and uninstall, installation keys, upgrade types and data loss on component removal, org-dependent unlocked packages, dependency graphs across repositories, and why StandardValueSet needs seedMetadata. Use when splitting a monorepo into packages, publishing or installing a package version, wiring package dependencies, or deciding whether packaging is the right release model at all.

alpayc Skill

Keeps the frontend's view of the backend API true — locates the contract, regenerates the typed client, reports drift. Run it before touching an endpoint, when a request fails on shape, or when the backend moved ahead. Answers what an endpoint actually returns.

breroz Bundle

Perform application security reviews for web apps, APIs, backend services, frontend code, infrastructure/configuration, authentication/authorization flows, dependency changes, pull requests, and deployed application behavior. Use when Codex is asked to audit, assess, threat model, review for vulnerabilities, check secrets, verify access control, harden an app, or produce security findings with practical remediation.

stas2-git Bundle

Use when designing or building a human-in-the-loop frontend for an ADK/Agent Runtime app, including pending approval queues, event correlation, session resume, function responses, manager dashboards, auth, audit, and Cloud Run/Pub/Sub wiring.

breroz Bundle

Install Google Analytics 4 (GA4) into a website's codebase — the base gtag tag plus event tracking — wiring it into the real framework so pageviews fire on every route and meaningful interactions are tracked. Use this whenever someone wants to add, install, set up, wire up, or instrument Google Analytics / GA4 / gtag / a measurement ID (G-XXXXXXXXXX) on their site, or asks to "track events", "add analytics", "set up conversion tracking", or "get analytics working before launch" — even if they don't name GA4 specifically and even if they just hand you a measurement ID and a repo. Auto-detects the stack (static HTML, React SPA, Next.js, and similar) and writes the install in the idiomatic way for that stack. This skill writes code into the project; it is not an audit-only report.

alanpai Skill

Auto-start a local development server before sharing a localhost URL with the user. Use this skill PROACTIVELY whenever (1) the user asks to test, preview, open, or access a local frontend / web app / website ("幫我開啟本地端", "本地測試", "我要看", "give me the local link", "open it locally", "let me try it"), OR (2) you are about to give the user a `http://localhost:...` link. Never hand out a localhost URL without first verifying the server is actually running. Covers static sites (vanilla HTML/JS, no build), Vite, Next.js, CRA, Python static sites, and similar.

samber Bundle

Design how an API platform communicates status and incidents to external consumers - status-page modeling (the four-stage incident lifecycle, degraded/partial/major component semantics, component granularity), monitoring-driven status instead of a hand-flipped green light, pull and push channels, incident-update cadence and templates, public postmortems for a developer audience, public SLA/SLO reporting, and maintenance-window notices. Use whenever the user mentions a status page, Statuspage, incident updates, uptime or SLA reporting, postmortems, or scheduled maintenance - even if they never say "status communication". Do NOT use for deprecation and breaking-change notices - use samber/developer-platform-skills@api-versioning-policy instead.

macfarlanem-cloud Skill

Use whenever the user is building, rebuilding, or polishing a lecture or content page in Canvas (with Claude in Chrome, the Canvas rich content editor, or raw HTML). Trigger on requests to add accordions, dropdowns, expanders, hover or mouse-over definitions, a Key Terms glossary, images with alt text, or to bring a page "up to standard." Produces modern, accessible, warmly written Canvas pages with DesignPLUS structure, openly licensed images hosted in course Files, and bolded key terms with definitions. Do not use for quizzes, discussions, or assignments unless the user asks for page-style formatting inside them.

seryozh Bundle

Audit and rebuild a web layout from the live rendered page instead of from a screenshot. Measures real geometry, type, spacing, colour contrast, tap targets and reading load out of the browser, computes what is usually left to taste (visual weight per band, first-glance saliency, alignment lanes, spacing-scale conformance), writes acceptance criteria, builds the proposed version as real HTML in the site's own cascade, then re-measures and returns PASS or FAIL per criterion. Use when someone asks what is wrong with a page or section, why a layout feels cluttered, heavy, empty or confusing, where the eye goes, how a section should be rearranged, or when an agent is about to rebuild a section and needs a spec it can be held to. Works from a screenshot alone in a reduced mode, and says so.

macfarlanem-cloud Skill

Use whenever the user asks for help designing courses, modules, lessons, assignments, rubrics, discussion prompts, assessments, syllabi, learning outcomes, or any instructional materials for learners of any age across any modality (online, hybrid, in-person, self-paced, synchronous, asynchronous). Applies a humanizing pedagogy/andragogy grounded in learner identity, agency, and belonging, and operationalizes equity and design frameworks including Universal Design for Learning, transparent assignment design, culturally responsive practice, backward design, and WCAG accessibility standards. Do not use for general writing unrelated to instructional design.

jawkx Bundle

Use Argent tools for iOS, Android, tvOS, Android TV, React Native, don't use it for web application. Covers device setup and interaction, UI testing, screenshots and visual diffs, reusable flows, Metro/CDP debugging, React and native profiling, performance optimization, and Argent Lens design variants. Use whenever a task involves Argent, a simulator/emulator/TV device, app UI automation or QA, React Native runtime debugging or profiling, screenshot comparison, flow recording, or Lens proposals.

cnfjlhj Bundle

Use when turning an academic paper PDF/arXiv/OpenReview page/local LaTeX source into a single-file Chinese HTML deep-reading page, especially when the user wants a Cheat-Sheet style explanation, KaTeX formulas, figure/table evidence, validation, or a publishable research page.

samber Bundle

Writes or reviews a shooting-ready script for a technical video or screencast - a two-column visual/narration beat sheet with a 30-second hook, code-on-screen pacing, segment chapters, a runtime budget, integrated description for accessibility, and a pre-decided cut list. Use whenever someone mentions a screencast script, a demo or walkthrough video, a video tutorial script, narrating a code walkthrough, turning a blog post, changelog, docs page or existing demo into a video, or asks why viewers drop off in the first minute - even if they only say they are recording something. Not a live stage demo - use samber/developer-relations-skills@developer-live-demo-design. Not video editing or podcast guesting.

luisotavio756 Bundle

Write clear, maintainable unit tests using the AAA pattern, behavior-focused names, and minimal mocking. Use when creating or updating tests, writing *.test.ts(x), mocking dependencies, or when the user asks to test a component, hook, store, service, or utility.

luisotavio756 Skill

Act as a senior product designer and UI engineer.

luisotavio756 Bundle

Organize Zustand stores with separated actions, selectors, typed hooks, and optional staging stores. Use when creating or modifying Zustand stores, store actions, selectors, edit/cancel flows, or when the user mentions zustand, store structure, or useXxxActions.

luisotavio756 Skill

Rules

port-labs Bundle

Build and update Port dashboard pages: widgets (table, number chart, pie chart, bar chart, multi-line chart, markdown, iframe, links, action card, action-runs table, entity details, AI agent), the 12-column row layout, sidebar placement, and private-page rules. Covers dataset filter syntax so a widget shows the entities you expect instead of an empty or wrong result. Use when asked to "build a Port dashboard", "add a widget to a dashboard page", "create a number chart / pie chart / table widget in Port", "why is my Port widget empty", "make this dashboard page private", or "where should this dashboard go in the sidebar". For building a custom plugin widget (your own React iframe), use the nested `port-dashboard-plugins` skill instead.

port-labs Bundle

Scaffold, implement, and audit Port custom plugin widgets: self-contained React/TypeScript iframe apps built on @port-labs/plugins-sdk and uploaded with @port-labs/port-plugins-cli. Covers the postMessage host bridge (PLUGIN_DATA, PORT_TOKEN), the React-hooks-before-early-return rule that causes blank iframes, upload-params.json design (blueprint params vs runtime API calls), theming, webpack/CSP upload safety for chart libraries, and versioning. Use when asked to "build a custom Port widget", "create a Port plugin", "why is my Port plugin blank in the iframe", "add a params.json blueprint param to a Port plugin", or "upload a Port plugin with port-plugins-cli". For Port's built-in dashboard widgets (table, number chart, pie chart, and so on, no custom code), use the parent `port-dashboards` skill instead.

kentico Bundle

Validates a live Xperience by Kentico site against static HTML designs — a bundled Playwright script compares each design page with the rendered live page (content, structure, computed styles), and each difference is classified as a content, serving, or styling issue with the root cause and fix location identified. Use when asked to validate, QA, or compare pages against a design/mockup/static HTML, or why a page differs from the design; also proactively after changing a page, template, widget, view component, or stylesheet when a design for it exists.