productivity▌

이 스킬이 호출되면 아래 STOP PROTOCOL을 반드시 따른다.

Use the use_figma tool to execute JavaScript in Figma files via the Plugin API. All detailed reference docs live in references/.

Capture architectural decisions as they happen during coding sessions. Instead of decisions living only in Slack threads, PR comments, or someone's memory, this skill produces structured ADR documents that live alongside the code.

Structure vague product requests into validated opportunities and testable solutions before building. \n \n Guides teams through a five-question discovery process: extract desired outcome, identify customer problems (opportunities), generate solution ideas, evaluate feasibility and impact, and select a proof-of-concept to test first \n Prevents \"feature factory\" syndrome by forcing divergence across multiple opportunities and solutions before converging on what to build \n Outputs a structured

Build WCAG 2.1 AA compliant websites with semantic HTML, ARIA, focus management, and screen reader support. \n \n Covers five core areas: semantic HTML element selection, ARIA patterns (labels, live regions, roles), keyboard navigation with focus traps, color contrast requirements (4.5:1 text, 3:1 UI), and accessible form design with validation \n Includes 12 documented accessibility issues with prevention strategies, from missing focus indicators to keyboard traps to insufficient contrast \n Pr

Evaluate feature investments using revenue impact, cost structure, ROI, and strategic value. \n \n Guides product managers through a structured 4-step assessment: revenue connection (direct monetization, retention, conversion, expansion), cost structure (dev + COGS + OpEx), constraint evaluation, and ROI calculation \n Delivers one of four recommendation patterns: build now (strong ROI), build for strategic reasons (marginal ROI but competitive/platform value), don't build (poor ROI), or build l

Create Zustand stores following established patterns with proper TypeScript types and middleware.

Learn from practitioners, not theorists—build skills based on real-world case studies and failure patterns. \n \n Focuses on finding practitioners who excel in their domain, then extracting their concrete methods through case studies, failures, and before/after comparisons rather than abstract theory \n Workflow: narrow the task, collect golden cases (what top performers do) and failure cases (common mistakes), identify patterns through contrast, then use theory only to explain why \n Emphasizes

You are an expert team communication specialist focused on async-first standup practices, AI-assisted note generation from commit history, and effective remote team coordination patterns.

Use this skill when working with applications, agents, workflows, or migrations built on Microsoft Agent Framework.