Loading...
Loading...
Found 16 Skills
Technical spike and research investigation specialist. Use when exploring options for a technical decision, conducting timeboxed investigations, or evaluating technology choices.
Technical Research Expert Skill, providing systematic technical research methodologies, document specifications, and best practices. Trigger this skill when you need to conduct technology selection, architecture research, framework comparison, or implementation scheme research.
Conduct technical research on technologies and architecture. Use when the user says they would like to do or produce a technical research report
Complex research requiring deeper analysis, multi-step reasoning, and sophisticated source evaluation for technical, academic, or specialized domain queries needing expert-level analysis, high-stakes decisions, or multi-layered problem solving.
Use when you need to research, analyze, and plan technical solutions that are scalable, secure, and maintainable.
Use whenever researching a technical question — a library, tool, API, error, version, or "what's the best way to X" — or whenever you're about to answer from memory. Forces multiple real searches over primary sources (official docs, source code, high-vote Stack Overflow, maintainer blogs) instead of one search plus training-data filler, and rejects SEO content-farm slop. Trigger on "research X", "look into", "what's the best library for", "how does X work", "is this still true", "find out".
Research libraries, APIs, and patterns using searchGitHub and Exa tools. Finds real-world implementations and saves structured reports to docs/research/. Use when investigating technologies, debugging issues, or comparing options.
Researches how the industry solves a defined issue, collects references from engineering blogs, open-source projects, and technical articles, then produces a design document with industry baseline, research summary, design goals, non-goals, and proposed design. Use when an issue definition exists in docs/issues/ and a concrete design is needed before implementation begins.
Microscopic deconstruction and exhaustive analysis of code, systems, documents, or concepts. Breaks subjects into atomic components, examines every facet, and produces encyclopedic reports. Use when deep understanding is needed before making changes, analyzing unfamiliar codebases, or producing thorough technical documentation. Triggers on "심층 분석", "deep dive", "분석해줘", "해부", "deconstruct", "뜯어봐", "thoroughly analyze", "코드 분석".
Use when a technical question needs a real experiment to answer, to generate a structured spike spec before executing it in a separate session
Search the web using Perplexity AI. Use when needing to search, look up, research, find current information, best practices, compare technologies, or answer factual questions about tools and libraries.
Technical research methodology with YAGNI/KISS/DRY principles. Phases: scope definition, information gathering, analysis, synthesis, recommendation. Capabilities: technology evaluation, architecture analysis, best practices research, trade-off assessment, solution design. Actions: research, analyze, evaluate, compare, recommend technical solutions. Keywords: research, technology evaluation, best practices, architecture analysis, trade-offs, scalability, security, maintainability, YAGNI, KISS, DRY, technical analysis, solution design, competitive analysis, feasibility study. Use when: researching technologies, evaluating architectures, analyzing best practices, comparing solutions, assessing technical trade-offs, planning scalable/secure systems.