Web & Frontend

lossless-group Bundle

The Lossless Group's coined term and pattern — parent repos that aggregate child repos (often as git submodules) primarily to host a parent-level context-v/. Use whenever working anywhere in lossless-monorepo or its descendants, when starting any new task that might overlap with prior work, when scaffolding a new project, when the user mentions "pseudomonorepo", "submodule", "context-v", or names of the children (ai-labs, astro-knots, content-farm, tidyverse), AND ALWAYS when the user proposes to move/relocate/re-clone/re-nest a repo within the tree (which triggers the HARD STOP three-precondition checklist — local branches synced, remote branches catalogued, gitignored secrets backed up). Encodes the search-first-before-creating behavior, the tree-walking discipline, and the relocation-safety protocol.

lossless-group Bundle

The Lossless Group's workflow for filling in team and portfolio metadata for VC firms and the operating companies they back — crawl a firm's site, fetch structured data + brand assets for people and companies referenced in a deck/PDF, ingest as canonical .md files with YAML frontmatter. Supports two starting anchors — firm-anchored (one VC → its team → its portfolio → portco CEOs) and company-anchored (one operating company → its backer firms → each backer's team + portfolio, stopping there) — for credibility-card use. Use whenever you need to recreate VC team pages, advisor sections, or portfolio company sections in HTML/Tailwind/Reveal slideshows; whenever the input is "here's a PDF and/or a firm URL, fill in the people and companies"; whenever you need headshots, LinkedIn URLs, company logos (SVG preferred), CEO metadata; whenever you need to "ingest our backers" or "make these investors legible to readers"; whenever the user mentions "fill out the team", "find the headshots", "credibility ingest", "we nee

lossless-group Bundle

The Lossless Group's workflow for developing slides-only Astro sites for fundraise processes, aligned with the calmstorm-decks project patterns and the iterative approach from the "Develop a Slides-only Astro Site for a Fundraise Process" specification. Use when creating or modifying slide decks, managing slide variants, or implementing the structured iteration workflow for fundraise material development.

sordi-ai Skill

Apply when writing React components. Hook discipline, state placement, performance, async cleanup, and list keys.

tkoenig Skill

Get DaisyUI component snippets, layouts, templates, and theme configuration for Tailwind CSS 4. Use when building UI with DaisyUI 5 components.

tkoenig Skill

Use when the task asks for a visually strong landing page, website, app, prototype, demo, or game UI. This skill enforces restrained composition, image-led hierarchy, cohesive content structure, and tasteful motion while avoiding generic cards, weak branding, and UI clutter.

tkoenig Skill

Debug CSS override issues in Tailwind/DaisyUI/component-library projects. Use when styles do not apply as expected, active/hover states look wrong, `!important` does not win, `:where()` specificity is involved, or Tailwind `@layer`/generated CSS order may affect the cascade.

methasit-pun Skill

Kafka, Flink, Kinesis, and Spark Structured Streaming design — consumer groups, partitioning, exactly-once semantics, lag monitoring, windowing, and late-arriving data. Use this skill whenever the user needs real-time or near-real-time data processing, is redesigning a batch pipeline into streaming, asks about event-driven architectures, or mentions Kafka topics, consumer lag, checkpointing, watermarks, or stream-table joins. Also trigger when the user says batch is "too slow", stakeholders want "live" dashboards, or the pipeline needs to react to events as they happen rather than on a schedule. If latency requirements are under a few minutes, this skill should be active.

studio-moser Skill

Use when a Harness request needs proof from driving a machine, not reading code: launch or attach to a live app, page, browser, simulator, or device; exercise the flow; and capture fresh visual or runtime evidence you inspect. Trigger for opening, clicking through, verifying on screen/device, or proving behavior from a worktree under stated path, permission, or artifact constraints. Also use when Accessibility, Screen Recording, or simulator capability may be missing, so the result must be blocked rather than replaced with code inspection. Skip reading existing screenshots, one-off screenshot capture without workflow verification, writing tests without running a browser, explaining OS settings, or code-only verification.

studio-moser Bundle

Use when designing, building, or reviewing the interface of a native-feeling macOS desktop app implemented with Tauri, Svelte, HTML/CSS, Rust, or a WebView; especially when it resembles a website, dashboard, enlarged mobile app, or imitation Mac window. Not for Windows, Linux, iOS, Android, or SwiftUI-first UI.

studio-moser Bundle

Use to raise a design to a high bar — a website, screen, UI, presentation, graphic, mockup, HTML/CSS or SwiftUI/AppKit output — via the Gauntlet Loop: independent fresh-context critics that judge against an explicit "done" bar and iterate until they pass, instead of the generator grading its own homework. Triggers: "critique this design", "run the gauntlet", "design loop", "polish this", "make it better", "raise the bar", "is this good enough". Also invoke it from another design skill after building, to verify the output against that skill's checklist. If "done" is unclear, it asks the user for goals and reference examples first. Reserve for high-value / reusable artifacts — the loop is token-expensive. NOT for routine one-off tweaks.

wonderslife Skill

This skill should be used when setting up, auditing, or enforcing internationalization/localization in UI codebases (React/TS, i18next or similar, JSON locales), including installing/configuring the i18n framework, replacing hard-coded strings, ensuring en-US/zh-CN coverage, mapping error codes to localized messages, and validating key parity, pluralization, and formatting.

leeovery Bundle

Form handling with XForm component and useFormBuilder. Use when creating forms, handling validation errors, managing form state, or building form-based slideovers and modals.

leeovery Bundle

Testing strategy across unit, component, composable, API integration, and E2E layers. Use when adding tests, choosing the right tier for a piece of behaviour, setting up vitest or Playwright, or designing test seams for Nitro-side effects.

leeovery Bundle

Vue component patterns with Composition API and script setup. Use when creating components, understanding script setup order convention, organizing component directories, or implementing component patterns like slideovers, modals, and tables.

leeovery Bundle

Creating custom Vue composables with proper patterns. Use when building reusable stateful logic, shared state management, or encapsulating feature-specific behavior.

leeovery Bundle

Foundational architecture for Nuxt 4 + Vue 3 + Nuxt UI applications. Use when starting new projects, understanding project structure, or making architectural decisions about directory organization, technology choices, and pattern selection.

leeovery Bundle

Design tokens and theming via Tailwind 4 `@theme static` and Nuxt UI semantic classes. Use when registering custom type scales, motion curves, brand palettes, or contextual CSS overrides; also when building dark-mode-correct surfaces and View Transitions.

sreejithraman Bundle

Find a small, checked set of strong UI component references for a feature.

sreejithraman Bundle

Find architecture improvements, explain the findings and recommendations, then explore whichever one you pick. HTML reports are optional.

wangyendt Bundle

Send emails via SMTP with support for HTML formatting, file attachments, and email templates. Use when users ask to: (1) Send an email, (2) Email someone, (3) Send a notification, (4) Use email templates, or (5) Send files via email.

wangyendt Bundle

一对一辅导老师技能，用于解答数学题，生成HTML讲解文档和带配音的Manim动画视频。 核心工作流：数学分析 → HTML可视化 → 分镜脚本 → TTS音频 → 验证更新 → 脚手架 → Manim代码 → 渲染验证 触发条件：学生粘贴数学题图片、需要教学视频、需要HTML讲解资料 【重要】生成的视频必须带 TTS 配音，这是强制要求，不可跳过

312362115 Skill

快速原型技能：5 分钟出可交互 demo，验证想法和交互方案。 比 task-start 轻量得多——不需要 spec/plan，就是快速 PoC。 输出单个 HTML 文件，浏览器直接打开可交互。 触发词：快速出个 demo、试一下效果、原型、PoC、验证一下、快速搭个页面。 触发场景：验证交互方案、给老板演示想法、技术可行性验证、UI 方案对比。 和 task-start 的 UI 原型环节的区别：task-start 是流程中的一步， rapid-prototype 是独立的快速验证工具，可以在任何时候使用。

arcadi4 Skill

Use when writing new React components that involve state derived from props, event-driven side effects, or external subscriptions. Also use when auditing existing code for unnecessary useEffect calls, reviewing useEffect-heavy components, or refactoring to eliminate cascading renders. Applies to React 18+ codebases.

arcadi4 Skill

Use when debugging a CSS layouts, box-model mismatch, or DOM structure problem that keeps breaking under CSS tweaks.

arcadi4 Skill

Use when the partner asks for manual frontend QA, hand-testing, or step-by-step UI verification, or when you finish a frontend change and want to offer manual verification proactively. Especially when Playwright/Cypress/Selenium is unavailable, not worth setup, or the partner said "just check it manually." Requires direct communication with the human partner.

bruno-cunha-souza Bundle

Lazy-senior-dev posture for code output — before writing, climb the ladder: YAGNI → reuse what's in the codebase → stdlib → native platform → installed dep → one line → minimum that works. Never cuts validation, error handling, security, or accessibility. Governs what you build, not how you talk. Intensity levels: lite / full / ultra. Use on ANY coding task (writing, refactoring, fixing, designing, choosing dependencies), or when the user says 'ponytail', 'be lazy', 'yagni', 'simplest solution', 'do less', 'menos código', 'simplifica', or complains about over-engineering, bloat, or unnecessary dependencies. Not for non-coding requests (prose, translation, summaries).

bruno-cunha-souza Bundle

Web/API security lifecycle for Go, Next.js, Python, and Bun — design controls, active testing, supply-chain/CI-CD, and LLM/agentic/MCP coverage. Maps to OWASP Web Top 10 2025 + API 2023 + LLM 2025 + Agentic 2026. Triggers: 'security review', 'revisão de segurança', 'auditar segurança', 'pentest', '/code-security-review'.

gridlock-nyc Skill

Generates professional inline SVG data visualizations — bar charts, donut charts, progress rings, stat cards, comparison tables, and sparklines — from user-supplied data. Output is clean, print-ready SVG embeddable in HTML documents, reports, and one-pagers without external dependencies. Trigger phrases: "chart forge", "make a chart", "generate a bar chart", "create a donut chart", "visualize this data", "add a chart to my report", "SVG chart", "data visualization", "make this visual", "progress ring", "stat card", "inline chart", "embed a chart", "chart from this data", "turn this into a chart". Do NOT use for: code analysis, architecture diagrams, flowcharts or system diagrams (use /plan-directions), data analysis or statistics (use exploratory-data-analysis), writing or editing document prose, generating images via external APIs, or any task that does not involve rendering data as SVG.

gridlock-nyc Skill

Run build, typecheck, lint, tests, and security checks for the current project. Auto-detects Python vs Node/Next.js.

gustavoalecio Bundle

Gera uma proposta comercial (orçamento) da sua empresa (definida em company.json) em Markdown, HTML e PDF, a partir de uma conversa guiada com o usuário.

impertio-studio Bundle

Use when styling Draw.io shapes, connectors, or labels. Prevents the common mistake of using wrong property names, missing html=1, or mismatched perimeters that cause rendering failures. Covers style string syntax, property categories, color system, fontStyle bitfield, and perimeter requirements. Keywords: drawio style, fillColor, strokeColor, fontStyle, perimeter, shape style, mxGraph CSS, change color, style shape, bold text, customize appearance, shape doesn't look right.

impertio-studio Bundle

Use when a Draw.io diagram fails to render, shows errors, or has structural problems. Prevents wasting time on symptoms by providing a diagnostic decision tree from symptom to root cause to fix. Covers XML structure errors, missing required cells, duplicate IDs, broken parent references, invalid styles, and HTML escaping issues. Keywords: drawio error, XML error, diagram broken, not rendering, duplicate ID, missing cell, invalid style, diagram won't open, Draw.io shows error, blank diagram, XML parse error.

impertio-studio Bundle

Use when creating shapes, connectors, groups, or containers in Draw.io XML. Prevents the common mistake of missing vertex/edge flags, broken parent references, or unescaped HTML in labels. Covers mxCell vertex/edge creation, UserObject metadata wrappers, HTML labels, placeholders, groups, and container nesting. Keywords: mxCell, vertex, edge, UserObject, object, HTML label, container, group, parent, create shape, create connector, add label, nest shapes, group elements.

impertio-studio Bundle

Use when creating C4 model diagrams, software architecture views, or cloud architecture diagrams in Draw.io. Prevents mixing cloud provider stencils in the same view or using wrong C4 color conventions. Covers C4 system context, container, and component diagrams, AWS/Azure/GCP stencil usage, and deployment views. Keywords: C4 model, architecture diagram, system context, container diagram, AWS, Azure, GCP, deployment, software architecture, cloud diagram, system design, infrastructure diagram.

impertio-studio Bundle

Use when encountering Vite build failures, chunk size warnings, or version-specific build errors. Prevents the common mistake of using deprecated rollupOptions in v8 or misconfiguring build targets and minifiers. Covers Rolldown/Rollup bundling failures, CSS minification errors, sourcemap problems, library mode build failures, BundleError handling, and asset processing errors. Keywords: build error, Rolldown, chunk size, sourcemap, library mode, minify, BundleError, rollupOptions, build.target, build fails, vite build broken, chunk too large, production build error, output too big.