Claude Skills by majiayu000

Analyze customer support data (Excel/CSV with PIT, Support Tickets, CSAT) to categorize issues, prioritize by impact (P0-P3), and generate strategic markdown reports with examples and trends.

Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to \"survey patterns\", \"find existing patterns\", \"look for analogous features\", \"check how similar things are done\", \"find prior art for this change\", or needs pattern context before planning a change.

Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to \"survey patterns\", \"find existing patterns\", \"look for analogous features\", \"check how similar things are done\", \"find prior art for this change\", or needs pattern context before planning a change.

Survey the codebase for analogous features, reusable utilities, and existing patterns relevant to a proposed change. Returns structured findings without writing code. Use when the user asks to \"survey patterns\", \"find existing patterns\", \"look for analogous features\", \"check how similar things are done\", \"find prior art for this change\", or needs pattern context before planning a change.

Audit PostHog survey SDK features and version requirements

Audit PostHog survey SDK features and version requirements

Analyze swap compatibility and safety. Use when evaluating proposed schedule swaps to ensure they maintain ACGME compliance and operational coverage.

Analyze swap compatibility and safety. Use when evaluating proposed schedule swaps to ensure they maintain ACGME compliance and operational coverage.

Generate and maintain deterministic SwiftUI-vs-Raven API parity reports and automation. Use when users ask to audit missing SwiftUI components/APIs, refresh coverage reports, reduce report noise, tune matching logic (owner-qualified names, constructors, operators), or update the weekly GitHub Actions PR workflow that publishes Reports/swiftui-api-gap/gap_report.md.

Generate probability-weighted alternative options that challenge default thinking. Forces unconventional alternatives and exposes hidden assumptions behind the "obvious" choice. For decision-point analysis, NOT full design exploration. Triggers on "대안", "alternatives", "옵션 뽑아", "options", "어떤 방법이", "아이디어", "다른 방법", "선택지".

Generate probability-weighted alternative options that challenge default thinking. Forces unconventional alternatives and exposes hidden assumptions behind the "obvious" choice. For decision-point analysis, NOT full design exploration. Triggers on "대안", "alternatives", "옵션 뽑아", "options", "어떤 방법이", "아이디어", "다른 방법", "선택지".

Exposes Claude's reasoning chain as an auditable, decomposable artifact. Quick mode (default) gives assumption inventory + weakest-link in 2 stages. Full mode (--full) adds decision branching, confidence decomposition, and falsification conditions. Triggers on "왜 그렇게 생각해", "reasoning", "근거", "show your work", "어떻게 그 결론이", "trace", "판단 근거", "why do you think that".

Exposes Claude's reasoning chain as an auditable, decomposable artifact. Quick mode (default) gives assumption inventory + weakest-link in 2 stages. Full mode (--full) adds decision branching, confidence decomposition, and falsification conditions. Triggers on "왜 그렇게 생각해", "reasoning", "근거", "show your work", "어떻게 그 결론이", "trace", "판단 근거", "why do you think that".

Build an evidence-cited SWOT of one company — yours or a competitor's — from public sources, ending with the S-O/W-T crossings. Use for strategy reviews, board prep, or competitor depth.

Apply SY1 Leverage Points to identify intervention points where small changes produce disproportionate effects.

Apply SY2 System Boundaries to define what is inside versus outside system scope for analysis or design.

Apply SY3 Stocks & Flows to distinguish accumulations from rates of change affecting them.

Apply SY4 Requisite Variety to match control system's complexity to system being controlled.

Apply SY5 Systems Archetypes to recognize recurring dynamic patterns across different domains.

Apply SY7 Path Dependence to acknowledge how early decisions constrain future options through accumulated consequences.

Sync cross-agent comparison (Dimension 8) across all analysis docs

Cross-domain integration using diffusion dynamics. Operationalizes intellectual chaos methodology - deliberately combining diverse materials to surface unexpected patterns. Use when given multiple documents from different fields, asked to find connections between disparate concepts, synthesizing across disciplines, or when user uploads varied materials expecting emergent insight.

Cross-domain integration using diffusion dynamics. Operationalizes intellectual chaos methodology - deliberately combining diverse materials to surface unexpected patterns. Use when given multiple documents from different fields, asked to find connections between disparate concepts, synthesizing across disciplines, or when user uploads varied materials expecting emergent insight.

