Validate and enrich semantic references (ConceptIds) against the Knowledge Graph. Use when linking artifacts, specs, or code to ontology concepts, validating SHACL constraints, or discovering related concepts from DomainForge™.
Esta skill debe usarse cuando el usuario pide "consultar documentación de [paquete]", "agregar librería X", "migrar de A a B", "alternativa a librería", menciona errores de paquetes especializados, o necesita consultar documentación antes de implementar librerías de terceros por primera vez. También aplicable en modo plan cuando se requiera investigar paquetes especializados (zod, bull, sharp, ioredis, react-hook-form, etc.). NO para librerías comunes (express, react, lodash, axios).
開発中の問題解決と知見の記録。エラーや予期しない動作に遭遇したら既存のnotesを確認し、新しい発見はnotesに記録する。未解決の問題はissuesに記録する。「このエラーの解決策は？」「なぜ動かない？」などのリクエスト時に使用。
Expert sales engineering covering technical demos, solution design, RFP responses, POC management, and technical objection handling.
Expert methodology for breaking down complex problems into fundamental truths and rebuilding solutions from the ground up. Use when users need breakthrough innovation (not incremental improvement), question industry assumptions, face seemingly impossible problems, want to understand root causes, ask "why does this have to be this way", "rethink from scratch", "reimagine this", request analysis "from first principles", want to challenge conventional wisdom, question everything, or need to deconstruct problems to their core elements. Ideal for strategic decisions, innovation challenges, cost optimization, and escaping local optima.
This skill should be used when the user asks to "start a data science project", "brainstorm analysis", "plan a data analysis", or wants to clarify analysis requirements. REQUIRED Phase 1 of /ds workflow. Uses Socratic questioning to clarify goals, data sources, and constraints.
Deep research on features before building with co-founder mindset. Use when user wants to research a feature idea, explore if something is worth building, or says 'research this feature', 'is this worth building', 'explore this idea', or wants product + market + tech analysis.
Deep pre-execution analysis framework using four philosophers (Socrates, Aristotle, Feynman, Drucker) for structured critical thinking before implementing plans. Use when users need to thoroughly understand a topic, question assumptions, clarify objectives, or explore multiple perspectives before taking action. Triggered by phrases like "help me think through," "analyze this topic," "before we start," "I want to understand," or when complex decisions require deeper exploration.
Execute high-density architectural analysis on user ideas. Move from 'Vague' to 'Verified' using a 5-step logic chain: Calibration → Decomposition → Excavation → Re-Architecting → Inversion. This skill should be used when analyzing system architecture, validating technical ideas, or performing pre-mortems on solutions.
This skill should be used when the user asks "what is an ADR", "when should I create an ADR", "ADR best practices", "architecture decision records", "ADR lifecycle", "how to document architecture decisions", or needs guidance on ADR fundamentals, when to create ADRs, or ADR lifecycle management.
Provides legal guidance for contracts, compliance, intellectual property, data privacy, and regulatory matters. Use when reviewing contracts, ensuring compliance, protecting IP, or navigating technology law. Triggers include "contract review", "terms of service", "GDPR", "privacy policy", "intellectual property", "licensing", "compliance".
This skill should be used when the user asks about "ADR quality", "review ADR", "ADR checklist", "improve ADR", "ADR validation", "good ADR examples", or needs guidance on evaluating, improving, and maintaining high-quality architectural decision records.
Standards and templates for product vision, roadmap planning, and technology selection. Use when establishing product foundation or making strategic decisions.
This skill provides high-level overview about the network topology and functions to be achieved in the project. Use for understanding the project contexts outside of the codebase.
Expert UX research covering user research methods, usability testing, data synthesis, and research operations.
Comprehensive UX research assistant that analyzes user feedback from surveys, reviews, and interviews to identify trends, cluster themes, surface friction points, and generate actionable product roadmaps. Use when analyzing user feedback, conducting UX research, evaluating product performance, prioritizing features, or transforming qualitative/quantitative feedback into strategic insights.
Adversarial self-validation skill for verifying outputs before delivery. Applies systematic counter-argument challenges including "why is this wrong", "prove this is incorrect", and "why doesn't this make sense" to catch logical flaws, unfounded assumptions, and errors. Use when generating code, making claims, proposing solutions, or producing any output that benefits from validation.
This skill should be used when users request comprehensive analysis of technology ecosystems, comparing multiple libraries/frameworks/tools with quantitative metrics from GitHub and web research. Trigger words include "ecosystem analysis", "compare libraries", "analyze React/Vue/Python ecosystem", "trending libraries", "technology stack comparison", or requests to evaluate multiple technical tools with data-driven insights.
Skill for optimizing content, microcopy, and CTA placement for mobile viewports.
Guides the creation and review of Architectural Decision Records (ADRs). Use this skill when a significant architectural change is proposed, a new technology is introduced, or a trade-off needs to be documented.
Generate 1-page pursuit briefs for qualified RFP opportunities. Use when creating bid/no-bid decision documents or implementing pursuit brief generation features.
Perform structured judgment based on DoesThisFeelRight.com principles. Use this skill to evaluate systems, designs, and workflows through the DTFR frame.
Product roadmap prioritization and feature decision framework. Use when user asks about what to build next, whether to build a specific feature, roadmap prioritization, or feature validation. Helps challenge feature ideas, prevent feature creep, and maintain product focus based on stage-specific rules and impact vs effort analysis.
