Loading...
Loading...
Found 1,839 Skills
Draft or update requirement documents under `easysdd/requirements/` for the project — describe a capability's "reason for existence, solution approach, and boundaries" using **user stories + plain language**, so non-technical readers can quickly grasp the key highlights of the system. Layered with architecture: requirement is the "problem space" (why this capability is needed), while architecture is the "solution space" (what structure is used to implement it). Two modes: new (draft a new requirement doc from scratch), update (refresh an existing doc based on new materials or implementation changes). Single-target rule — only modify one document at a time. Trigger scenarios: when the user says "fill in a requirement doc", "write down the requirements for this capability", "update the requirements directory", or when it is found during the feature-design phase that there is no corresponding requirement for the capability to be implemented this time.
Write or update external guide documents for the project —— dev-guide (for contributors/integrators/downstream developers) and user-guide (for end users). The output is stored in the project's docs/ directory, maintained alongside the code, and searchable by search tools. Difference from libdoc: guidedoc is task-oriented ("How to do Y with X"), while libdoc is reference-oriented ("What each part of X looks like"). Trigger scenarios: When the user says "write documentation", "developer guide", "user guide", or proactively push at the end of feature-acceptance.
Break down a requirement that is "too large to be implemented as a single feature" into a list of sub-features with dependencies and statuses, and place it in the independent `codestable/roadmap/{slug}/` directory — serving as the seed and scheduling basis for subsequent multiple feature processes. Two modes: new (draft a new roadmap from a large requirement), update (refresh an existing roadmap: add items, modify dependencies, reorder, mark as drop). Division of labor with requirements / architecture — those two record "what the system is now", while the roadmap records "what we plan to do next". Trigger scenarios: Users say "I want an X system", "Help me break down this requirement", "Schedule this large requirement", "Create a roadmap", or it is found during the feature-design phase that the requirement is too large to fit into a single feature.
Analyzes code architecture and structure — layer violations, circular dependencies, god objects, anemic domain models, missing boundaries, directory structure issues, and configuration problems. Generates severity-scored findings with fix prompts. Trigger phrases: "architecture review", "structure check", "layer analysis", "god class".
Initialize the memory system in the current directory, generating CLAUDE.md (optional AGENT.md for Cursor), MEMORY.md, and the memory/ directory. Triggered when the user says "initialize memory", "set up memory", "memory init", or "/memory-init".
Guide for operating the bitdrift bd CLI and analyzing live bitdrift account data — workflows, charts, sessions, issues, keys, connectors, and app health investigations. Trigger when the user wants to run bd commands, inspect live platform data, debug an app with bitdrift, create or edit workflows, read charts or metrics, triage crashes, inspect session timelines, or automate bitdrift operations from the CLI.
Generate a polished one-page PowerPoint slide summarizing key takeaways from recent funding rounds and notable capital markets activity across a user's watched sectors or companies. Use this skill when the user asks for a deal flow summary, weekly recap, funding digest, transaction roundup, or capital markets briefing. Triggers on: 'deal flow digest', 'weekly funding recap', 'deal roundup', 'transaction summary this week', 'what happened in [sector] this week', 'capital markets update', or any request to compile recent funding activity into a briefing slide. Produces a professional single-slide PPTX with key takeaways, valuation data, and Capital IQ deal links.
Analyst EPS estimate time series for a listed stock via Longbridge — tracks how the consensus EPS forecast (high / low / mean / median / analyst count) has changed over time, and shows actual values where reported. Answers "have analysts been raising or cutting their estimates?" Complements longbridge-consensus (current snapshot) by focusing on the historical revision trajectory. Triggers: "分析师预测历史", "EPS预测趋势", "一致预期变化", "预期上调下调", "分析师预期轨迹", "分析师EPS", "预测时间序列", "分析師預測歷史", "EPS預測趨勢", "一致預期變化", "預期上調下調", "分析師EPS", "analyst estimate history", "EPS estimate trend", "consensus revision history", "estimate time series", "analyst forecast trajectory", "EPS upgrade downgrade history".
ETF analysis framework via Longbridge — product screening (AUM/expense ratio/index), tracking error, liquidity (bid-ask spread/volume), premium/discount (NAV vs market price), and A-share ETF allocation insights. Triggers: "ETF分析", "ETF选择", "ETF跟踪误差", "ETF溢价", "ETF流动性", "ETF费率", "ETF规模", "宽基ETF", "行业ETF", "指数基金", "ETF分析", "ETF選擇", "ETF追蹤誤差", "ETF溢價", "ETF流動性", "ETF費率", "ETF規模", "指數基金", "ETF analysis", "ETF selection", "tracking error", "ETF premium discount", "ETF liquidity", "expense ratio", "broad market ETF", "sector ETF", "index fund".
Industry valuation rank time series for a single stock via Longbridge — tracks how a stock's PE / PB / PS / dividend-yield rank within its sector has changed over time (rank N of total M). Answers "is my stock becoming relatively cheaper or more expensive vs peers?" Complements longbridge-valuation (single-stock percentile history) and longbridge-industry-valuation (current sector snapshot). Triggers: "行业排名变化", "估值排名", "PE排名历史", "行业估值位置", "排名走势", "估值相对同业", "行業排名變化", "估值排名", "PE排名歷史", "行業估值位置", "排名走勢", "valuation rank", "industry rank history", "PE rank trend", "relative valuation rank", "sector ranking over time", "how does AAPL rank in industry PE".
Reads AR/AP, historical cash timing, and known fixed costs from QuickBooks, PayPal, Stripe, or Square — or a CSV upload — and produces a 30/60/90-day cash flow forecast with percentage-variance confidence bands and named risk flags. Delivers a chat summary and a downloadable XLSX. Use when the user asks "forecast my cash flow," "will I make payroll," mentions "runway," or says "cash crunch." Falls back to CSV upload when no connector is live.
Initialize a new MissionForge mission workspace with the required directory structure and template files.