Loading...
Loading...
Found 255 Skills
Create stunning, animation-rich HTML presentations from scratch or by converting PowerPoint files. Use when the user wants to build a presentation, convert a PPT/PPTX to web, or create slides for a talk/pitch. Helps non-designers discover their aesthetic through visual exploration rather than abstract choices.
Comprehensive Next.js, React, Redux, and TypeScript development guidelines covering SOLID principles, component architecture, and best practices.
TDesign Vue 3 component library usage guide, covering tdesign-vue-next 1.x series, including basic components, forms, tables, theme customization, dark mode, and AI Chat components
Use when scaffolding a new Nuxt 4 project with standard config files (prettier, eslint, gitignore, husky, vitest, tsconfig, sops) and bun scripts.
When the user wants to create, optimize, or audit 404 error pages. Also use when the user mentions "404 page," "404 error," "error page," "page not found," "broken link page," "404 design," "custom 404," "404 redirect," "404 page UX," or "404 recovery."
Documentation of the project's standardized approach to using `@vueuse/integrations/useAxios`. Focuses on minimizing boilerplate, leveraging global error handling, utilizing built-in state management, and enforcing consistent naming conventions.
Provides usage guidance for Instructure UI (InstUI) React components. Use when working with @instructure/ui packages, when asked how to use InstUI components, which component to choose, or how to apply props, guidelines, theming, or accessibility rules. Covers AiInformation, Alert, AppNav, Avatar, Badge, Billboard, Breadcrumb, Button, Byline, Calendar, Checkbox, CheckboxGroup, CloseButton, ColorContrast, ColorIndicator, ColorMixer, ColorPicker, ColorPreset, CondensedButton, ContextView, DataPermissionLevels, DateInput, DateInput2, DateTimeInput, DrawerLayout, Drilldown, Editable, FileDrop, Flex, FormField, FormFieldGroup, Grid, Heading, IconButton, Img, InlineList, InPlaceEdit, InstUISettingsProvider, Link, List, Menu, Metric, MetricGroup, Modal, NutritionFacts, NumberInput, Overlay, Pages, Pagination, Pill, Popover, ProgressBar, ProgressCircle, RadioInput, RadioInputGroup, RangeInput, Rating, Responsive, Select, SideNavBar, SimpleSelect, SourceCodeEditor, Spinner, Table, Tabs, Tag, Text, TextArea, TextInput, TimeSelect, ToggleButton, ToggleDetails, ToggleGroup, Tooltip, TopNavBar, Tray, TreeBrowser, TruncateText, View.
Use when executing next-safe-action actions from React client components -- useAction, useOptimisticAction, handling status/callbacks (onSuccess/onError/onSettled), execute vs executeAsync, or optimistic UI updates
Use when editing .astro/.mdx files, modifying astro.config.*, working with content collections (build-time or live), adding Tailwind CSS v4, using client directives (client:load/idle/visible), handling forms/actions with Zod 4, configuring server features (sessions, i18n, env vars, CSP, Cloudflare Workers), using view transitions or ClientRouter (<ClientRouter />), or setting up adapters (Node/Vercel/Netlify/Cloudflare) in an Astro project. Provides correct Astro 6 patterns, hydration guidance, view transition lifecycle, and prevents outdated Astro 3/4/5 code.
Génère des règles de design system personnalisées pour le codebase de l'utilisateur. À utiliser quand l'utilisateur dit « créer des règles de design system », « générer des règles pour mon projet », « configurer les règles de design », « personnaliser les guidelines du design system », ou veut établir des conventions spécifiques au projet pour les workflows Figma-vers-code. Nécessite une connexion au serveur MCP Figma.
Integrate CometChat into any app. Auto-detects your platform and framework, then walks you through picking and applying a chat experience. Start here — do not invoke platform-specific skills directly. Trigger with "/cometchat", "integrate cometchat", or "add chat to my app".
Guidelines for building AI-accessible web interfaces that work well with AI agents, automation tools, and screen readers. Use this skill whenever the user is building or reviewing a webpage, UI component, form, or frontend feature and any of these apply: they mention AI agents, automation, Playwright, web scraping, accessibility, a11y, aria, semantic HTML, or ask how to make their UI "agent-friendly", "AI-friendly", or "machine-readable". Also trigger when reviewing existing frontend code for accessibility or automation compatibility issues, even if the user doesn't explicitly mention AI.