'solver' 검색 결과

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Drafts one knowledge article or known-error article from a resolved incident or ticket thread: symptoms as reported, environment, cause exactly as the resolver stated it, resolution steps as performed, workaround with its limits, verification, things tried without effect, related records, keywords and proposed metadata, every statement traced to a ticket note or marked UNKNOWN, with a redaction log and a question list for the knowledge owner. Never decides a root cause, adds a step or publishes. Use when the user asks to "write a KB article from this ticket", "turn this resolved incident into a knowledge article", "draft a known error record for this", "document the fix we just did" or "make this thread into a how-to for the service desk". Do not use for a procedure the team will execute (runbook, operating procedure, playbook), use runbook-drafter instead; for a post-incident review, use incident-postmortem-drafter. Drafts for human review; never approves, authorises or signs off.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Resolve App Store Connect IDs (apps, builds, versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Resolve App Store Connect IDs (apps, builds, app and digital-goods versions, groups, testers) from human-friendly names using asc. Use when commands require IDs.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Capture The Flag challenge solving — reverse engineering, steganography, forensics, crypto, web exploitation, binary exploitation, OSINT. Pattern recipes for fast triage and direct exploitation.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Istruzioni cognitive avanzate per risolvere compiti complessi, includendo Chain of Thought e revisioni Red Team.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Solve partial differential equations — finite differences, spectral methods, and physics-informed neural networks (PINNs via DeepXDE). Supports 1D/2D/3D, steady/transient, linear/nonlinear PDEs with Dirichlet, Neumann, and periodic boundary conditions.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Solve ordinary differential equations (initial and boundary value problems). Supports stiff/non-stiff systems, event detection, Hamiltonian/symplectic integration, parameter sweeps, and phase space analysis. Use for any ODE system in physics, engineering, or applied math.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Computational fluid dynamics — Navier-Stokes solvers, lid-driven cavity, channel flow, vortex methods, turbulence statistics, drag/lift computation. Spectral and finite-difference methods for incompressible and compressible flows.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

React Hook Form v7 (RHF、非制御フォームライブラリ) リファレンス。別名 rhf / React-Hook-Form。 useForm, register, handleSubmit, watch, setValue, getValues, getErrors, reset、 Controller, useFieldArray / FieldArray, formState / FormState, ErrorMessage、 resolver (Zod / Yup / Joi)、バリデーション、Server Actions / useActionState、 DevTools (@hookform/devtools)、TypeScript 型。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

CadQuery (Python 製 3D CAD スクリプティングライブラリ) リファレンス。 Workplane API (lineTo / extrude / revolve / sweep / loft / fillet / chamfer / shell)、 Sketch API、Assemblies (Constraint solver)、Free Function API (hollow / prism / draft / offset2D, History)、 Selectors、Shape / Vertex / Edge / Wire / Face / Shell / Solid、 Import / Export (STEP / DXF / STL / glTF / SVG)、Visualization (VTK, cadquery.fig 非ブロッキング, Jupyter)、CQGI。

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Calls HLA class I and class II alleles at 2/4/6/8-field resolution from WGS/WES/RNA-seq/long-read data using OptiType, HLA-LA, T1K, Polysolver, HLA-HD, arcasHLA, StarPhase, or HIBAG imputation. Use when typing for HSCT, solid-organ transplant, neoantigen prediction, PGx screening (B*57:01, B*15:02, etc.), or disease-association studies, with reconciliation across tools and IPD-IMGT/HLA version mismatch handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Use when the user hands over a GitHub issue to be delivered end to end — 'resolver a issue #42', 'loop na issue 42', 'deliver issue https://github.com/o/r/issues/42' — or when an Orca worker preamble dispatches `feat-loop #N`. Turns the issue into a plan, executes it, reviews the result and runs at most 2 fix cycles until APPROVED, then opens a pull request that closes the issue. Never merges. Do NOT use without an issue (feat-feature / feat-quick), to only plan (feat-feature), to only review (feat-review) or to execute an existing plan (feat-exec).

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Resolve the current user prompt into an atm.taskIntent.v1 proposal before next-action routing.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Calls HLA class I and class II alleles at 2/4/6/8-field resolution from WGS/WES/RNA-seq/long-read data using OptiType, HLA-LA, T1K, Polysolver, HLA-HD, arcasHLA, StarPhase, or HIBAG imputation. Use when typing for HSCT, solid-organ transplant, neoantigen prediction, PGx screening (B*57:01, B*15:02, etc.), or disease-association studies, with reconciliation across tools and IPD-IMGT/HLA version mismatch handling.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Validates typed DAG dependency declarations, returns Kahn linear extensions or generations and residual cycle witnesses, and identifies changed consumers for revalidation. NOT for constructing graphs, scheduling resource capacity, granting effects, or executing nodes.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Render mathematically-faithful Turkish marbling (Ebru) and paper-marbling with closed-form coordinate-deformation maps — a drop is a radial outward push, a comb/tine is a decaying shear, all composed as homeomorphisms over colored region boundaries. No fluid solver, runs 60fps on a 2D canvas. Use when building a marbling/Ebru toy or generative-art renderer, implementing drop/comb/wave/swirl deformations, scripting traditional patterns (Battal, Gel-Git, Şal, Bülbül Yuvası), keeping combed edges crisp via adaptive resampling, modeling ox-gall shouldering for crisp ring-in-ring drops, or exporting high-DPI marbled prints. NOT for real fluid / Navier-Stokes simulation, metaball / alpha-blended "smoke" blob effects, raster image-processing filters, or non-marbling generative art.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Migrates legacy AEM (6.x, AMS, on-prem) to AEM as a Cloud Service using BPA CSV or cache, CAM/MCP target discovery, and a one-pattern-per-session workflow. Use for BPA/CAM findings, Cloud Service blockers, or fixes for scheduler, ResourceChangeListener, replication, EventListener, OSGi EventHandler, DAM AssetManager, HTL data-sly-test lint. OSGi configs → Cloud Manager — scan ui.config, .cfg.json, secrets, $[secret:]/$[env:] — agent follows references/osgi-cfg-json-cloud-manager.md when prompted. After BPA/CAM discovery, migration hands off each (pattern, file) pair to the code-assessment skill — code-assessment owns the five pattern guides (scheduler/, resource-change-listener/, replication/, event-migration/, asset-manager/) and the shared references for SCR→DS, ResourceResolver/SLF4J, HTL lint, and prerequisites.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

AEM Cloud Service expert skill for the Asset Manager API (com.day.cq.dam.api.AssetManager). Covers two migration paths — Path A (create/upload, replacing createAssetForBinary/getAssetForBinary/client-facing createAsset with Direct Binary Access via @adobe/aem-upload) and Path B (delete, replacing removeAssetForBinary with in-JVM resolver.delete() + commit or external HTTP Assets API with IMS bearer tokens). Covers IMS authentication, service-user setup with crx delete permissions, asset processing pipeline, common pitfalls (hardcoded credentials, AEM calling its own HTTP API), and composition with replication/event-migration skills.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Hunting skill for sqli vulnerabilities. Built from 12 public bug bounty reports including modern NoSQL injection (Rocket.Chat CVE-2021-22911 MongoDB $regex, Mongoose ORM CVE-2024-53900 $where bypass), modern ORM raw-fragment SQLi (Django CVE-2024-42005, Sequelize GHSA-wrh9-cjv3-2hpw), second-order SOQL injection (HackerOne Salesforce), time-based blind SQLi in GraphQL resolvers, and SQLi on OIDC-proxy backends. Use when hunting SQLi on any target. Dedicated NoSQL operator injection (MongoDB/CouchDB $where/$regex/$ne) is owned by hunt-nosqli — NoSQL appears here only as adjacent ORM/WAF context.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

GraphQL gives clients exactly the data they need - no more, no less. One endpoint, typed schema, introspection. But the flexibility that makes it powerful also makes it dangerous. Without proper controls, clients can craft queries that bring down your server. This skill covers schema design, resolvers, DataLoader for N+1 prevention, federation for microservices, and client integration with Apollo/urql. Key insight: GraphQL is a contract. The schema is the API documentation. Design it carefully.

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.

Review and resolve PR issues with Qodo - get AI-powered code review issues and fix them interactively (GitHub, GitLab, Bitbucket, Azure DevOps)

한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.