659건 · 관련도순
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Space/aerospace mission monitoring: dark command center, amber telemetry on navy, monospace precision. Functional clarity above all. For ops dashboards, build/deploy status, and real-time monitoring.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Raw, anti-design aesthetic inspired by concrete architecture with unadorned elements, jarring layouts, and functional minimalism.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use before any creative work - creating a feature, building a component, adding functionality, or changing behavior - to explore intent and design before implementation
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design precise, production-grade enterprise UI — dashboards, admin panels, SaaS interfaces, and data-heavy applications. Use this skill for professional software interfaces that need Jony Ive-level craft: clean, minimal, functional, with intentional personality. Do NOT use for creative landing pages, marketing sites, or experimental/artistic frontends.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Perform a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the work is functionally complete and needs finishing touches—not when the hierarchy, structure, tone, or technical foundation still need major changes.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for testing code changes in AEM Edge Delivery projects including blocks, scripts, and styles. Use this skill after making code changes and before opening a pull request to validate functionality. Covers unit testing for utilities and logic, browser testing with Playwright, linting, and guidance on what to test and how
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply a Content Driven Development process to AEM Edge Delivery Services development. Use for ALL code changes - new blocks, block modifications, CSS styling, bug fixes, core functionality (scripts.js, styles, etc.), or any JavaScript/CSS work that needs validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guide for implementing code changes in AEM Edge Delivery Services. Handles block development (new or modified), core functionality changes (scripts.js, styles, delayed.js, etc.), or both. Use this skill for all implementation work guided by the content-driven-development workflow.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Refactor code to improve quality while maintaining functionality. Use when you need to improve code structure, eliminate duplication, optimize performance, or enhance maintainability without changing behavior.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Upgrades existing websites and apps to premium quality. Audits current design, identifies generic AI patterns, and applies high-end design standards without breaking functionality. Works with any CSS framework or vanilla CSS.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create a new command file following repo conventions. Use when you need to add a new slash command, create automation workflows, or extend the command library with new functionality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Fix broken or failing functionality through structured reproduction, root-cause analysis, minimal fix, and verification. Load when the user asks to fix a bug, debug an error, resolve an issue, or work on a Linear ticket. Also triggers on "this is broken", "fix this bug", "why is this failing", "debug this", "resolve this error", "what went wrong", or any request to diagnose and fix a problem.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write the executable feature specification — the WHAT and WHY artifact that agents and reviewers treat as source of truth. Owns both /specify and /clarify modes. Load when the user asks to write a feature spec, write a specification, write an executable spec, define functional requirements, capture acceptance criteria as Given/When/Then, or when the spec-driven-development orchestrator routes here. Also triggers on "feature spec", "executable spec", "/specify", "/clarify", "write the spec for this feature", "specification for", "spec-driven", "machine-readable spec". Output: docs/specs/YYYY-MM-DD-<slug>-feature-spec.md. Hard gate: cannot Approve while [NEEDS CLARIFICATION] markers remain.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Toolkit for interacting with and testing local web applications using Playwright. Supports verifying frontend functionality, debugging UI behavior, capturing browser screenshots, and viewing browser logs.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Biopython is a comprehensive set of freely available Python tools for biological computation. It provides functionality for sequence manipulation, file I/O, database access, structural bioinformatics, phylogenetics, and many other bioinformatics tasks.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Astropy is the core Python package for astronomy, providing essential functionality for astronomical research and data analysis.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert patterns for Algolia search implementation, indexing strategies, React InstantSearch, and relevance tuning Use when: adding search to, algolia, instantsearch, search api, search functionality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Assign cell types from marker expression in IMC/MIBI data using clustering (PhenoGraph/FlowSOM/Leiden/Pixie), marker-based probabilistic classifiers (Astir), or image-context CNNs (CellSighter), covering the double-positive segmentation artifact, lineage-vs-state markers, the two spillover types, and why a "cell type" in imaging is conditioned on a segmentation guess. Use when phenotyping segmented IMC cells, choosing clustering vs classification, diagnosing implausible double-positive populations, separating lineage from functional markers, or transferring labels across a cohort.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Quantifies biodiversity from species abundance/incidence tables using Hill numbers (iNEXT) with coverage-based rarefaction-extrapolation (Chao & Jost 2012), asymptotic richness via Chao1/ACE/jackknife as a lower bound, Baselga turnover/nestedness partition with the Podani alternative as sensitivity check, mandatory Hellinger transformation before ordination (Legendre & Gallagher 2001), Faith PD and SES_MPD/SES_MNTD with explicit null-model choice, and Maire 2015 functional-diversity dimensionality optimization. Use when comparing diversity across sites with unequal sampling effort, picking the right richness estimator for singleton-heavy amplicon data, partitioning beta diversity into turnover vs nestedness, reporting Hill-number effective species counts rather than raw entropies, computing SES_MPD with explicit null-model justification, or deciding whether to apply standard metrics to compositional amplicon data. Not for clinical 16S microbiome diversity (see microbiome/diversity-analysis).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Analyzes base-editing screens for variant function. Covers library design (Sanson 2020 GRACE, Hanna 2021 BRCA1/2 SNV scanning, Cuella-Martin 2021), CBE vs ABE chemistry choice (BE3/BE4 vs ABE7.10/ABE8.20/ABE8e), editing-window math (positions 4-8 from PAM-distal end, wider for ABE8e), bystander-edit quantification and the variant-call ambiguity it creates, sgRNA-efficiency filtering before hit calling, indel byproduct interpretation, the substitution-vs-indel diagnostic, variant annotation against ClinVar / COSMIC, and the Broad be-validation-pipeline. Use when designing a BE variant screen, choosing CBE vs ABE for a specific edit, interpreting bystander-confounded hits, distinguishing functional signal from indel artifact, integrating CRISPResso2 output with screen scoring, or deciding BE vs PE for SNV installation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.