Loading...
Loading...
Found 1,100 Skills
NautilusTrader algorithmic trading platform reference. NautilusTrader 量化交易框架参考。 Use this skill when: - Working with NautilusTrader API (使用 NautilusTrader API) - Implementing trading strategies (实现交易策略) - Running backtests (运行回测) - Configuring data feeds and adapters (配置数据源和适配器) - Debugging NautilusTrader code (调试 NautilusTrader 代码) - Understanding trading concepts like positions, orders, and fills (理解持仓、订单、成交等概念) Keywords: NautilusTrader, strategy, backtest, trading, adapter, Binance, quantitative, 量化, 策略, 回测
ALWAYS use when writing code importing "@vueuse/core". Consult for debugging, best practices, or modifying @vueuse/core, vueuse/core, vueuse core, vueuse.
ALWAYS use when writing code importing "pinia". Consult for debugging, best practices, or modifying pinia.
ALWAYS use when editing or working with *.vue files or code importing "vue". Consult for debugging, best practices, or modifying vue, core.
ALWAYS use when writing code importing "@vueuse/components". Consult for debugging, best practices, or modifying @vueuse/components, vueuse/components, vueuse components, vueuse.
ALWAYS use when writing code importing "@vueuse/integrations". Consult for debugging, best practices, or modifying @vueuse/integrations, vueuse/integrations, vueuse integrations, vueuse.
ALWAYS use when writing code importing "@vueuse/shared". Consult for debugging, best practices, or modifying @vueuse/shared, vueuse/shared, vueuse shared, vueuse.
ALWAYS use when writing code importing "vee-validate". Consult for debugging, best practices, or modifying vee-validate, vee validate.
ALWAYS use when writing code importing "primevue". Consult for debugging, best practices, or modifying primevue.
ALWAYS use when writing code importing "@tanstack/vue-query". Consult for debugging, best practices, or modifying @tanstack/vue-query, tanstack/vue-query, tanstack vue-query, tanstack vue query, query.
Analyze application logs for performance insights and issue detection including slow requests, error patterns, and resource usage. Use when troubleshooting performance issues or debugging errors. Trigger with phrases like "analyze logs", "find slow requests", or "detect error patterns".
ALWAYS use when writing code importing "@pinia/colada". Consult for debugging, best practices, or modifying @pinia/colada, pinia/colada, pinia colada, pinia-colada.