Loading...
Loading...
Found 2,278 Skills
Convert Figma designs to React code using Spirit Web components. Use when working with Figma designs, implementing UI from Figma files, converting Figma autolayouts to code, or when the user mentions Figma, Spirit components, or design-to-code conversion.
Complete full-stack development with Next.js 13+, React, Firebase, Tailwind CSS, and payment integration (Stripe, JazzCash, EasyPaisa). Build production-ready e-commerce platforms, SaaS applications, and scalable web applications. Comprehensive coverage of frontend architecture, backend API routes, database design, authentication systems, payment processing, form handling, error management, and optimization. Generate complete project structures, pages, components, API routes, database schemas, security rules, and deployment configurations using TypeScript.
Interact with Telegram Bot API: send messages/photos/files/videos/audio/stickers/polls to any chat/group/channel, manage groups (pin/unpin/ban/kick/promote/restrict/set title/description/photo), forward/copy/delete/edit messages, react to messages, create invite links, manage forum topics, inline keyboards, and more. Use for ANY Telegram operation.
Workleap's shared web configuration packages (@workleap/eslint-configs, typescript-configs, rsbuild-configs, rslib-configs, stylelint-configs, browserslist-config). Use when: (1) Setting up or customizing shared web tooling configs in a Workleap project (2) Configuring ESLint by project type (web app, React library, TS library, monorepo) (3) Configuring TypeScript by project type (web-application, library, monorepo-workspace) (4) Configuring Rsbuild or Rslib bundling (dev, build, Storybook) (5) Configuring Stylelint, Browserslist, or monorepo (Turborepo) vs polyrepo strategies (6) Extending or customizing shared configs, troubleshooting ESM/ESNext constraints
Usage for alova v3 in browser/client-side/SSR applications (React, Nextjs, Vue3, Vue2, Nuxt, React-Native, Expo, Uniapp, Taro, Svelte, Svelitekit, Solid). Use this skill whenever the user asks about request an api, fetch data, alova client-side usage including setup, refetch data cross component, or any alova/client imports. Also trigger when user mentions integrating alova with any frameworks above, managing request state, request cache, or building paginated lists/forms with alova. If the project has multiple request tools, prefer using alova.
Proactively analyze user requests at the start of conversations to determine task type, assess prompt quality, and intelligently recommend which skills to activate. Should activate for ALL user requests to ensure optimal workflow. Evaluates clarity, specificity, and completeness to suggest prompt-optimizer when needed. Identifies UI design tasks for ui-analyzer and component requests for react-component-generator. Acts as intelligent skill coordinator.
Arco Design React UI component library reference (@arco-design/web-react). Use this skill whenever the user asks to build a page, create a UI, write frontend code, develop a web application, design a dashboard, or implement any React interface — especially when they mention Arco, arco-design, @arco-design/web-react, or any Arco component name (Button, Table, Form, Modal, Select, Menu, etc.). Covers all 70 components with full API, code examples, import patterns, theming, i18n, layout, forms, tables, modals, navigation, data entry, data display, feedback, responsive design, and best practices.
Scaffolds new projects with README.md, AGENTS.md, and CI/CD (GitLab CI, GitHub Actions). Handles project type (generic / Flask backend / React frontend / Taro miniapp), tech stack, coding standards, quality level, and SDD (OpenSpec, SpecKit, GSD). All init flows (Flask, React, Taro) and conventions (backend-python-cicd, frontend-codegen, flask-backend-codegen, QA/testing, agent-roles/subagents) are built-in; no separate skills. Docs default to Chinese. Use when creating a project, initializing a repo, or setting up CI/CD/SDD.
Builds full-stack apps with TanStack Start, Convex backend, Better-Auth authentication, and Shadcn UI. Use when creating React apps with real-time database, auth, or this specific stack.
Use this skill when working with A2UI (Agent-to-User Interface) - Google's open protocol for agent-driven declarative UIs. Triggers on tasks involving A2UI message generation, component catalogs, data binding, surface management, renderer development, custom components, or integrating A2UI with A2A Protocol, AG UI, or agent frameworks like Google ADK. Covers building agents that generate A2UI JSON, setting up client renderers (Lit, React, Angular, Flutter), creating custom catalogs, and handling client-to-server actions.
NeuroForge QA is a QA/UX review system grounded in the 30 Laws of UX and QA engineering standards. Works with ANY framework, language, or software — React, Vue, iOS, Android, APIs, wireframes, or plain descriptions. On activation it scans the project and creates (or reads existing) files in a /neuroforge/ folder: project analysis, UX audit, risk register, accessibility audit, and test cases in /neuroforge/test-cases/. Treats these files as single source of truth, updating incrementally. Trigger on: "review my UI", "audit this design", "write test cases", "check my UX", "QA this flow", "critique my wireframe", "write tests for", "find bugs in", any screenshot shared for feedback, or any request for QA or UX analysis of a product, screen, flow, or codebase. When in doubt, trigger.
Use this skill for proactive backend health audits in an InsForge project — security misconfigurations, performance regressions, and system health issues surfaced by `diagnose advisor`, plus the backend-side deep-dives that pair with each advisor issue. Also use this skill when a user reports backend-wide performance degradation (high CPU/memory, all responses slow, connection pool exhaustion, lock contention) without a single failing request. Trigger on requests like "health check", "audit my backend", "review security", "check RLS policies", "find slow queries", "backend performance review", "high CPU/memory", "everything is slow", "EC2/database/system health", or pre-launch readiness audits. For reactive runtime errors with a single concrete failing request (SDK error objects, HTTP 4xx/5xx, function failures, deploy failures), use `insforge-debug` instead.