Web & Frontend

coco-research Skill

Generate complete test coverage for any file, component, or module. Covers unit tests, integration tests, edge cases, error handling, and mocking — adapted to whatever testing framework the project uses.

coco-research Bundle

Generate architecture documentation using C4 model Mermaid diagrams. Use when asked to create architecture diagrams, document system architecture, visualize software structure, or generate context/container/component/deployment diagrams.

coco-research Bundle

Build ChatGPT apps with MCP servers on Cloudflare Workers. Extend ChatGPT with custom tools and interactive widgets (HTML/JS UI). Use when: developing ChatGPT extensions, implementing MCP servers, or troubleshooting CORS, widget 404s, MIME types, ASSETS binding errors, Next.js integration issues, or edge platform limitations.

coco-research Bundle

Generate self-contained HTML visual explanations for systems, code changes, plans, data, and technical concepts. Use for diagrams, architecture overviews, diff or plan reviews, project recaps, comparison tables, slide decks, and other visual explanations.

coco-research Skill

Post-implementation verification system that catches AI-introduced bugs. Covers 7 categories — TDZ errors, import mismatches, reference integrity, dead code, React state/effects, mock isolation, and CSS integrity. Run after every code change, after writing tests, or before marking a task complete. Triggers on "verify", "check code quality", "run verification", "audit code", "quality gate", "pre-commit check".

coco-research Skill

Tailwind CSS v4 principles. CSS-first configuration, container queries, modern patterns, design token architecture. Use when building with Tailwind v4 or migrating from v3.

coco-research Skill

Anti-slop frontend skill for landing pages, portfolios, and redesigns. The agent reads the brief, infers the right design direction, and ships interfaces that do not look templated. Real design systems when applicable, audit-first on redesigns, strict pre-flight check.

coco-research Skill

Generate UI design contract (UI-SPEC.md) for frontend phases

coco-research Skill

Retroactive 6-pillar visual audit of implemented frontend code

coco-research Skill

Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.

peterbamuhigire Bundle

Use when specifying testable game software requirements for player experience, gameplay state, platforms, multiplayer, saves, content, performance, accessibility, telemetry, security, builds, release, or live operations.

eugenelim Bundle

Create, revise, retrofit, audit, or verify product documentation — pack READMEs, journeys, tutorials, how-to guides, reference pages, and explanations. Use when asked to write, improve, restructure, audit, or verify user-facing documentation, fix a pack README, create a guide for a feature, update a journey page, or check whether docs match shipped behavior. Infers the mode from the request. Do NOT use for feature specifications (use new-spec), cross-cutting proposals (use new-rfc), decisions (use new-adr), product or market strategy, frontend implementation alone, internal maintainer runbooks without user-facing concern, or arbitrary prose editing with no documentation purpose.

eugenelim Bundle

Render a Markdown file as a self-contained, offline HTML proof artifact styled for human review. Use when the user asks to "render this for review", "proof this draft", "give me a proof of this document", "show me this markdown rendered", or "make this readable for a reviewer". Outputs a single HTML file that opens in any browser with no server or network access at view time. Not for slides, presentations, or publication — use markdown-to-html for that. The rendered output uses a muted stone/slate palette deliberately distinct from the publication look.

eugenelim Bundle

Convert Outlook .msg and MIME .eml email files to Markdown with a versioned output contract, preserving headers (From, To, CC, BCC, Date, Importance), the body (HTML reduced to Markdown, or plain text), and an attachments table. Use when the user wants to convert, read, or process a .msg or .eml email into Markdown, or extract its attachments.

eugenelim Bundle

Convert documents and images to Markdown for AI context layers. Documents (PDF, DOCX, XLSX, PPTX, HTML, EPUB, CSV/TSV, OpenDocument, .eml) go through `scripts/convert.py`, which extracts at a no-ML Tier-0 floor (pure-Python / stdlib parsers) and falls through to Docling (Tier 2) only for .xls and images; images go through a two-pass sliding-window vision pipeline whose tiling and reconciliation are deterministic (`scripts/split_image.py` and `scripts/reconcile.py`). Every output carries a versioned frontmatter contract (provenance + a quality/confidence signal). The agent's job is the per-tile vision read; tile dedup and ordering are handled by the script.

eugenelim Bundle

Convert a Markdown file to a self-contained, styled HTML page (sticky header, sidebar nav, syntax-highlighted code, callout boxes, Mermaid diagrams, print-ready). Use when the user asks to render, convert, or export a `.md` file as a shareable HTML document -- not for slides, presentations, or pitch decks. Rendering is deterministic via `marked` + `highlight.js`; the agent only invokes the script.

eugenelim Bundle

