use-case-development
Master use case development with actors, scenarios, preconditions, postconditions, and detailed specifications for comprehensive requirements.
Browse reusable Agent Skills, each with a clear purpose and practical guidance.
Master use case development with actors, scenarios, preconditions, postconditions, and detailed specifications for comprehensive requirements.
Create learning-oriented documentation following Diataxis framework. PROACTIVELY activate for: (1) teaching new concepts, (2) onboarding guides, (3) getting started documentation, (4) step-by-step learning paths. Triggers: "write tutorial", "create tutorial", "onboarding guide", "getting started", "teach me", "learning guide", "beginner guide"
Research keywords for Russian/CIS markets using Yandex Wordstat data. Analyzes search volumes, trends over time, and regional distribution. Use when user asks about keyword research, search volumes, trending topics, or what people are searching for in Russia/CIS.
Generate EARS-format requirements based on project description and steering context. Use when generating requirements from project description.
Use when the user wants to analyze or distill a blogger/account on Xiaohongshu or Douyin, benchmark a target creator, or diagnose their own content strategy. Trigger on requests such as “拆解博主””蒸馏博主””分析小红书博主””分析抖音博主” “诊断我的账号””对标账号””内容策略分析””小红书账号分析””抖音账号分析” “分析封面””关键词趋势””升级我的skill”.
Maintain Con's CHANGELOG.md and release notes. Use when updating changelog entries, preparing a beta/dev release, reviewing PR release-note coverage, or ensuring contributor PR credit is present.
Use when writing, editing, reviewing, or replacing UI copy, UX writing, microcopy, button labels, link text, form labels, helper text, empty states, error messages, confirmation dialogs, onboarding text, notifications, or user-facing product wording.
Synthesises the current conversation context into a Product Requirements Document and publishes it to GitHub (as a comment on a referenced issue, or a new issue). Synthesises from context; does not interview. TRIGGER when: the conversation has produced enough understanding of a feature and the user wants it captured as a PRD. DO NOT TRIGGER when: a single small issue is enough → creating-issues; the idea has not been stress-tested yet → grilling-ideas first; bug reports.