'cycles' 검색 결과

Validates DAG structures, performs topological sorting, detects cycles, and resolves dependency conflicts. Uses Kahn's algorithm for optimal execution ordering. Activate on 'resolve dependencies', 'topological sort', 'cycle detection', 'dependency order', 'validate dag'. NOT for building DAGs (use dag-graph-builder) or scheduling execution (use dag-task-scheduler).

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

Prioritizes rare-disease variants from trio/quad WES/WGS with de novo (DeNovoGear, Triodenovo), compound-heterozygous phasing (WhatsHap), mosaic VAF tiering, phenotype-driven ranking (Exomiser, Phen2Gene, AMELIE), ClinGen gene-disease validity gating, and ACMG SF v3.2 secondary findings reporting. Use when running diagnostic exome / genome pipelines, identifying candidate Mendelian disease genes, screening for incidental findings, or auditing VUS reclassification cycles. The ACMG/AMP classification framework (PVS1 decision tree, Pejaver PP3/BP4 calibration, Tavtigian point system) is in clinical-databases/acmg-classification.

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

Resolve the architecture of focal oncogene amplifications — extrachromosomal DNA (ecDNA), breakage-fusion-bridge (BFB) cycles, homogeneously staining regions (HSR), and linear amplification — from whole-genome sequencing with AmpliconArchitect, the AmpliconSuite pipeline, and AmpliconClassifier. Covers copy-number seed selection, breakpoint-graph reconstruction, balanced-flow optimization, ecDNA classification, and the limits of depth-only amplification calls. Use when a focal amplification needs structural characterization, when distinguishing ecDNA from chromosomal amplification, suspecting ecDNA-driven oncogene amplification or therapy resistance, or selecting copy-number seeds for amplicon reconstruction.

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

Track complex, multi-session work with dependency graphs using bd (beads) issue tracker. Use when work spans multiple sessions, has complex dependencies, or requires persistent context across compaction cycles. For simple single-session linear tasks, TodoWrite remains appropriate.

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

Worker-Reviewer iterative pipeline for quality-critical code with review cycles

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

Vehicle data through Openapi Automotive - look up cars, motorcycles, insurance and MOT status by license plate across Italy, UK, Germany, France, Spain, Portugal. Use for vehicle technical data and insurance validity checks by plate.

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

Derive an execution roadmap from a project's vision/spec docs by first principles, then diff that fresh derivation against the existing roadmap to prove the task ORDER is correct. Use this whenever the user wants to review, validate, re-derive, or sanity-check an execution roadmap or delivery plan; asks whether the tasks/epics are "in the right order"; suspects a task is scheduled before its prerequisite (a producer-after-consumer / dependency-inversion error like "OpenAPI after the web client that consumes it", OR a cross-cutting inherited default like observability/auth/tenancy scheduled after the feature work that inherits it — a seam-after-consumer error); wants to find missing tasks, circular dependencies, or over-fragmented epics; or wants to compact a plan to raise velocity. Also trigger on "review the roadmap", "re-derive the plan from the spec", "is this the right build order", "check the dependency graph of our epics", "which task should come first". It reads the vision + spec corpus, decomposes actors → use-cases → modules → epics → typed tasks, identifies cross-cutting inherited-default seams, builds a real dependency graph with hard + soft (seam) edges (deterministic helper), breaks cycles, topologically orders, compacts, and emits a derived roadmap PLUS a delta report against the current one — it never blindly overwrites a hand-crafted roadmap.

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

/cs:aims-audit <scope> — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation. Use before certification stage 1, before annual internal audit cycles, or when onboarding a new AI system into an existing AIMS.

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

Expert-level aerospace propulsion covering gas turbine engines, rocket propulsion, thermodynamic cycles, nozzle design, and propellant chemistry.

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

Expert-level engineering thermodynamics covering laws of thermodynamics, thermodynamic cycles, steam power plants, refrigeration, gas dynamics, and combustion.

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

