Research

Reference and maintain the project's technical stack documentation including frameworks, languages, databases, testing tools, and third-party services to ensure consistency across all development work. Use this skill when choosing technologies for new features, when documenting technology decisions, when working with framework-specific code patterns, or when ensuring consistency with existing technology choices. Use this skill when working with any code file to verify it follows the conventions of the project's chosen frameworks and tools. Use this skill when setting up new dependencies, configuring build tools, or making architectural decisions about which libraries or services to use. Use this skill when onboarding new team members or creating technical documentation about the project's architecture and technology choices.

Provides quick reference for BI Dashboard (Plotly Dash) commands and operations. Activates when user asks how to run, test, or verify the BI Dashboard. Includes startup, shutdown, verification, and troubleshooting procedures.

Code review for Paweł Lipowczan portfolio project (React+Vite+Tailwind SPA). Use when user wants to review code changes, pull requests, commits, or modifications in portfolio project. Verifies architecture compliance, SEO standards, accessibility (WCAG 2.1 AA), performance (Core Web Vitals), blog system (markdown frontmatter, OG images), prerendering setup, and edge cases. References docs/{PRD.md,SRS.md,TODO.md,blog/BLOG_WORKFLOW.md}. Focuses on bugs, edge cases, and conditions causing errors after deployment.

Deep technical assistant for projects that combine Neural Quantum States (FFNN and Transformer-based) with Sample-based Quantum Diagonalization (SQD). Trigger this skill whenever the task involves: (1) designing or analyzing NQS architectures for quantum chemistry, (2) connecting classical samplers to qiskit-addon-sqd, (3) studying sample-efficiency, bias, and variance in few-sample regimes (e.g. 12–14-bit H2).

Use the `date` command via Bash tool whenever you or the user mention time, dates, or temporal concepts. Verify current date/time before ANY temporal response, as environment context may be outdated. Parse expressions like "tomorrow", "next week", "3 days", "in 2 weeks", "next Monday at 3pm". Proactively invoke for deadlines, schedules, time-sensitive tasks, week numbers, or any date/time reference.

Searches the NIST NVD database for CVE vulnerabilities using API 2.0. Returns CVE details, CVSS scores, affected software, and references. Use when user asks about "CVE", "vulnerability database", "NIST", "NVD", "security advisory", "CVE-2024", "CVE-2023", "脆弱性", "セキュリティアドバイザリ", or wants to find known vulnerabilities for specific software.

Google Apps Script documentation, guides, and API reference for automating Google Workspace applications

Deep exploration from a key paper. Triggers: 這篇論文的相關研究, 誰引用這篇, 類似文章, related articles, citation tree, paper exploration

Provide accurate, evidence-based answers by referencing sources from documents, textbooks, or research papers. Use when user asks for factual or source-backed responses.

Conduct comprehensive academic research using OpenAlex, PDF extraction, paper search MCPs, and web search. Always produces comprehensive reports with 5+ evidence cards covering conflicting ideas and best approaches. Integrates academic papers (high weight) and non-academic sources (blogs, docs - lower weight but valuable for SOTA). Use when: (1) Researching software architecture patterns, (2) Finding academic papers on technical topics, (3) Conducting literature reviews, (4) Analyzing research papers for evidence-based decisions, (5) Building evidence cards from papers, (6) Finding related works and citations, or (7) When you need grounded, paper-backed technical recommendations. Triggers: research, find papers, literature review, evidence-based, academic research, compare approaches, what does research say, find studies on, search for papers about.

Skriptoteket-specific brutalist/academic UI design. Use for Vue/Vite SPA and SSR templates when you want grid-based layouts, systematic typography, and high-contrast “academic” aesthetics, while staying compatible with Skriptoteket’s pure-CSS + HuleEdu token stack (no Tailwind).

Use this skill to query your Google NotebookLM notebooks directly from Claude Code for source-grounded, citation-backed answers from Gemini. Browser automation, library management, persistent auth. Drastically reduced hallucinations through document-only responses.

Live testing and validation of production research API for strategy optimization loops

Chaos experiment design methodology. Hypothesis formation, success criteria definition, blast radius control, validation patterns, and SLI monitoring for effective chaos engineering.

Enforces online documentation research before any technical implementation. Use when implementing features to ensure code follows current best practices by researching official documentation first.

Validate images against tacosdedatos illustration style guide. Use this skill when reviewing generated images, checking uploaded images for brand consistency, providing quality feedback on visual assets, or deciding if an image is ready for publication. Returns pass/fail with specific actionable feedback.

Create bold, high-end, production-grade frontend interfaces with the mindset of a professional UI/UX designer and frontend engineer. This skill is used when the user asks to design or redesign web interfaces (components, pages, dashboards, or applications) that must feel intentional, distinctive, and non-generic. The model should actively draw inspiration from a wide range of real-world design references (e.g. modern product interfaces, editorial layouts, design systems, experimental web design, trends seen on platforms like Pinterest, Awwwards, Dribbble), without copying any single source. The output must be real, implementation-ready code, but should avoid rigid, template-like, or overly symmetric “AI-looking” components. Layouts, spacing, typography, hierarchy, and interaction patterns should feel designed, not generated. Preference is given to strong visual direction, thoughtful UX decisions, and controlled experimentation over safe or conventional UI patterns.

Analyze therapy session transcripts or journal entries. Identifies cognitive patterns, emotional themes, and tracks progress over time. Automatically references recent analyses for context. Use for session analysis, journal reflection analysis, or pattern identification.

Synthesize claims across multiple sources to identify consensus, disagreements, and emerging narratives on AI research topics. Use when you have claims from both lab researchers and critics on the same topic and need to understand where they agree, disagree, and what the overall hype level is.

ANYTHING related to SolidWorks. Writes, modifies, and debugs C# code that interacts with SolidWorks. Use when working with .cs or .csproj files that (will) reference SolidWorks SDK, SolidWorks.Interop assemblies, COM interop with SolidWorks.