nuxt-devtools-kit-skilld
ALWAYS use when writing code importing "@nuxt/devtools-kit". Consult for debugging, best practices, or modifying @nuxt/devtools-kit, nuxt/devtools-kit, nuxt devtools-kit, nuxt devtools kit, devtools.
ALWAYS use when writing code importing "@nuxt/devtools-kit". Consult for debugging, best practices, or modifying @nuxt/devtools-kit, nuxt/devtools-kit, nuxt devtools-kit, nuxt devtools kit, devtools.
Creates new Agent Skills for Claude Code following best practices and documentation. Use when the user wants to create a new skill, extend Claude's capabilities, or package domain expertise into a reusable skill.
Extract methodologies from documents or examples to create executable skills
Search and recommend Claude Code skills from trusted marketplaces
Create skills by learning from high-quality GitHub projects
Decision-grade workflow for synthesizing a source set into clear findings, contradictions, confidence markers, gaps, and next questions. Use for prompts like "synthesize these sources", "turn this research into a brief", "what are the key findings", or "where do these sources disagree". Best when you have a research question, a defined audience, and a set of source materials. Optional Open Brain search and capture can pull prior context and store the final synthesis.
LaTeX submission pipeline: templates, local build (latexmk), bibliography (bibtex/biber), lint (chktex), formatting (latexindent), CI build (GitHub Actions), and submission zip packaging.
Build slide decks and presentations for research talks. Use this for making PowerPoint slides, conference presentations, seminar talks, research presentations, thesis defense slides, or any scientific talk. Provides slide structure, design templates, timing guidance, and visual validation. Works with PowerPoint and LaTeX Beamer.
Build research slides with text-first source (Slidev/Marp/Reveal/Quarto) and reproducible export (PDF). Includes structure, figure reuse rules, and quality checklist for top-tier scientific presentations.
Discover codebase patterns, conventions, and unwritten rules before making changes. Use when implementing features, fixing bugs, or refactoring code.
Systematic research idea discovery through paper combination matrix. Use when finding research ideas, evaluating paper combinations, building unified theoretical frameworks, or generating code skeletons from combined methods.
Treat manuscripts as software: version control, reproducible builds, figure pipelines, CI, and structured repo layout. Helps teams avoid 'final_v7' chaos and ensures submission-ready artifacts.
Structured clarification workflow for underspecified requirements. Use before planning to resolve ambiguities through coverage-based questioning. Records answers in spec clarifications section.
Write comprehensive clinical reports including case reports (CARE guidelines), diagnostic reports (radiology/pathology/lab), clinical trial reports (ICH-E3, SAE, CSR), and patient documentation (SOAP, H&P, discharge summaries). Full support with templates, regulatory compliance (HIPAA, FDA, ICH-GCP), and validation tools.
Compatibility alias for OpenAI platform documentation guidance. Delegate to the canonical local `openai-docs` payload while preserving route compatibility.
Generate technical implementation plans from feature specifications. Use after creating a spec to define architecture, tech stack, and implementation phases. Creates plan.md with detailed technical design.
Create or update feature specifications from natural language descriptions. Use when starting new features or refining requirements. Generates spec.md with user stories, functional requirements, and acceptance criteria following spec-driven development methodology.
Update project documentation after code changes. Maintains the 4 core ai-context files (spec, project-structure, progress, deployment-infrastructure) and CLAUDE.md. Use after completing features, refactors, or any changes that affect project structure, capabilities, or status. Also creates initial documentation if files don't exist yet.
Add KDoc documentation to Kotlin public API. Use whenever the user asks to document Kotlin code, add KDoc, generate API docs, mentions undocumented public declarations, or wants to improve existing documentation. Also trigger when the user says 'add docs', 'document this class/file/module', 'write KDoc', or asks about missing documentation in Kotlin code.
Acquires visual assets from multiple sources: web image search, live website screenshots via Playwright, and user-provided files. Organizes assets in the squad's reference folder.
Guides creation and maintenance of best-practice files for the Opensquad best-practices library. Handles format validation, cross-references, versioning, and catalog consistency.
Read and write Obsidian vault files, manage wiki-links, process markdown with YAML frontmatter. Use when working with vault file operations, creating notes, or managing links.