Loading...
Loading...
Found 442 Skills
Build and execute commands to obtain Japanese stock market data with J-Quants CLI (jquants). It supports acquisition of stock prices, OHLCV candlesticks, minute bars, tick data, margin trading balances, short selling ratios, futures, options, financial statements, dividends, TOPIX and index data. It also supports checking API availability and obtainable data periods (Free/Light/Standard/Premium) for each plan. Triggers: jquants, J-Quants, stock price, stock price data, ticker, OHLCV, minute bar, JPX, TSE, TOPIX, Nikkei 225, futures, options, derivatives, short selling, margin trading, dividend, financial statements, financial results, PER, PBR, ROE, index, bulk download, Japanese stock, market data, subscription, plan, data range, API availability, update time, data update, update timing, outdated data, latest data, data freshness, update schedule
Define the smallest viable experiment and MVP for a selected one-person company opportunity. Use when Codex needs to explain what MVP means when needed, verify prerequisites, ask one question at a time, present multiple MVP options, and write user-confirmed outputs into `opc-doc/`.
Apply Ansoff Matrix to evaluate growth strategy options across market and product dimensions. Use this skill when the user needs to decide how to grow — through existing vs new markets and existing vs new products. Also use when the user asks 'how should we grow', 'should we launch a new product or expand to new markets', or 'what's our growth strategy'.
Summarizes descriptive concepts for max pain options theory, covered-call style crypto ETFs, crypto arbitrage families and risks, and bull/bear flag chart patterns—always as non-prescriptive education. Use when the user asks about max pain, premium income ETFs, arbitrage, funding rates, flash loans, or bull/bear flags in crypto trading context.
Use this skill when rendering text in PixiJS v8. Covers Text for canvas-quality styled labels, BitmapText for cheap per-frame updates via glyph atlas, HTMLText for HTML/CSS markup via SVG, SplitText and SplitBitmapText for per-character animation, TextStyle, tagStyles, constructor options, TextOptions, HTMLTextOptions, BitmapText, SplitTextOptions, SplitBitmapTextOptions. Triggers on: Text, BitmapText, HTMLText, SplitText, SplitBitmapText, TextStyle, HTMLTextStyle, BitmapFont.install, tagStyles, fontFamily, wordWrap.
Decision Coaching for Vue Component/Composable Refactoring — Users paste a piece of code or point to an SFC, and the skill first performs a diagnosis ("Fat Trunk" / "UI & IO Entanglement" / "Reactivity & Business Logic Entanglement"), then selects one from three recipes, and provides a specific sequence of extraction steps (which variable to move first, what errors the compiler will throw, how to fix them one by one, when rollback is possible). The entire process ensures behavioral equivalence through compiler green lights + step-by-step rollback, without relying on test safeguards. Trigger scenarios: Users say "This Vue component is too fat / I want to extract the logic / Split this SFC / This composable is too messy / Extract a composable / Split into humble / Pure functionalize", or point to an obviously overlong .vue / composable file and request "Refactor / Optimize / Split". Only handles Vue (Vue 2 Options, Vue 2/3 `<script setup>`, composable, pinia store). Does not handle: Adding new features (follow feature process), fixing bugs (follow issue process), cross-module architecture restructuring, backend code.
Turn validated benchmark research into campaign briefs and concept candidates for short-form video production. Use this when you already have research artifacts such as reports, master tables, pattern tables, or comment analyses and need to produce fact-grounded briefs, concept lists, hook options, or test plans. This skill must stay anchored to real source data and should not invent angles, personas, or claims that are not supported by the available research.
Adversarial thinking partner for founders and executives. Stress-tests plans, prepares for brutal board meetings, dissects decisions with no good options, and forces honest post-mortems. Use when you need someone to find the holes before the board does, make a decision you've been avoiding, or understand what actually went wrong.
Collaborative design exploration for new features and architecture decisions. Triggers: 'brainstorm', 'ideate', 'explore options', or /ideate. Presents 2-3 approaches with trade-offs, documents chosen approach. Do NOT use for implementation planning or code review. Requires no existing design document — use /plan if one exists.
Wide before deep. Fans out N parallel divergent thoughts under structurally different cognitive frames (regulator, biology, speedrunner, 10 year old, $0 budget), then scores, clusters, prunes traps, and deepens only the top survivors. The isolated parallel branches and the separated generator/critic phases are load-bearing. Do not collapse them into a single linear thought. Use when the user asks to brainstorm, ideate, generate options, design an architecture, name something, pick between approaches, plan a refactor, design an API or SDK surface, generate hypothesis classes for a fuzzy bug, or any prompt of the shape "give me a few ways to". Also use when the obvious answer feels obvious and wrong, or when the user explicitly invokes /adhd or asks for "ADHD mode".
使用 parallel sub-agents 为 module 生成多个 radically different interface designs。Use when user wants to design an API, explore interface options, compare module shapes, or mentions "design it twice".
Create structured technology trade-off analysis documents with scored comparison matrices. Use this skill whenever the user wants to compare technologies, evaluate architectural options, analyze build-vs-buy decisions, assess migration strategies, or produce any decision document that compares multiple approaches across weighted dimensions. Triggers on: 'trade-off analysis', 'tradeoff', 'comparison matrix', 'evaluate options', 'which technology should we use', 'compare approaches', 'pros and cons of', 'build vs buy', 'migration analysis', 'consolidation analysis', 'technology selection'. Also use when the user has completed technical research and wants to structure findings into a decision document.