Loading...
Loading...
Found 52 Skills
Send commands to ESP32 and microcontrollers via serial port to emulate button presses and user actions. Use for automated testing, stress testing, and debugging without physical interaction.
Artillery Config Generator - Auto-activating skill for Performance Testing. Triggers on: artillery config generator, artillery config generator Part of the Performance Testing skill category.
Stress-test a plan, design, or architecture through relentless interviewing. Use when user says "grill me", "challenge this", "stress test my design", "review my plan", wants a design interview, or needs to think through decisions before building. Two modes — collaborative interview (default) and devil's advocate.
Create critical process briefs through challenging dialogue that exposes operational blind spots and stress-tests workflows. Use when user wants to map out business processes, operations, or workflows. Proactively finds gaps, exposes hidden complexity, identifies fragile points, and tests scalability. Creates structured process briefs in .ideas/[name]/process.md. Triggers include "how would this work operationally", "what's the process", "how do we deliver", or operational details questions.
Performance testing specialist for load testing, stress testing, and performance optimization across applications and infrastructure
Test application performance, scalability, and resilience. Use when planning load testing, stress testing, or optimizing system performance.
Diagnose risks and inefficiencies in an existing investment portfolio. Use when the user asks to review, audit, or stress-test their current holdings, evaluate portfolio concentration, check factor exposures, assess correlation risks, identify hidden tilts, or get actionable improvement suggestions for a portfolio they already own.
Gatling Scenario Creator - Auto-activating skill for Performance Testing. Triggers on: gatling scenario creator, gatling scenario creator Part of the Performance Testing skill category.
Harden designs for real-world use by systematically identifying and designing for every condition outside the happy path. Part of the Intent design strategy system. Covers state inventories, error recovery, empty states, loading patterns, first-run experiences, stress testing, internationalization readiness, and latency handling. Trigger on: edge cases, error states, empty states, loading states, first-run experience, onboarding, offline mode, "what happens when", "what if the user", "stress test this", "what could go wrong", "harden this design", "edge case review", "what are the failure modes", zero states, timeout handling, or any question about how a design behaves outside ideal conditions. The happy path is a fantasy — this skill designs for the world your users actually live in.
Risk measurement and stress testing via Longbridge — computes VaR (historical simulation / parametric), CVaR (expected shortfall), max drawdown, Sharpe ratio, Calmar ratio, and runs historical scenario stress tests (2008 GFC, 2020 COVID crash, 2022 rate-hike cycle). Triggers: "风险分析", "VaR", "压力测试", "最大回撤", "夏普比率", "CVaR", "历史情景", "尾部风险", "风险测量", "風險分析", "壓力測試", "最大回撤", "夏普比率", "歷史情景", "尾部風險", "風險測量", "risk analysis", "VaR value at risk", "CVaR", "stress test", "max drawdown", "Sharpe ratio", "Calmar ratio", "tail risk", "historical scenario".
Use this skill when > Conduct a comprehensive plan or design stress-test through systematic questioning. Interviews relentlessly about every decision point, resolves interdependencies progressively, and traverses the complete decision tree. Use when thoroughly vetting a proposal, design, or architecture before committing to it.
[BETA] Stress-test an existing implementation plan and selectively strengthen weak sections with targeted research. Use when a plan needs more confidence around decisions, sequencing, system-wide impact, risks, or verification. Best for Standard or Deep plans, or high-risk topics such as auth, payments, migrations, external APIs, and security. For structural or clarity improvements, prefer document-review instead.