Use when an approved customer journey needs to become screens, transitions, failure paths, and navigation routes. Produces a complete screen sequence plus one self-contained brief per screen and a whole-flow walk-through. Use `journey-mapping` to understand the journey first, `interaction-design` for behavior within one screen, and `service-blueprint` for backing services. Adoption strategy belongs upstream; appetite and scope belong to `frame-intent`; implementing routes and screens belongs to `frontend-engineering`. Triggers on "turn this account-recovery journey into screens and transitions", "map the error paths across our checkout screens", "create a screen flow and brief for every onboarding screen".

eugenelim Bundle

Orient skill — read the current surface's evidence manifest, known exceptions, and gate history to return a surface-state summary against the frontend engineering quality floor. Triggers on "what is the frontend quality status of this surface", "show me the latest gate history and known exceptions", "what should we fix before changing this existing page".

eugenelim Bundle

Use when someone asks to critique an existing rendered screen, flow, or mockup for usability, quality-floor, clarity, and aesthetic-fit problems. Produces a severity-rated findings list grounded in the actual artifact. Use `creative-direction` to name a new visual direction, `information-architecture` to design hierarchy, and `design-system` to derive tokens. Reviewing product strategy or choosing a bet is upstream strategy work; framing the work belongs to `frame-intent`; reviewing code defects or implementation quality belongs to frontend engineering. Triggers on "review this checkout flow for usability problems", "critique this landing page mockup against our design principles", "what's wrong with this rendered dashboard".

eugenelim Bundle

Use when an approved aesthetic direction exists and someone asks how to name and organize semantic tokens, spacing, type, or color scales. Produces a token taxonomy and rationale; it does not implement token values. Use `creative-direction` to establish the vibe, `information-architecture` for page hierarchy, and `design-review` to evaluate an existing surface. Product differentiation belongs to product strategy; framing a design-system initiative belongs to `frame-intent`; implementing tokens or components belongs to `frontend-engineering`. Triggers on "derive a semantic token taxonomy from this aesthetic direction", "organize our spacing, type, and color scales by role", "design the token system without choosing implementation values".

eugenelim Bundle

Use when someone asks what a surface should communicate, to whom, in what form, and in what order before wireframes or final copy. Produces a content brief for acquisition, product, or reference surfaces. It owns message and narrative structure; `tone-of-voice` owns the brand register, `copy-direction` owns acquisition-surface copy goals, and `ux-writing` owns product UI strings. Organization-level content strategy belongs to `define-content-strategy`; feature framing belongs to `frame-intent`; page or content-system implementation belongs to `frontend-engineering`. Triggers on "create a content brief for our onboarding flow", "decide what this pricing page needs to say and in what order", "shape the message hierarchy before we wireframe the help page".

eugenelim Bundle

Use when a team asks what an end user goes through across an experience, from one meaningful outcome to the next. Produces a customer journey map of stages, actions, touchpoints, emotions, pains, and opportunities, adjusted for the relevant platform. Use `service-blueprint` for backing services, `user-flow` to turn the journey into screens, and `process-mapping` for internal operations. Adoption strategy belongs to product strategy; selecting and scoping a bet belongs to product-engineering shaping; implementing journey screens belongs to `frontend-engineering`. Triggers on "map the customer journey from trial signup to first value", "show what a new admin goes through when setting up a workspace", "map the pains and opportunities in our returns experience".

eugenelim Bundle

Use when someone asks how a productivity, collaboration, or agentic workspace should support sustained professional work across sessions. Produces a workspace-surface specification covering context persistence, collaboration state, ambient attention, interruptions, and session arcs. Use `analytical-design` for dashboards and monitoring views and `marketplace-design` for exchange surfaces. Product strategy is upstream; choosing the appetite and scope belongs to product engineering; implementing the workspace or writing its UI strings belongs to frontend engineering and `ux-writing`. Triggers on "design the session flow for our collaborative editor", "how should this agent workspace preserve context between sessions", "structure interruptions and handoffs in our team workspace".

eugenelim Bundle

Use when someone asks where the current experience-design thread stands, which design artifacts exist, what is missing, or which design skill comes next. Reads the configured design output and returns a read-only orientation; it never writes files or performs the missing design work. Product or portfolio status belongs to product strategy, prioritizing and shaping the next feature belongs to product engineering, and implementation or build status belongs to frontend engineering. Triggers on "where are we with the design", "what experience artifacts do we have", "what's next in the design".

eugenelim Bundle

Use when someone asks what people, services, and systems support each step of an existing customer journey. Produces a service blueprint across frontstage, line of visibility, backstage, and support. Use `journey-mapping` to discover the customer path first, `user-flow` for screen transitions, and `process-mapping` for an internal operation without the customer lens. Service strategy belongs upstream; framing the initiative belongs to `frame-intent`; implementing service calls or frontend behavior belongs to engineering. Triggers on "blueprint the services behind our account-opening journey", "map what happens backstage at each checkout step", "connect this customer journey to the teams and systems that support it".

