Loading...
Loading...
Found 127 Skills
Unified team skill for brainstorming team. All roles invoke this skill with --role arg for role-specific execution. Triggers on "team brainstorm".
Generate novel research ideas with iterative refinement and novelty checking against literature. Score ideas on Interestingness, Feasibility, and Novelty. Use when brainstorming research directions or validating idea novelty.
Generate 5-10 tailored content concepts for a creator partnership that feel native to the creator's style rather than brand-dictated. This skill should be used when brainstorming content ideas for a creator campaign, generating influencer content concepts, ideating creator deliverables, coming up with content angles for an influencer partnership, developing video concepts for TikTok or Reels or YouTube Shorts, creating content hooks for a creator collab, building a concept menu for a creator brief, generating native-feeling content ideas for a sponsored post, or planning what a creator should actually make. For writing the full content brief after selecting concepts, see content-brief-builder. For building the campaign brief that precedes content planning, see campaign-brief-generator. For adapting a single concept across platforms, see multi-platform-format-adapter.
Use this skill when brainstorming, designing, or planning any Swift feature. This is the right skill whenever the user describes a feature they want to build, asks "how should I implement X", wants to think through a design, or starts with something like "I want to add..." or "let's plan...". Use it even if they don't explicitly say "brainstorm" — if there's a feature to figure out, start here before touching any code.
Product idea generation and business validation specialist. Use when brainstorming ideas, validating business concepts, analyzing market opportunities, or evaluating product-market fit. Triggers on "idea generation", "business validation", "market analysis", "competitive research".
Use this skill BEFORE implementing any new feature. This is NON-NEGOTIABLE for scope control. Use when evaluating features during brainstorming, planning new functionality, branches approach size limits (1000/1500/2000 lines, 15/25/30 commits). Do not use when feature is already approved and in progress. DO NOT use when: simple bug fixes with clear scope.
Create or update role-specific skill packages with deterministic files. Supports output to skills/ (open-source publishing) or .agents/teams/ (team use). Triggers: 创建角色, 新建 role, create role, 更新 role scope, edit role, update role, add role skill, 修改角色配置. Use when the user asks to create, update, or edit frontend/backend/product (or custom) role skills with auto-generated role fields, guided brainstorming fallback, and curated skills selection.
Research codebase, write concrete implementation plan. Use after brainstorming.
Use BEFORE brainstorming — when the user wants to capture WHAT a feature should do as Gherkin scenarios. Trigger when the user says "I need to build X", "let's spec this out", "what should this feature do?", or wants to formally capture a new edge case or bug as a BDD scenario.
Generate exactly 5 probability-weighted options for a specific decision point. Forces unconventional alternatives beyond safe defaults. For quick decision-point analysis, NOT full design exploration (use brainstorming for that). Triggers on "대안", "alternatives", "옵션 뽑아", "options", "어떤 방법이", "아이디어", "다른 방법", "선택지".
Collaborative blog writing assistant that guides users from topic to structured draft through iterative brainstorming. Acts as an advanced rubber duck — asking tough questions to help authors think deeper and gain clarity. Use this skill when a user wants to write a blog post, structure their thoughts into a post, turn notes/context into a blog, or needs help organizing ideas for written content. Also trigger when users mention "blog", "write a post", "help me write about", or have context files they want to turn into publishable content. Do NOT use for: editing existing drafts, proofreading, formatting, or when user just wants you to write something for them without collaboration.
Use when creating or iterating on a detailed per-subsystem technical design specification from a system spec, before starting OpenSpec workflow. Triggers: "design spec", "subsystem spec", "write the spec for S1", "phase breakdown", "implementation phases", "mid-level spec", "technical design". Encodes opinionated progressive phase discipline with FP progression and contract boundaries. Do NOT use for high-level system specs (use brainstorming) or for OpenSpec artifacts (use openspec directly).