entry-signals
Entry signal patterns with historical success rates. Use when deciding whether to open a position.
trading-wisdom
Core trading insights learned from Agent Arena competition. Use when making any trading decision to apply institutional knowledge.
risk-management
Risk management rules learned from competition outcomes. Use when sizing positions or setting stop-losses.
tpm-spec-trace-ids
Annotate a Spec/PRD with Feature IDs and generate a Coverage Index. Use when user wants to add spec tags to a vision document, create F-nnn identifiers, set up traceability, or initialize a PRD framework for phased development.
tpm-roadmap-slice
Generate a Phase Spec/PRD by extracting features from an annotated Vision PRD. Use when user wants to create quarterly phase documentation, extract requirements from vision, plan a development phase, or decompose features into R-nnnn requirements. Requires annotated Vision PRD with F-nnn tags and Coverage Index.
simplify
Radical Simplicity Audit. Use when the user asks for advice on simplifying an idea, product, architecture, or system. Helps distinguish essential from superfluous.
self-improvement
Analyze autonomous loop session efficiency, track improvements, and view trends. Use when the user says "check loop metrics", "how are sessions doing", "analyze iterations", "self-improvement", "loop performance", "session efficiency", or wants to add/search/fix improvement records.
creative-direction
Develop brand creative treatments from GTM data. Use when the user says 'creative direction', 'brand treatments', 'brand tone', 'creative brief', 'brand identity direction', or wants to develop visual/verbal brand direction from their GTM decomposition.
nano-banana-image-gen
Generate images using the `imagen` CLI (Gemini and OpenAI models). Use when the user says "nano banana", "generate an image", "create an image", "make me a picture", "image gen", "draw", "illustrate", or wants to create images from text prompts.
idea-to-icp
Take a messy business idea and work through to structured GTM primitives — Product, ICP segments, value prop, beachhead market, and channel strategy. Use when the user shares a product idea, says 'decompose my idea', 'help me find my ICP', 'who should I sell to', 'idea to ICP', or wants to structure their go-to-market thinking.
find-bugs
Adversarial three-agent bug review pipeline. Runs search → adversary → judge to find high-confidence bugs with reduced false positives. Use: /find-bugs src/
five-whys
Root cause analysis technique for self-improvement. Use after any failure, mistake, or suboptimal outcome to find systemic causes and actionable changes. Triggers: analyzing why something went wrong, debugging repeated failures, post-mortem analysis, retrospectives, understanding root causes, reflecting on what could be improved.
webdev-token-input
Multi-value token/chip input patterns for tag inputs, filter bars, and email "To" fields. Builds on webdev-combobox-autocomplete with token state management, key:value parsing, context-dependent suggestions, and token editing patterns. Use when building filter inputs, tag selectors, multi-select chips, or any input that creates visual tokens/pills from text.
webdev-filter-query-builder
Domain-specific filter query building with AST representation, operator handling, query serialization, and field-type-specific inputs. Use when building advanced filter UIs for observability tools, data analytics, search interfaces, or any system requiring structured query construction with boolean logic, comparison operators, and URL/string serialization.
ui-design-iteration
Iterates on data-intensive UI designs to improve scannability, hierarchy, accessibility, and systematization. Use when improving an existing UI, reviewing a design for UX issues, or transforming a functional-but-flat interface into a polished product.
tpm-spec-verify
Enrich a Phase Sepc/PRD with Quality Requirements (Q-nnn) and Acceptance Criteria (AC-nnnn). Use when user wants to add QA perspective, define test criteria, identify non-functional requirements, add verification steps, or prepare a Phase PRD for test planning.
webdev-combobox-autocomplete
Foundational patterns for building accessible autocomplete/combobox components with state management, ARIA patterns, keyboard navigation, async suggestions, and framework-agnostic implementation. Use when building autocomplete inputs, command palettes, search inputs, select replacements, or any dropdown with keyboard navigation and suggestions.
project-handover-generator
Generate a practical project handover document from the current codebase and project artifacts. Use when a user needs to: (1) prepare resignation or transition handover docs, (2) summarize project architecture and responsibilities, (3) explain deployment, configuration, risks, and pending work for successors, (4) produce a structured, editable handover document grounded in the actual repository.
prd-gatekeeper
Engineering PRD gatekeeper that validates PRDs against 5 hard quality gates and ensures production-readiness for engineers. Use when reviewing, critiquing, or validating PRDs to ensure: (1) No implicit product decisions are pushed into implementation, (2) Success criteria are testable and verifiable, (3) Failure scenarios and dependencies are explicitly defined, (4) Scope is bounded with enforceable non-goals, (5) Engineering risk is assessable with clear responsibility boundaries.
resume-project-analyzer
Transform codebases into authentic, interview-defensible resume project experience. Use when analyzing a codebase for: (1) Extracting resume-ready project descriptions, (2) Preparing for technical interview questions about past projects, (3) Understanding the engineering depth and value of a codebase, (4) Identifying defensible technical achievements. Prioritizes correctness and interview credibility over exaggeration.
project-migration
Plan and drive safe old-to-new project or repository migrations with phase-based outputs, risk controls, and migration artifacts. Use when a user needs to: (1) audit an inherited or undocumented project before migration, (2) compare old and new repositories across tooling, architecture, routing, state, request, styling, CI/CD, or release flow, (3) produce migration deliverables such as audits, maps, diff matrices, plans, pilot scopes, adapter plans, risk lists, or verification checklists, (4) execute or update a specific migration phase such as intake, audit, map, diff, plan, pilot, execute, verify, or cleanup.
painpoint-validate
Validate whether pain points are real, frequent, severe, and poorly solved today. Use when the idea-to-requirement workflow reaches the `painpoint_validate` stage, or when independently producing `04-painpoints.md` from upstream stage documents.
motivation-clarify
Clarify why the idea exists and what external background or trigger supports it. Use when the idea-to-requirement workflow reaches the `motivation_clarify` stage, or when independently producing `01-motivation.md` from upstream stage documents.
skills-workflow-builder
Create a new dedicated workflow skill by reusing the existing skills-workflow (to collect/normalize a pipeline) and the existing skill-creator (to materialize the new skill). Use when you want a reusable workflow skill without re-entering skill order/templates each time.
solution-design
Design solution, modules, flow, inputs, outputs, processing logic, fallback, and tradeoffs. Use when the idea-to-requirement workflow reaches the `solution_design` stage, or when independently producing `08-solution.md` from upstream stage documents.
release-skills
Release workflow for baoyu-skills plugin. Use when user says "release", "发布", "push", "推送", "new version", "新版本", "bump version", "更新版本", or wants to publish changes to remote. Analyzes changes since last tag, updates CHANGELOG (EN/CN), bumps marketplace.json version, commits, and creates version tag. MUST be used before any git push with uncommitted skill changes.
user-identify
Identify target users, first adopters, non-target users, and user characteristics. Use when the idea-to-requirement workflow reaches the `user_identify` stage, or when independently producing `02-users.md` from upstream stage documents.
clean-code
Clean Code 规范总览与路由，覆盖命名、函数、注释、格式、对象与数据结构、错误处理、边界、测试、类、系统、并发、简单设计、渐进式重构及各类代码坏味道。当用户进行代码审查、重构、写新代码或询问 Clean Code / 整洁代码 / 代码坏味道相关规范时使用，并按主题加载 references 中的对应规则文件。Use for code review, refactor, writing new code, or any clean code / code smell / readability question; routes to the matching rule file under references.
doc-generator
Use this skill when the user wants to generate, update, or improve usage documentation for a project, file, component, SDK, module, or function based on source code.
value-assess
Assess user value, business value, engineering value, priority, and value strength. Use when the idea-to-requirement workflow reaches the `value_assess` stage, or when independently producing `05-value.md` from upstream stage documents.
doc-skill-creator
Use this skill when the user wants to convert one or more existing documents into a dedicated skill, including analyzing suitability, extracting capabilities, designing the skill structure, and drafting SKILL.md and references.
dev-spec
Spec-driven development workflow skill for product requirement intake, engineering research, technical planning, task breakdown, implementation, testing, bugfix loop, and engineering review. Use when a user wants to run or continue a structured software delivery workflow with explicit specs, durable artifacts, and iterative implementation/testing loops.
deep-learning
Systematically learn and explain the principles of a library, framework, module, function, or code path. Use when a user wants to understand overall architecture, module responsibilities, execution flow, call chains, core data structures, design tradeoffs, implementation details, or interview-ready explanations from source code.
skills-workflow
Interactive skills workflow for chaining multiple skills where the output of step i becomes the input of step i-1. Use when you need to: (1) Chain multiple skills together in a specific order, (2) Pass outputs between skills as inputs, (3) Execute complex multi-step workflows with traceability, (4) Run skills in dry-run mode before execution, (5) Debug or audit multi-skill workflows
api-generator
Autonomous Frontend Code Generation Agent specialized in project-aware API integration. Use when user provides backend API specs needing frontend request code, mock data to convert to request types and handlers, API endpoints to add with types mocks and tests, or new API integration following existing project conventions. Automatically detects TypeScript, request patterns, mock infrastructure, and test frameworks to generate artifact-gated code.
scope-define
Define MVP scope, non-scope, future scope, and tradeoff reasons. Use when the idea-to-requirement workflow reaches the `scope_define` stage, or when independently producing `09-scope.md` from upstream stage documents.
scenario-restore
Restore realistic user scenarios, current workflow, target workflow, and trigger moments. Use when the idea-to-requirement workflow reaches the `scenario_restore` stage, or when independently producing `03-scenarios.md` from upstream stage documents.
requirement-assemble
Assemble all stage documents and research into the final requirement, decision, and source summary. Use when the idea-to-requirement workflow reaches the `requirement_assemble` stage, or when independently producing `11-requirement.md` from upstream stage documents.
prompt-minifier
Minify verbose prompts into semantically equivalent minimal prompts while preserving behavior. Supports configurable output modes (prompt-only or prompt + compression report).
architecture-analysis
Comprehensive frontend architecture analyzer that identifies technology stacks, build tools, and architectural patterns. Use when you need to quickly understand a project's structure, dependencies, and technical configuration. Provides analysis for Vue/React/Angular frameworks, Node.js environments, package managers, TypeScript usage, linters, and architecture patterns with multiple output formats including executive summaries and visualizations.
dependency-analysis
Enhanced dependency analyzer with comprehensive markdown reporting and actionable recommendations. Use when you need to optimize frontend project dependencies, detect security vulnerabilities, identify unused packages, find duplicate functionality, analyze dependency impact, generate cleanup scripts, or produce detailed Markdown reports. Supports JavaScript, TypeScript, Vue, React, Angular, and modern build tools with parallel processing and incremental analysis capabilities.
unit-test-generator
Intelligent unit test generator for frontend projects that detects existing test frameworks and generates comprehensive tests for functions, components, and modules. Use when you need to: (1) Add unit tests to existing codebases, (2) Set up testing infrastructure for new projects, (3) Generate test cases for specific functions or components, (4) Ensure architectural consistency in testing approach across projects. Supports Jest, Vitest, Mocha with React, Vue, Angular frameworks.
acceptance-criteria
Define functional, process, exception, and non-functional acceptance criteria and DoD. Use when the idea-to-requirement workflow reaches the `acceptance_criteria` stage, or when independently producing `10-acceptance.md` from upstream stage documents.
feasibility-assess
Assess technical, product, business, cost, time, risk, and MVP feasibility. Use when the idea-to-requirement workflow reaches the `feasibility_assess` stage, or when independently producing `06-feasibility.md` from upstream stage documents.
goal-define
Turn vague intent into measurable user, business, and engineering goals and success metrics. Use when the idea-to-requirement workflow reaches the `goal_define` stage, or when independently producing `07-goals.md` from upstream stage documents.
idea-intake
Record a raw idea, create the idea workspace, and initialize status and source files. Use when capturing a new raw idea, or when the idea-to-requirement workflow reaches the `idea_intake` stage to produce `00-idea-intake.md`.
idea-requirement
Orchestrate the full evidence-driven workflow that turns a raw idea into a complete requirement by running 12 node skills with document persistence and Web Search evidence.
code-evolver
当用户要求将会话中的代码规范、工程约定、架构约束、命名规则、目录结构、测试要求、提交流程、协作规则或 AI 协作规则沉淀为长期可复用的项目规则，或在对话中持续出现这类稳定约束时，调用此 skill。用于识别规则、判断新增/更新/合并/冲突、过滤临时指令，并按职责同步到 .cursor/rules、AGENTS.md、CLAUDE.md。
context-probe
Minimal Context Sentinel Installer (All-Layers Broadcast). Installs a hard Context Sentinel rule into EVERY detected rule file to force assistant to append a sentinel token to every response. Use when (1) Installing context monitoring via /context-probe, (2) Checking installation status via /context-probe status, (3) Uninstalling via /context-probe off.
prompt-interviewer
Senior Prompt Engineer and Prompt Interviewer that interviews users to refine and complete their prompts through structured analysis and iterative questioning. Use when a user has an initial prompt but needs help refining it for better LLM performance: (1) When a prompt lacks clarity or context, (2) When constraints or boundaries are missing, (3) When output formats or quality criteria are undefined, (4) When there are ambiguities or conflicting requirements
Page 1208 of 1717 · 85836 results
