Total 59,422 skills
Showing 12 of 59422 skills
Deploy, manage, and optimize vector databases for AI applications. Covers Qdrant, Weaviate, pgvector, and Pinecone — collection management, indexing strategies, backup, and performance tuning for production RAG and semantic search workloads.
Turn a destination, some dates, and your vibe into a realistic day-by-day trip itinerary — paced for real humans, with a packing list and a rough budget. Use when asked to plan a trip, build a travel itinerary, what should I do in [place], or help me plan my holiday. Produces a day-by-day plan grouped by area (so you're not criss-crossing the city), must-book-ahead flags, a packing list tuned to the trip, a rough budget range, and honest notes on pace and gaps to fill with local info.
Expert integration of Supabase Auth with Next.js App Router
Escolher, compor e adaptar uma biblioteca de componentes React com Tailwind CSS para landing pages, marketing, navegação, formulários, dados, feedback e tipografia. Use quando uma interface React precisar de referências TSX reutilizáveis, exemplos visuais ou uma composição de página; use sempre em conjunto com a skill specsfy-specialist-ui-design, que governa hierarquia, layout, estados e coerência visual.
Implementar, revisar e operar aplicações Laravel — HTTP, Eloquent, autorização, filas, eventos, cache e testes. Use quando o projeto contém `artisan` ou `laravel/framework` e a tarefa toca rotas, controllers, models, policies, jobs, commands, migrations, Pest ou PHPUnit; não use para PHP sem Laravel nem para modelagem de Postgres em si — combine com `specsfy-specialist-postgres` quando a decisão for de schema ou índice.
실질적으로 빈 폴더에서 새 프로젝트의 Git, AGENTS.md, CLAUDE.md와 최초 저장점을 준비한다. “프로젝트 세팅해줘”, “새 프로젝트를 만들어줘”, “새 프로젝트 작업 환경을 준비해줘”, “이 빈 폴더를 초기화해줘”라는 요청에 사용한다. 기존 코드나 프로젝트 설정이 있는 폴더에는 사용하지 않는다.
Generate a step-by-step manual QA and test plan for a feature just implemented, grounded in the actual code changes, and save it to docs/qa for a human to run. Use when a coding session wraps and you want to hand-test the result, or the user says "write a QA plan", "make a manual test plan", "how do I test this", "generate a testing plan for this feature", or runs /qakit.
Platform basic capabilities exclusively for Feishu CLI, not a universal fallback for all Feishu requests. Covers configuration initialization, OAuth login and Token/Profile management, doctor diagnosis, OpenAPI schema query, general API pass-through, global search, as well as user and department queries. This Skill must be used when users mention Feishu login, Device Flow, scope, User/Tenant Token, Token expiration, profile, doctor, 99991672/99991679, querying API path/parameters/scope, raw api, calling unencapsulated OpenAPI, searching documents/messages/apps, or querying users, emails, departments. It is explicitly prohibited to use this Skill for document content, cloud disk files, messages/group chats, Sheet/Bitable, whiteboard/presentation, calendar/task/approval/attendance/OKR, email, or meetings/Miaoji; these business operations should be handled by corresponding domain Skills. The "global search" here only refers to `search docs/messages/apps`, excluding queries within business domains such as approval, meetings, email, etc. When a request involves approval, approval_code, approval definition/instance/todo, this Skill must not be used; use feishu-cli-work instead. When video conferences, Miaoji, minute, recording or verbatim transcripts are involved, use feishu-cli-meetings instead.
Nuxt adapter for embedding emulators directly in a Nuxt app via @emulators/adapter-nuxt. Use when the user needs to embed emulators in Nuxt, set up same-origin OAuth for preview deployments, create an emulate catch-all server route, configure persistence for embedded Nuxt emulators, or wrap nuxt.config with withEmulate. Triggers include "Nuxt emulator", "adapter-nuxt", "embedded emulator", "same-origin OAuth", "createEmulateHandler", "withEmulate", or any task requiring emulators inside a Nuxt app.
When the user wants to write, rewrite, or improve marketing copy for any page — including homepage, landing pages, pricing pages, feature pages, about pages, or product descriptions. Also use when the user says 'write copy for this page,' 'rewrite this,' 'our messaging is off,' 'help me with the words,' 'write a headline for this,' or 'our copy isn't resonating.' For editing existing copy, see copy-editing. For page conversion optimization beyond just copy, see page-cro.
Use when creating or changing a Bagisto payment method — a payment class, the payment methods config, the checkout redirect and callback flow, or integrating a gateway such as Stripe or PayPal. Trigger phrases include "payment", "payment method", "payment gateway", "Stripe", "PayPal", "Razorpay", "checkout payment", "redirect", "webhook".
Use when writing or updating any Bagisto documentation site — the developer documentation, the merchant user guide, or any other Bagisto docs repository — covering page content, code samples, screenshots, the sidebar, image naming, and moving or deleting pages. Trigger phrases include "docs", "documentation", "user guide", "developer documentation", "dev docs", "merchant documentation", "marketplace docs", "document this", "update the docs", "add a doc page", "screenshot", "ImagePopup", "redirect a doc page".