Meta-mathematical connections, cross-domain synthesis, and the Complex Plane as a navigational tool. Classifies problems by quadrant (Abstract/Embodied x Logic/Creativity), routes them to relevant domains, and traces dependency chains. Use when classifying mathematical problems across domains, navigating the Complex Plane of Experience, finding cross-domain connections, or building multi-domain solution strategies.

Consolidate brainstorm rounds into an organized synthesis. Themes emerge, winners surface, evolution becomes visible.

Synthesize research findings into actionable insights

Synthesize research findings into actionable insights

Generate structured options with tradeoffs.

Consolidate inputs into a concise summary.

Deep cross-domain synthesis engine for the vault. Triggers on "synthesize X", "what do I know about X", "connect ideas about X", "cross-domain analysis of X", "map everything in the vault about X". Searches comprehensively, surfaces non-obvious patterns and tensions, then challenges the user to generate original thought. The vault should surprise you — if synthesis only confirms what you already think, it failed.

Use after layer analysis is complete to validate architecture documentation and generate a strategic rebuild plan focused on re-use decisions

Understand complex systems, interconnections, and emergent behaviors

Identifies bug-introducing commits using SZZ-style analysis based on bug-fixing commits, commit history, and code blame information. Use this skill when you need to trace bugs back to their origin, identify which commits introduced bugs, analyze bug-fix commits to find root causes, perform software repository mining for bug analysis, or conduct empirical studies on software defects. Triggers when users ask to find bug-introducing commits, identify when a bug was introduced, trace bug origins,...

General-purpose instability detector and killer. Tachyons are runaway modes -- imaginary mass, exponential growth, positive feedback disguised as negative. LRC resonance cancels instability without killing the system. GSO projection enforces symmetry constraints that eliminate entire classes of tachyon. What survives is the stable spectrum.

Tree of Attacks with Pruning for systematic code analysis

Targeted metabolomics analysis using MRM/SRM with standard curves. Covers absolute quantification, method validation, and quality assessment. Use when quantifying specific metabolites using calibration curves and internal standards.

Use when diagnosing bugs, analyzing errors/stack traces, or performing root cause analysis with evidence-based debugging protocols.

Use when investigating existing features, understanding logic flow, or exploring how code works.

Extract Federated Taxonomy tags from text. LLM extracts candidates, deterministic validation filters to known vocabulary. Returns bridge tags for multi-hop graph traversal.

Find LinkedIn profiles of a specific team or department at a company. Use when asked to get LinkedIn profiles, find team members, or look up people in a particular team/department/group at a company.

Compare your sales reps side by side on outreach volume, engagement rates, and meetings booked to identify top performers and coaching opportunities.

Assess team structure against Skelton's Team Topologies. Evaluate cognitive load, interaction modes, and Conway's Law alignment.

対象技術の最新情報を調査し、技術調査レポートを作成する

This skill should be used when analyzing technical debt in a codebase, documenting code quality issues, creating technical debt registers, or assessing code maintainability. Use this for identifying code smells, architectural issues, dependency problems, missing documentation, security vulnerabilities, and creating comprehensive technical debt documentation.

Assess technical patterns, integrations, and constraints in the domain to inform feasibility and strategy.

Build a technology radar for an engineering team, categorizing technologies into Adopt/Trial/Assess/Hold quadrants following the ThoughtWorks Tech Radar format. Use when asked to create a tech radar, evaluate the team's technology landscape, categorize tools and frameworks, or establish a technology strategy. Produces a full tech radar with quadrant tables, individual blip rationales, a decision trail, and a maintenance process guide.

**TECH STACK ADVISOR** - '기술 스택', '프레임워크 추천', 'DB 뭐 쓸까', '어떤 기술', '스택 선택', '뭘로 만들까' 요청 시 자동 발동. 비개발자 친화적 기술 선택 가이드. 유지보수성, 확장성, 학습 곡선 고려한 추천.

Comprehensive technology stack evaluation and comparison tool with TCO analysis, security assessment, and intelligent recommendations for engineering teams

Technology stack evaluation and comparison with TCO analysis, security assessment, and ecosystem health scoring. Use when comparing frameworks, evaluating technology stacks, calculating total cost of ownership, assessing migration paths, or analyzing ecosystem viability.

Analyze terms of service and privacy policies to identify concerning clauses, hidden permissions, and user rights implications