start-phase-plan
Mode 1 - Strategic planning with human approval before execution
Discover business sales marketing skills, compare source repositories and read the instructions for each workflow.
Mode 1 - Strategic planning with human approval before execution
Project management database for tracking specs, jobs, tasks, and execution
Generate a Product Requirements Document (PRD) for a new feature. Use when planning a feature, starting a new project, or when asked to create a PRD. Triggers on: create a prd, write prd for, plan this feature,...
Engage in a socratic-sage interview-style collaborating session to understand exactly what the user wishes to build. Must be used for every request that touches more than 2+ files when creating features, buildi...
Audit for WCAG 2.1 AA compliance including keyboard navigation, ARIA usage, color contrast, and screen reader support. Use when building UI components, reviewing forms, or checking accessibility of new features...
Use for workflow guidance on HOW to work effectively. Covers task execution, decision escalation, and team coordination.
Guidelines for Plan Mode - focus on planning before implementation
「Clarity / Deference / Depth」と、1プロダクト=1焦点の構成・大きいタイポ・余白・最小CTAを抽象化して、Web UI設計に適用する。
Review and analyze design docs for health, quality, and improvement opportunities. Use when auditing design documentation, checking doc health, or identifying areas for improvement.
Explore implementation plans, status, and relationships. Provides comprehensive plan ecosystem navigation with filtering, health analysis, and actionable recommendations.
Structured logging and reporting system for development work sessions. Trigger: Completing development tasks, generating session reports, documenting changes.
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
Use when reviewing UI/UX design. Provides a checklist for colors, typography, accessibility, design patterns, design tokens, and writing guidelines.
Systematic feature planning workflow - use when starting complex features requiring structured approach
Use when working with Affinity CRM via MCP tools - find entities, manage workflows, log interactions, prepare briefings, find warm intros. Also use when user mentions "pipeline", "deals", "relationship strength...
Generate daily standup notes from memory. Use when user says "standup", "daily report", "what did I work on", "summarize my day", or needs work summary.
Micro-task development patterns with 50% context budget. Use for task decomposition, context management, escape hatch protocols, and orchestration patterns.
AI-powered PR creation after spec completion. Analyzes spec metadata, git diffs, commit history, and journal entries to generate comprehensive PR descriptions with user approval before creation.
Fast-capture intake queue for ideas and follow-up tasks. Add items quickly, list pending items, or dismiss resolved ones.
사용자의 기능 아이디어를 시니어 전문가 관점에서 검토하고 PRD를 작성합니다. 기획/API/비즈니스/개발 관점에서 일반 방법론과 비교하여 문제점과 트레이드오프를 분석합니다.
This skill should be used when designing UI/UX interfaces, creating design systems, or implementing user interfaces. It provides guidance on psychology-driven design principles (Fitt's Law, Hick's Law, Miller's...
This skill should be used when preparing for system design interviews or designing systems following interview best practices. It provides the 5-step interview framework, scale estimation techniques, and mock i...
Best practices for prospect research including company analysis, contact profiling, and signal detection. Triggers when researching companies, contacts, or preparing for sales calls.
Standard structure and style for sales call briefings including templates for full briefings and quick-reference cheat sheets. Triggers when generating or formatting prospect briefings.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.