130건 · 관련도순
Translate Python programs to equivalent Lean4 code while preserving semantics and ensuring type safety. Use when users ask to convert, translate, or port Python code to Lean4, or when they need to verify Python algorithms using Lean4's theorem proving capabilities. Handles functions, classes, data structures, control flow, and ensures the generated Lean4 code is well-typed, executable, and can successfully run.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
TanStack Router type-safe file-based routing for React. Use for SPAs, TanStack Query integration, Cloudflare Workers, or encountering devtools, type safety, loader, Vite bundling errors.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Adding JSDoc/TSDoc, updating READMEs, replacing any types with proper definitions, and adding high-value comments to complex logic. Use for documentation gaps or type safety.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Prioritize drug targets from a ranked gene list (e.g., scRNA-seq DE output) by orchestrating parallel API queries against UniProt, OpenTargets (with integrated DepMap CRISPR essentiality + gnomAD constraint), PubMed, the Human Protein Atlas (HPA), and ChEMBL tool compounds, then re-ranking by a composite score combining protein localization, druggability, disease genetics, tissue specificity (safety), focus-cell-type expression, CRISPR essentiality, LoF safety constraint, and research maturity. Use whenever the user wants to filter, triage, prioritize, or "do due diligence" on a list of candidate genes for drug discovery, especially after a DE / DEG analysis when they say things like "which of these should I follow up on", "filter for druggable targets", "make a target dossier", "rank these for tractability", "annotate these genes for druggability", or "build a target report". Trigger even when the user says just "filter these candidate genes" or hands over a CSV from a DE pipeline.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews Rust FFI code for type safety, memory layout compatibility, string handling, callback patterns, and unsafe boundary correctness. Use when reviewing extern blocks, #[repr(C)] types, bindgen output, or code calling C/C++ libraries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews Python code for type safety, async patterns, error handling, and common mistakes. Use when reviewing .py files, checking type hints, async/await usage, or exception handling.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Reviews Python code across type safety, error handling, security, performance, modern patterns, design clarity, typed-boundary compliance, test quality, and documentation. Use when performing code review, PR review, pre-merge quality checks, or assessing Python for security vulnerabilities, bare except clauses, Any usage outside boundaries, or missing input validation at system boundaries.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Validate Python code quality with formatting, type checking, linting, and security analysis. Use for Python codebases to ensure PEP 8 compliance, type safety, and code quality.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Suggests that clinicians continue CSII in hospitalized patients with type 1 or type 2 diabetes when the institution has clear protocols for evaluating pump candidates and appropriate monitoring and safety procedures. Trigger phrases include: 'Admitted patient on pump, check hospital pump policy' and 'Inpatient with diabetes using pump, verify institutional guidelines'.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Expert-level nuclear energy covering fission reactor physics, reactor types, safety systems, nuclear fuel cycle, waste management, and advanced reactor concepts.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Garanta estrutura válida de JSON/XML/código durante a geração, use modelos Pydantic para outputs type-safe, suporte modelos locais (Transformers, vLLM) e maximize velocidade de inferência com Outlines - biblioteca de geração estruturada da dottxt.ai
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Core technical, safety, and maintainability rules for codebase edits. Trigger when: - Writing code, refactoring, modifying files, or creating unit tests. - Proposing commits, reviewing git history, or auditing code quality. - Modifying files in any programming language (e.g. *.go, *.rs, *.py, *.ts, *.js, *.c, *.cpp). - Prompt contains keywords: refactor, build, compile, lint, test, git, commit, rule priority, type safety, error handling, defensive programming.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Guarantee valid JSON/XML/code structure during generation, use Pydantic models for type-safe outputs, support local models (Transformers, vLLM), and maximize inference speed with Outlines - dottxt.ai's structured generation library
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
C++ 코드 구현·검토·리팩터링에서 타입 사용, 메모리 관리, 예외 처리와 동시성을 점검합니다. 표준 지침에 따라 안전성과 코딩 방식의 일관성을 정리합니다.
Implement controlled retries and request throttling for external APIs. Covers retryable errors, provider-specified waiting times, increasing delays with random variation, retry limits, and checks that repeating a request will not cause unintended duplicate changes.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Provides guidance for managing Twitter/X content, including weekly plans, posts, threads, replies, and performance analysis. Includes API v2 examples and review queue templates to help organize publishing and maintain a consistent brand voice.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Audit Claude Code and Codex hooks, actions triggered by agent events. Check commands, trigger conditions, blocking behavior, and timeouts to identify why hooks fail to run, fail to block actions, or delay the agent.
한국어 요약은 준비 중입니다. 영어 요약을 표시하고 있습니다.
Golang refactoring — safe, at-scale restructuring of existing Go code: a coverage-adaptive safety net, behavior-preserving transforms (gopls Rename/Extract, `gofmt -r`, `gopatch`), the Fowler catalog mapped to Go, breaking import cycles, and small stacked PRs. Apply when a function or type has grown too large, a code smell blocks a feature, or the user asks to refactor Go code — also for renaming at scale, extracting functions or interfaces, moving code between packages, or planning a multi-step refactor. Target styles owned elsewhere → See `samber/cc-skills-golang@golang-naming` (renames), `samber/cc-skills-golang@golang-project-layout` (splits), `samber/cc-skills-golang@golang-modernize` (idioms), `samber/cc-skills-golang@golang-code-style` (control flow), `samber/cc-skills-golang@golang-design-patterns` (patterns/DI).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user asks to "review this influencer content" or "check if this post meets brand guidelines"; runs the typed STAR pre-publish gate, scores Trust and Appeal on the deliverable, folds in the creator Suitability read, computes the profile-weighted SQS, checks the disclosure/claim/brand-safety and fraud/fake-engagement vetoes, and writes constructive revision feedback. Not for drafting the brief — use brief-generator; not for partnership terms — use contract-helper. 达人内容审核/发布前质检
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Builds Python 3.11+ applications with type safety, async programming, robust error handling, mypy strict mode, pytest suites, and code validation with black and ruff.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Dart 3.x language feature standards: null safety, records, sealed classes, switch pattern matching, extensions, and async/await. Use when using !, ?., ??, late, sealed classes, record types, switch expressions, or async patterns — and before introducing any new Dart 3.x construct to confirm the modern idiomatic approach.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Design, implement, optimize, and review SIMD code in .NET. USE FOR: vectorizing scalar loops with TensorPrimitives, Vector64/128/256/512, or platform hardware intrinsics; reviewing existing SIMD code, including the generic Vector type, for contract equivalence, tail handling, memory safety, portability, fallbacks, and measured performance. DO NOT USE FOR: performance work unrelated to SIMD or vectorization.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Run targeted linting, formatting, and code quality checks on modified files. Use this to validate code style, type safety, security, and other quality metrics before committing. Supports running all checks or targeting specific checks on specific files for efficient validation.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when auditing source code for vulnerabilities — drive CodeQL/Semgrep/Joern to taint untrusted data source-to-sink across injection, memory safety, deserialization/prototype-pollution, secrets/crypto/authz/race, and supply-chain risks
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.