657건 · 관련도순
Develop and fix code by first writing a failing test, then making it pass and improving the implementation. The skill follows the project's testing tools and checks both the intended behavior and existing functionality.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Find biological pathways and functions enriched in gene lists or ranked gene data. Choose an appropriate statistical method, align gene identifiers, define comparison backgrounds, and turn results into interpretable tables and plots with multiple-testing corrections.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Refactor JavaScript using ES6+ features to make code easier to read and maintain. Covers asynchronous operations with async/await, modules, and functional patterns that transform data without changing the original values.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Create a functional application prototype from an initial idea. The workflow covers requirements, technology choices, plan approval, project setup, implementation, visual assets where needed, build verification, and instructions for starting the result.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Coordinate AI agents acting as company executives through shared question and response formats. The skill defines limits on repeated calls, independent analysis, peer checks, conflict reporting, and decision records to support cross-functional reviews and board meetings.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Review a pull request, a proposed code change, for code that can be removed or simplified. Consider product decisions, final functionality, and whether rare edge cases have led to unnecessary complexity.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Monadic types for Golang using samber/mo — Option, Result, Either, Future, IO, Task, and State types for type-safe nullable values, error handling, and functional composition with pipeline sub-packages. Apply when using or adopting samber/mo, when the codebase imports `github.com/samber/mo`, or when considering functional programming patterns as a safety design for Golang. Not for nil-safety and zero-value design without this library (→ See `samber/cc-skills-golang@golang-safety` skill), nor for native error wrapping with fmt.Errorf, errors.Is and errors.As (→ See `samber/cc-skills-golang@golang-error-handling` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Functional programming helpers for Golang using samber/lo — 500+ type-safe generic functions for slices, maps, channels, strings, math, tuples, and concurrency (Map, Filter, Reduce, GroupBy, Chunk, Flatten, Find, Uniq, etc.). Core immutable package (lo), concurrent variants (lo/parallel aka lop), in-place mutations (lo/mutable aka lom), lazy iterators (lo/it aka loi for Go 1.23+), and experimental SIMD (lo/exp/simd). Apply when using or adopting samber/lo, when the codebase imports github.com/samber/lo, or when implementing functional-style data transformations in Go. Not for streaming pipelines (→ See `samber/cc-skills-golang@golang-samber-ro` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Idiomatic Golang design patterns — functional options, constructor APIs, `init()` and global-state avoidance, enums, panic vs error decisions, resource management and lifecycle, graceful shutdown, timeouts and retries, streaming and iterators, and architecture styles (clean, hexagonal, DDD, flat). Apply when choosing between architectural patterns, implementing functional options, designing constructor APIs, setting up graceful shutdown, applying resilience patterns, or asking which idiomatic Go pattern fits a specific problem. Not for wiring a DI container or comparing DI libraries (→ See `samber/cc-skills-golang@golang-dependency-injection` skill), nor for error wrapping, `errors.Is`/`As`, or logging mechanics (→ See `samber/cc-skills-golang@golang-error-handling` skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Identify likely causal variants within GWAS loci using SuSiE for sum of single effects regression and FINEMAP for shotgun stochastic search. Computes posterior inclusion probabilities and credible sets to prioritize variants for functional follow-up. Use when narrowing GWAS association signals to candidate causal variants or building credible sets for functional validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Apply lean thinking to UX: hypothesis-driven design, collaborative sketching, and rapid experiments instead of heavy deliverables. Use when the user mentions "Lean UX", "design hypothesis", "outcome over output", "design studio method", "assumption mapping", "lightweight research", "too much design documentation", or "get the team designing together". Also trigger when reducing design-documentation overhead, getting cross-functional teams to co-design, or running fast usability experiments. Covers hypothesis statements, MVPs for UX, and cross-functional collaboration. For Build-Measure-Learn, see lean-startup. For usability audits, see ux-heuristics.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Plan tests for an API endpoint or service — functional, negative, and contract. Use when asked to test an API, write API test cases, plan REST/GraphQL endpoint testing, or validate an API contract. Produces an API test plan — per-endpoint cases (status codes, schema, auth, validation, errors), boundary/negative cases, contract checks, and non-functional notes — so the API is verified beyond the happy 200.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Estimates SNP heritability and partitions it across functional annotations, cell types, and loci from GWAS summary statistics or individual-level genotypes. Implements LDSC, stratified LDSC with the baseline-LD model, Finucane 2018 cell-type prioritization, LDAK SumHer, HDL, HESS local heritability, BOLT-REML, GCTA-GREML, graphREML, and Popcorn cross-population genetic correlation. Use when computing total h2_SNP from summary stats, partitioning heritability across functional categories, prioritizing trait-relevant tissues or cell types from ENCODE/Roadmap chromatin marks, reconciling LDSC vs LDAK enrichment estimates, computing local heritability with HESS, estimating genetic correlation between traits, or producing publication-grade enrichment with calibrated sensitivity to model assumptions.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Cross-functional organizational health check scoring 8 dimensions on a traffic-light scale. Use when assessing company health, preparing for board reviews, identifying at-risk functions, or diagnosing cross-functional problems.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
a skill that determines whether a given subject matter qualifies for copyright protection under EU law by applying the Cofemel two-step test (concept of work + originality), grounded in fifteen CJEU judgments (including the most recent Mio/Konektra and Calinescu) and the four EU directive provisions on originality. It argues from one of two positions: pro-rightsholder (establishing that the work is original) or pro-alleged-infringer (contesting work status or originality via the four exclusion grounds — technical function, rule-dictated outcome, sweat of the brow, idea/functionality). It includes sector-specific modules for photography, software/GUI, sporting events, databases, applied art, functional texts, derivative works/critical editions, and multimedia works.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This packages provides C++ header files for developers wishing to create R packages that processes BAM files. ompBAM automates file access, memory management, and handling of multiple threads 'behind the scenes', so developers can focus on creating domain-specific functionality. The included vignette contains detailed documentation of this API, including quick-start instructions to create a new ompBAM-based package, and step-by-step explanation of the functionality behind the example packaged in
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
This package supports functional characteristics of both coding and non-coding genomics data for thousands of species with up-to-date gene annotation. It provides a univeral interface for gene functional annotation from a variety of sources
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Standardize SRS and FRS specifications for technical behavior, interfaces, data contracts, quality constraints, and verification mapping. Use when writing SRS, functional specification, system behavior requirements, API/data contracts, or non-functional thresholds.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
SKILL.md simplification with functional integrity verification. Analyze redundancy, optimize content, check no functionality lost. Triggers on "simplify skill", "optimize skill", "skill-simplify".
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Write, review, or modernize F# code in .NET repositories with functional-first design, algebraic data types, pattern matching, pipelines, async workflows, project ordering, and C# interop. USE FOR: F# .fs/.fsproj code; discriminated unions, records, options, results, pattern matching, computation expressions, or functional domain modeling; strongly typed AI-generated .NET code. DO NOT USE FOR: C# language modernization; FSI-only exploratory scripts with no project changes. INVOKES: inspect .fsproj file order and SDK settings, edit F# source and project files, and run dotnet build/test or dotnet fsi validation commands when changes are made.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when you need to add or evaluate Maven dependencies that improve code quality or domain modeling — including nullness annotations (JSpecify), static analysis (Error Prone + NullAway), functional programming (VAVR), architecture testing (ArchUnit), or money and currency support (JavaMoney) — and want a consultative, question-driven approach that adds only what you actually need. This should trigger for requests such as Add Maven dependencies; Add JSpecify nullness dependencies; Add Error Prone NullAway dependencies; Add VAVR functional dependencies; Add ArchUnit architecture testing dependencies; Add JavaMoney dependencies. Part of Plinth Toolkit
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create lane for fskill-creator; normalizes user briefs into create_context for the main skill to generate functional skills.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Extract abstract mathematical models from functional code (Haskell, OCaml, F#) for formal reasoning in Isabelle/HOL. Use when users need to: (1) Convert functional programs to Isabelle definitions, (2) Extract high-level algorithm essence from implementation code, (3) Generate formal specifications and properties from code, (4) Create verification-ready models that capture mathematical properties while abstracting away implementation details. Focuses on structural recursion, algebraic data types, higher-order functions, and invariant extraction.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Hardware verification tool for checking functional equivalence between two RTL designs (Verilog). Use when users need to: (1) Verify if two RTL versions are functionally equivalent, (2) Compare original vs. refactored RTL code, (3) Validate design changes or optimizations, (4) Identify semantic vs. cosmetic differences, (5) Generate counterexamples for non-equivalent designs. Analyzes interface alignment, state variables, logic differences, and produces detailed equivalence verdicts with plain language explanations. Particularly effective for design verification, code reviews, and regression testing of RTL modifications.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.