Loading...
Loading...
Found 350 Skills
Application performance profiling and bottleneck identification — Node.js profiling, Chrome DevTools, flame graphs, memory leak detection, CPU profiling, React rendering performance. Activate on "profiling", "performance bottleneck", "flame graph", "memory leak", "slow app", "CPU profiling", "heap snapshot", "React re-renders", "EXPLAIN ANALYZE", "event loop lag", "clinic.js", "Core Web Vitals". NOT for infrastructure monitoring or observability (use logging-observability), load testing (use a load-testing skill), or database schema optimization.
Wind MCP Data Bridge Skill (v1.1.0, 6 servers / 19 tools). Route by `server_type`: (1) `quote` for market data (A-shares/Hong Kong stocks snapshots, daily/weekly/monthly K-lines, minute-level data); (2) `fund_data` for fund-related data (profile/finances/holdings/performance/holders/management company); (3) `stock_data` for in-depth stock data (profile/financial fundamentals/equity structure/events/technical indicators/risk); (4) `financial_docs` for document RAG (announcements/financial news); (5) `economic_data` for EDB macro + industry economic indicators; (6) `analytics_data` for general NL → Wind data. WIND_API_KEY is required (obtained by logging into the Developer Center at aimarket.wind.com.cn). Trigger scenarios: A-shares/Hong Kong stock codes/K-lines/minute-level data, any dimension of funds, stock financial reports/valuation, listed company announcements/financial news, macroeconomic data, cross-comparison of targets. **Excluded**: US stocks/European stocks/Japanese stocks, exchange rates/futures quotes, cryptocurrencies, non-financial data.
Browser automation and web browsing via managed Chrome instance. Open URLs, browse websites, interact with web pages, scrape/extract content, debug web pages, fill forms, take screenshots, and maintain login sessions with persistent profiles. Supports anti-detection for sites with bot protection. Use when: opening links/URLs, viewing web pages, logging into websites, extracting or scraping page content, debugging frontend issues, interacting with web applications, or any task requiring a browser. Triggers: open URL, open link, browse, visit website, view page, scrape, extract content, debug page, login to site, web interaction, screenshot, fetch page, browser, 打开链接, 打开网页, 浏览器, 抓取内容, 调试网页, start browser, stealth chrome, anti-detection, persistent login, browser profile, connect CDP.
Configures SQL audit logging on CockroachDB clusters to capture security-relevant events including authentication, privilege changes, and sensitive data access. Use when enabling audit logging for compliance, setting up role-based audit policies, or verifying audit configuration.
Full Sentry SDK setup for Node.js, Bun, and Deno. Use when asked to "add Sentry to Node.js", "add Sentry to Bun", "add Sentry to Deno", "install @sentry/node", "@sentry/bun", or "@sentry/deno", or configure error monitoring, tracing, logging, profiling, metrics, crons, or AI monitoring for server-side JavaScript/TypeScript runtimes.
Use when you need to design, review, or improve security in Micronaut applications — including micronaut-security authentication, @Secured and intercept-url-map rules, JWT/session strategies, SecurityService checks, CORS, CSRF awareness for browser apps, rejection handlers, and sensitive-data-safe logging. This should trigger for requests such as Add Micronaut security support; Review Micronaut security configuration; Improve API authorization in Micronaut; Add JWT security in Micronaut; Harden Micronaut route authorization rules. Part of cursor-rules-java project
Guides edge and tactical autonomous systems—perception-planning-control under latency and safety constraints; behavior trees/state machines vs learned policies; human-on-the-loop; geofencing, no-strike rules, mission abort; sim and field testing; ROS2/middleware patterns; sensor fusion; degraded modes; autonomy audit logging. Use for UAS/autonomous stacks, safety rules, HITL, sim-to-field validation, fail-safe—not LLM products (ai-engineer), LLM red team (ai-redteam), safeguard serving (ml-infrastructure-engineer-safeguards), governance only (ai-risk-governance), MCU firmware without autonomy (embedded-real-time-software-engineer), plant PLC/DCS (control-software-developer), HIL security bench (hardware-in-the-loop-security-tester).
This skill should be used when the user says phrases like "record a topic", "new topic", "how is this topic", "I have an idea", "help me note this down", or shares a rough content idea that needs evaluation and recording. Even if the user casually mentions a content idea, actively trigger the evaluation process without waiting for the user to explicitly say "record". First, use the five-dimensional logic of dbs-content to diagnose whether the topic is worth doing. Only record it if it is worth doing, and recommend 3-5 similar topics by drawing inferences. Do not trigger: Deepen the topic to generate an outline (use li-topic), directly write scripts (use li-writer), or AI polish or beautify the topic title. Use when the user wants to "record a topic", "log a topic idea", "is this topic worth doing", or shares a rough contentclaise Du.弹应用样子Pr广解除禁 \ 诊断和记录.
Personal C# conventions - style/structure (file layout, naming, member/ctor ordering, methods, types, visibility, modern C# 11/12/13 syntax, forbidden patterns, XML doc) and runtime behavior (DateTime/IClock, async, dispose, exceptions + Result, structured logging, secrets/config, LINQ, System.Text.Json, decoupling + DI lifetimes). Load before creating or editing any `.cs` file - writing, reviewing, or refactoring C#; do not lean on recalled conventions.
Checklists and anti-patterns for reviewing Go code. Covers API design, error handling, concurrency, interfaces, safety, performance, naming, testing, functional options, logging, and deterministic simulation testing.
Track which optimization experiment was best. Use when you've run multiple optimization passes, need to compare experiments, want to reproduce past results, need to pick the best prompt configuration, track experiment costs, manage optimization artifacts, decide which optimized program to deploy, or justify your choice to stakeholders. Covers experiment logging, comparison, and promotion to production.
Idiomatic Go HTTP middleware patterns with context propagation, structured logging via slog, centralized error handling, and panic recovery. Use when writing middleware, adding request tracing, or implementing cross-cutting concerns.