Loading...
Loading...
Found 4,084 Skills
Use when installing or running the Inngest CLI and Dev Server for local development, local testing, serve endpoint debugging, Docker or Docker Compose setup, MCP configuration, self-hosted `inngest start`, or deployment workflow checks. Covers `inngest dev`, `inngest start`, auto-discovery, config files, environment variables, `@inngest/test`, local event sending, platform gotchas, and production/self-hosted server flags.
Author and maintain MANUAL and hybrid test cases and suites in TestRail, Xray (Jira), Zephyr Scale, and Qase. Covers test-case anatomy (title, preconditions, steps, expected results, test data), suite/section organization, bulk authoring from user stories and acceptance criteria, ambiguous-step linting, CSV/API import-export payloads per tool, requirement traceability and coverage gaps, review hygiene, and when a manual case should graduate to automation. Use when: "write a test case," "manual test case," "TestRail case," "Xray test," "Zephyr Scale case," "Qase case," "import CSV into TestRail," "lint these steps," "traceability report," "should this be automated." Not for: Generating automated TEST CODE — that is ai-test-generation. Sprint-level WHAT-to-test selection — that is test-planning. Related: ai-test-generation, test-planning, exploratory-testing, qa-project-context.
On-chain trading signals and custom signal strategy management on Binance Web3. Three signal sources: smart money (wallet buy/sell events), platform strategies, and user-created strategies (meme / fomo). Four scenario domains: (A) Reports — daily report, monthly backtest review (BSC vs Solana, protocol comparison); (B) Signal discovery — feed, sort by maxGain or multi-strategy hit, token buyability ("can I still buy"); (C) Analysis — backtest interpretation, strategy comparison by golden/silver/bronze rate, indicator impact (KOL holdings, protocol, liquidity); (D) Management — create/update/delete strategies, enable/disable strategies, trigger/schedule backtests, query credits, auto-scan, copy strategies from the strategy hall. Trigger whenever the user mentions trading signals, smart money, custom signal strategies, backtesting, strategy management, daily or monthly reports, token buyability, or indicator impact analysis — even if they don't say "signal" or "strategy".
Routes tasks related to reverse engineering, exploitation, penetration testing, malware, mobile security, firmware analysis, browser automation, documentation, and other security domains to the appropriate specialized skill modules. Use this when a task spans multiple modules or the correct entry point for reverse engineering skills is unclear.
Track custom events and conversions with Vercel Web Analytics. Covers common events, form tracking, and development testing.
Complete React + Vite expertise for building optimized, scalable applications. Covers project architecture, folder structure, component patterns, performance optimization, TypeScript best practices, testing, and build configuration. Use when building React apps with Vite, organizing projects, optimizing performance, or implementing best practices. Includes code generators, bundle analyzer, and production-ready templates.
Refactors brittle snapshot tests into resilient, focused assertions. Provides strategies for reducing snapshot size, extracting meaningful assertions, and maintaining snapshots. Use for "snapshot testing", "snapshot refactoring", "brittle tests", or "assertion improvement".
Shared Go best practices for LlamaFarm CLI. Covers idiomatic patterns, error handling, and testing.
Use when ML engineers need to identify symmetries in their data but don't know where to start. Invoke when user mentions data symmetry, invariance discovery, what transformations matter, or needs help recognizing patterns their model should respect. Works collaboratively through domain analysis, transformation testing, and physical constraint identification.
Zero Script QA - Testing methodology without test scripts. Uses structured JSON logging and real-time Docker monitoring for verification. Use proactively when user needs to verify features through log analysis instead of test scripts. Triggers: zero script qa, log-based testing, docker logs, 제로 스크립트 QA, ゼロスクリプトQA, 零脚本QA, QA sin scripts, pruebas basadas en logs, registros de docker, QA sans script, tests basés sur les logs, journaux docker, skriptloses QA, log-basiertes Testen, Docker-Logs, QA senza script, test basati sui log, log docker Do NOT use for: unit testing, static analysis, or projects without Docker setup.
Creates new Robot Framework test cases for SnapLogic pipeline testing. Use when the user wants to create a new test file, add test cases to existing files, or needs test templates for specific system types (Oracle, PostgreSQL, Snowflake, etc.).
Implement state machines with AASM for workflow management. Covers state transitions, guards, callbacks, and testing.