Expert-level thermochemistry knowledge. Use when working with enthalpy, calorimetry, Hess's law, bond energies, heat of formation, heat of combustion, heat capacity, thermodynamic cycles, or reaction energetics. Also use when the user mentions 'enthalpy', 'Hess law', 'calorimetry', 'heat of formation', 'heat of combustion', 'bond energy', 'specific heat', 'calorimeter', 'endothermic', 'exothermic', 'standard state', or 'thermodynamic cycle'.

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

Expert-level thermodynamics knowledge. Use when working with heat, temperature, entropy, thermodynamic laws, heat engines, refrigerators, phase transitions, statistical mechanics, or thermodynamic cycles. Also use when the user mentions 'entropy', 'enthalpy', 'Carnot', 'heat engine', 'thermodynamic cycle', 'ideal gas', 'phase transition', 'Gibbs free energy', 'specific heat', 'thermal equilibrium', or 'second law'.

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

When shaping a non-trivial migration — rollout phases, dual-write windows, cutover sequencing, deprecation cycles — hands off to the framework-specific migration skill for DDL once locked.

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

Review+fix protocol with optional pre-core git diff review and safety guardrails (unsoundness, invariants, footguns, incidental complexity). Use when prompts say "/tw-fix this PR", "fix current branch", "fix this diff", "repair CI red", or "apply a minimal patch", and when crash/corruption/invariant-break issues need correction with a validation signal. Stop only after self-review exhausts actionable changes, each full cycle reaches post-self-review rerun plus terminal diff-review closure, and two consecutive zero-edit full cycles are clean.

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

Manage agent-skill lifecycles across local, global, project, Skill Hub, skills.sh, GitHub, plugin-cache, and system roots. Use when searching, recommending, installing, updating, upgrading, syncing, merging, auditing, deduplicating, cleaning, packaging, publishing, or validating skills; choosing project versus global scope; verifying upstream source, stars, or installs; or working with skill-upgrade, check_upstreams.ps1, sync-pull/push, junctions, skills-lock.json, or skill-upstreams.json. Do not use for ordinary software-package upgrades or non-skill file cleanup.

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

Review a PR end-to-end with CI checks, fix cycles, and optional auto-merge. Use for PR review, cleanup, or readiness checks. Don't use for creating PRs, raw issue analysis, or non-PR code review.

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

Implement or extend a CPU architecture, processor variant, instruction set, addressing modes, registers, interrupts, bus transactions, disassembly, timing, and processor tests in EMULATORS. Use when adding a processor not yet emulated, deriving a CPU from F6500, FZ80, or another family, filling missing opcodes, correcting instruction semantics or cycles, or creating exhaustive instruction and interrupt tests.

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

Parse and interpret execution debug logs generated by the EMULATORS framework, correlating each CPU instruction block with its VIC-II, CIA, SID, interrupt, stop, raster, badline, and memory-access cycles. Use for .LOG traces from EMULATORS when diagnosing cycle timing, raster effects, CPU stalls, IRQ/NMI entry, instruction/chip synchronization, or when reconstructing execution around a PC or mapped register.

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

AID Memory System for session feedback, learning cycles, and skill improvement. Manages state, feedback collection, and improvement analysis. Load for /aid-init, /aid-start, /aid-status, /aid-end, /aid-improve, /aid-memory, /aid-reset.

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

Track design iteration history and apply consistent styling decisions across revision cycles. Use when handling follow-up change requests that reference previous design decisions (e.g., '前回も色で良いんだけど', 'same style as before', 'like we discussed').

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

/cs:aims-audit <scope> — ISO/IEC 42001 AIMS internal-audit 6-question forcing interrogation. Use before certification stage 1, before annual internal audit cycles, or when onboarding a new AI system into an existing AIMS.

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

Verify Stripe subscription billing cycles using a test clock. Use when you need to simulate time passing to trigger subscription renewals, recurring invoices, or to confirm that the next billing date generates the expected charge in Stripe test mode.

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

Load when the user asks to create, find, update, assign, label, prioritize, transition, or organize ISLAMU Event issues/cycles/modules in Plane via MCP; not for local todo lists or implementation-plan markdown.

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

Manage Linear issues from the command line using the linear CLI. Use when creating, updating, listing, or searching Linear issues, managing projects, cycles, milestones, or initiatives, or making Linear API calls.

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