Loading...
Loading...
Found 10,840 Skills
Use when a PlayCanvas scene must read as a deliberate cinematic image rather than a flat asset preview, to set key and ambient lighting, sky and image-based lighting, shadows, tone mapping and exposure, and a restrained post-process grade of bloom, fog, and colour.
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.
Unified entry for Feishu Visualization and Display, responsible for selecting appropriate carriers, and covering whiteboard, Slides, Miaobi BOX dynamic components, Miaoda HTML applications, and unified data visualization design specifications. This Skill must be used when users request whiteboard/whiteboard, architecture diagrams, flowcharts, flywheels, fishbone diagrams, roadmaps, posters, illustrations, SVG/Mermaid, data charts or dashboards, creating Slides/PPT, embedding dynamic ECharts/maps/3D/window.magic components, or publishing HTML applications with Miaoda/Miaoda/spark. Message cards are constructed and sent by feishu-cli-messaging; Markdown chart import is executed by feishu-cli-docs.
Use when building a storefront app or UI on the Bagisto Shop API — a customer-facing storefront, catalog, cart, checkout, customer account, wishlist, compare, reviews, or any page or component of a shop on the API, whether web, mobile or custom. Ask the client's platform and stack first, and treat the api-docs as the source of truth for exact shapes. Trigger phrases include "products", "cart", "checkout", "coupons", "customer login", "customer account", "wishlist", "storefront on the API".
This skill should be used when the user asks to "make a Vox-style map animation", "animate a map zoom", "draw a route on a map", "highlight a country/region", "use Google Earth Studio", "drop pins on a map and animate them", "pan/orbit a camera over a map", or "add map graphics to an explainer video". Covers Earth Studio→After Effects camera import, GeoJSON/SVG vector map motion, pins/routes/highlights/labels, the 12fps stutter cadence, and data-driven Remotion renders.
Diagnose Polygres CLI, Runtime API, control-plane, standard or synchronized PostgreSQL project, job, migration, retrieval, and pgContext failures using public read-only evidence. Use for errors, sync preflight or lifecycle failures, timeouts, partial failures, readiness problems, ambiguous projects, failed Context collections or operations, stale point mappings, or broken graph, vector, text, hybrid, or Joint retrieval. Do not use private observability, undocumented endpoints, or mutating repair actions.
Functional Style Guidelines for TypeScript. Coding rules that must be followed when processing **/*.{ts,tsx,js,jsx} code: Prioritize pure functions and composition, restrict mutability, ensure precise typing, and maintain declarative data transformation.
Automated UI testing for Windows desktop apps — generate a batch test script with the `winapp ui` UI Automation harness, run all tests in one pass, read results. Covers element assertions, interactions, value checking (TextBox, ComboBox, ToggleSwitch), keyboard shortcuts and typing (send-keys), hover, drag-and-drop, touch and pen input, file pickers, flyouts, dialogs, persistence, accessibility audits, and screenshot/video capture. Works on any Windows app (Win32, WPF, WinForms, WinUI 3, packaged or unpackaged).
Vue SFC Structure Specification. Mandatory script setup organization order and responsibility layering rules when processing **/*.vue files: best practices including definition order, shallowRef selection, template binding functions, attrs inheritance, etc.
Reconcile session outcomes into persistent project memory files. Updates project state, backlog, and status via section-aware merging -- not a session dump. Use at the end of any significant work session. Use when: 'session close', 'close session', 'save session', 'update memory', 'wrap up', 'end of session', or before ending a big session.
Generate decision memos and product launch documents in Amazon's narrative style. Two modes: `memo` produces a 6-page narrative memo (Introduction, Goals, Tenets, State of Business, Lessons Learned, Strategic Priorities + unlimited appendix); `prfaq` produces a Press Release + External FAQ + Internal FAQ for product launches (work backwards from launch). Enforces Strunk's prose rules (active voice, concrete language, omit needless words, no qualifiers, parallel construction, topic-sentence paragraphs, no overstatement) and Anthropic's removability discipline at the line level. Use when: 'six pager', '6-pager', 'amazon memo', 'narrative memo', 'PRFAQ', 'press release', 'work backwards', 'decision memo', 'strategy doc', 'launch document', 'silent read doc', before any decision big enough to warrant the week-long writing process.
(NS) Senior Tech Lead code review on SOLID, clean code, performance, security, and testability. Use proactively after writing or modifying code, before opening PRs, after implementation closure, or when the user asks for a code review, PR review, or issue review gate — even if they do not name this skill. For GitLab issue execution with ISSUE_URL, use Issue review mode. Do NOT write code-review-report.md. Do NOT use for root-cause debugging (use ns-investigator).