eugenelim Bundle

Measure, diagnose, and remediate Core Web Vitals and asset budget violations using structured profiling, causality analysis, and repeatable remediation patterns. Triggers on "diagnose why this route fails LCP", "find the cause of our INP regression", "bring this page back under its asset budget".

eugenelim Bundle

Use when someone asks how one screen or component should respond to actions, validate input, transition, recover, or feel in use. Produces behavioral and state specifications for the interaction. Use `information-architecture` for hierarchy, `user-flow` for cross-screen routes, and `creative-direction` for visual mood; `ux-writing` owns the strings shown in those states. Product strategy is upstream; framing and scoping the feature belongs to `frame-intent`; implementing the state machine, motion, or component code belongs to `frontend-engineering`. Triggers on "design how this search component validates, loads, and recovers", "map the state transitions inside this checkout form", "spec the feedback and motion for this async button".

eugenelim Bundle

Deep accessibility engineering beyond automated tooling — focus management architecture, ARIA role correctness under dynamic mutation, live-region discipline, keyboard contract specification, and manual WCAG 2.2 AA verification for the two criteria automated tools miss. Triggers on "audit this surface for accessibility beyond axe", "fix the focus management in this modal flow", "define the keyboard and screen-reader contract for this data grid", "verify WCAG 2.2 AA manually".

eugenelim Bundle

Organize CSS at scale using cascade layers, scoping strategies, and specificity budgets — preventing specificity wars, enabling safe deletion, and making CSS that other engineers can reason about. Triggers on "design the CSS architecture for this new codebase", "fix the specificity wars in our stylesheet", "refactor our cascade so rules can be deleted safely".

eugenelim Bundle

Use at business-unit scale to stand up and keep current a value-stream meta-repo — a coordinating repo with no app code that holds the cross-component artifacts a polyrepo has nowhere else to put (the federated Backstage catalog, the shared-contract authority, the C4/bounded-context architecture, and the cross-component delivery rollup). Triggers on "set up a value-stream meta-repo", "coordinate across component repos", "stand up the cross-component catalog", "where does the shared contract live", "is this feature delivered across all the repos". Reads the per-component slices that decompose-intent produces and rolls up their delivery. Do NOT use at app scale (use decompose-intent — the leaf is one repo's brief) or to author an intent (use frame-intent).

eugenelim Bundle

Design a UI component's public interface — props/slots/events, controlled vs. uncontrolled ownership, composition patterns, lifecycle contract, and usage documentation — before writing any implementation. Triggers on "design the public contract for a shared date picker", "define the props, events, and slots before we build this component", "review this shared component's API before we publish it".

eugenelim Bundle

Select and implement the correct rendering model (CSR/SSR/SSG/ISR/RSC) for each route based on data-access patterns, performance targets, and personalization requirements. Triggers on "choose the rendering model for each route in this product", "should this personalized route use SSR or CSR", "audit our docs routes for caching and hydration problems".

eugenelim Bundle

Design and govern a three-tier CSS custom property token system (primitive → semantic → component), including semantic alias layers, light/dark theming, and DTCG-compatible source generation. Triggers on "design a three-tier token system for our web app", "audit our CSS tokens for hardcoded value drift", "add a semantic dark-theme alias layer", "export our tokens in DTCG format".

eugenelim Bundle

Load when a task's primary output is HTML, CSS, or JS. Provides design pre-flight, codified craft rules, GATES verification commands, and an evidence manifest for that surface. Four modes — create (new surface), retrofit (improving existing), audit (review only), verify (run gates and manifest). Triggers on "build this dashboard in HTML, CSS, and JavaScript", "retrofit this existing landing page without breaking its states", "audit this web surface against the frontend quality floor", "verify this completed component and produce its evidence manifest".

eugenelim Bundle

Use when someone asks what goes where on a screen or flow, in what order, and how users stay oriented. Produces an information-architecture and layout-reasoning document covering hierarchy, reading flow, progressive disclosure, navigation, and wayfinding. Use `creative-direction` for visual mood, `interaction-design` for within-screen behavior, `user-flow` for screen sequence, and `design-review` for critique. Product direction belongs to product strategy; scoping the feature belongs to `frame-intent`; writing markup and styles belongs to `frontend-engineering`. Triggers on "decide what goes where on this settings screen", "design the hierarchy and wayfinding for this flow", "organize this account settings content around the user's primary task".

kumaran-is Bundle

Angular 21.x core patterns and APIs — Signals, Standalone components, Zoneless change detection, SSR/Hydration, Dependency Injection, Component composition, Signal-based state, Testing. Load when writing Angular code for API reference, testing patterns, or SSR configuration.