'files' 검색 결과

Runs a route through ScenarioRunner's RouteScenario mode (--route / --route-id) with an autonomous agent driving the ego — the same mechanism the CARLA Leaderboard uses, and the only way to reach the ~34 route-only scenario classes (Accident, ParkedObstacle, HazardAtSideLane, InvadingTurn, HardBreakRoute, YieldToEmergencyVehicle, junction and actor-flow scenarios). Inspects route files, lists route ids and their scenarios, and runs one or all of them. Use when the user asks to "run a route", "drive a route with my agent", "run leaderboard scenarios without the leaderboard", or names a route-only scenario type.

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

Installs Scenic, the probabilistic scenario description language, for the CARLA in use — pip installing it into the same interpreter that holds the CARLA client, optionally cloning the upstream repo for the example scenarios the wheel does not ship, and verifying that the `scenic` CLI, the client and Scenic's version-keyed blueprint table all agree. Use when the user asks to "install Scenic", "set up Scenic", "download Scenic", "pip install scenic", wants to run `.scenic` files, or has a Scenic whose model import or blueprint lookup fails.

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

Creates and edits CARLA Leaderboard route files — placing waypoints and scenario trigger points interactively from the spectator camera (route_creator, scenario_creator), visualising an existing route in the simulator (route_displayer), summarising it as a table (route_summarizer), capturing the current weather in route format (weather_creator), sorting scenarios by route position (scenario_orderer) and converting 1.0-format routes to 2.x (route_bridge). Use when the user asks to "make a new route", "add a scenario to a route", "visualise/debug a route", "see what's in this route file", or "convert old leaderboard routes".

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

Refactor a whole documentation page in this repository without losing source-verified behavior facts. Use for page rewrites, splits, reorganizations, or substantial shortening of README sections, docs pages, or instruction files. Do not use for ordinary documentation authoring, targeted corrections, or documentation review; use technical-documentation instead.

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

Write, review, or audit this repository's technical documentation, including README.md, CONTRIBUTING.md, root and scoped AGENTS.md files, docs pages, and documentation drift. Use for source-backed documentation authoring, behavior verification, and cross-surface consistency. Do not use for code review, deslop diff cleanup, or whole-page rewrites, splits, or reorganizations handled by docs-refactor.

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

Upstash サーバーレスデータプラットフォーム (マネージド SaaS の JS SDK)。 @upstash/redis (REST, pipelining, transactions, JSON, Redis Search, VECTOR/Array/Functions コマンド)、 @upstash/ratelimit (Fixed/Sliding Window, Token Bucket, blockUntilReady)、 QStash (publishJSON, schedules, queues, URL Groups, flow-control, DLQ)、 @upstash/vector (upsert, query, ANN, namespace, hybrid/sparse index, embedding models, reranking)、 @upstash/workflow (serve, durable execution, context.run/sleep/call/invoke, waitForEvent, parallel steps, agents)、 Upstash Search (@upstash/search, search, upsert, fetch, range, filtering, reranking, algorithm)、 @upstash/box (サンドボックス, filesystem, git, CDP, browser, network policy, snapshots, custom harness)、 upstash CLI。Rust 製 fandhe-db とは別。

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

Windows アプリ開発 (Windows App SDK / WinRT) のファイル・設定・データ保存リファレンス。 Windows.Storage の StorageFile, StorageFolder, IStorageItem, FileIO, PathIO, CachedFileManager, DataReader, DataWriter, BasicProperties。ApplicationData, ApplicationDataContainer, ApplicationDataCompositeValue のローカル・ローミング設定。 FileOpenPicker, FileSavePicker, FolderPicker, KnownFolders, StorageApplicationPermissions (FutureAccessList / MostRecentlyUsedList)。 JsonObject, JsonArray, XmlDocument, SQLite, EF Core, Microsoft.Data.SqlClient (SQL Server), Cosmos DB, MySQL, MongoDB 接続。

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

Claude Managed Agents (platform.claude.com) リファレンス。Agents / Sessions / Environments API, SSE event streaming, event deltas, session threads, session budgets, multiagent orchestration (subagents, dynamic workflows, workflow runs, advisor), deployments (cron), dreams, vaults, memory stores, self-hosted sandboxes, webhooks, web search / fetch ドメイン制限, secure deployment, permission policies, Agent Skills, MCP connector, user profiles。

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

Claude API (platform.claude.com) の Messages API リファレンス。 streaming (SSE), thinking (adaptive) / preserved thinking / effort, prompt caching, context editing, compaction (on-demand / threshold), structured outputs, Message Batches, token counting, vision / PDF, Files API, citations, embeddings (Voyage AI), errors, rate limits, beta headers, Bedrock / Vertex AI / Foundry 経由アクセス。

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

App Store Connect API 4.5.1 (REST) アプリ配布リファレンス。JWT 認証、API キー作成・失効、 Apps, Builds, Bundle IDs, Bundle ID Capabilities, Certificates, Devices, Provisioning Profiles, Users, User Invitations, Merchant IDs, Pass Type IDs、TestFlight (Beta Groups / Testers)、 Sandbox Testers、App Review, Review Submissions, Customer Reviews, Custom Product Pages, Phased Release、In-App Purchases, Subscriptions, Subscription Groups, App Price Points, Promotional Offers, Win-back Offers, Sales Reports、App Asset Library (screenshots / app previews)、 Webhooks / Webhook Events / Deliveries、Xcode Cloud (Workflows, Build Runs, Artifacts)、 Alternative Distribution (EU マーケットプレイス / Web Distribution)、 Game Center (Achievements, Leaderboards, Challenges)、Analytics / 診断レポート。

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

Turn character reference images into reusable, rigged voxel 3D assets for Blender and Three.js through an imagegen turnaround and user-approval workflow. Use when Codex needs to preserve a character's likeness across front, side, and back views; create or revise Minecraft-like cube-headed models; prevent missing rear hair or clothing; split features between block geometry and face/clothing textures; generate GLB and editable .blend files; add walk/smash-compatible rigid-part pivots; or diagnose why a voxel conversion is not recognizable.

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

Help job seekers use Otameshi Tenshoku to prepare profiles and applications, clarify trial conditions, plan learning visits or paid trial work, and reflect on the experience. Use when a candidate wants to apply for, prepare for, negotiate the scope of, or review an otameshi work experience; do not use to predict whether they will be hired or to judge their aptitude, to state fees, contract terms, or service conditions from memory, or to submit an application, update a profile, or send a message on their behalf. Employer-side requests belong to the employer skills (trial-work-design, trial-listing-draft, applicant-reply and others).

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

Triage a GitHub issue that already has the cc-issue-created label and is assumed ready to start. Inspect the comment history first to decide whether human confirmation is needed (cc-need-human-check, highest priority — reserved for issue-level deadlock, or for confirmation items answer-issue-questions already investigated and explicitly marked unanswerable); otherwise close the issue as not needed, delegate unanswered confirmation items in the last comment or the description to answer-issue-questions (cc-answer-issue-questions), refresh a description stale relative to settled comment-history content (cc-update-issue), turn the issue into an Epic and split it into sub-issues when its work should ship as separate PRs (cc-epic-issue), or move to execution (cc-exec-issue). Any UI-changing issue is routed to the design-first flow (cc-create-ui-design) before execution; the exceptions are an issue whose description already names the .pen design to implement against, and a minor UI change that introduces no new visual decision (no new screen/section, no layout change, no new reusable component, no visual expression outside existing design tokens/components). Design files are never edited in the implementation PR. Dependency checks are out of scope.

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

Builds an interactive HTML dashboard visualizing the Agent Skills ecosystem by fetching live data from github.com/agentskills/agentskills. Use this skill whenever the user wants to explore, research, or visualize Skills architecture, the SKILL.md spec, ecosystem adoption, repo stats, or any Skills intelligence dashboard. Trigger when the user mentions "skills dashboard", "skills ecosystem", "skills architecture overview", "agentskills repo", or wants to analyze how different tools implement Agent Skills. Optimized for Perplexity Computer — Computer fetches all data live, no static files required.

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

Routes memory and retrieval tasks between MemPalace and QMD. Use this skill whenever the user asks WHERE something is in the codebase (route to QMD), WHY something was built a certain way or what was decided (route to MemPalace), or needs BOTH code and historical context (combined). Trigger on phrases like: 'where is X', 'find X in the code', 'search the codebase for X', 'what did we decide about X', 'why does X work this way', 'show me X and why we built it', 'look up X', 'what's in the handoffs about X', 'pull the relevant files for X'. Use proactively whenever a question could benefit from codebase search OR project memory — don't wait for the user to explicitly ask for a search.

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

Conventions to use in Readme files

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

Use when the user is explicitly working with Quarto, .qmd files, _quarto.yml, Quarto projects, or Quarto features such as callouts, cross-references, citations, Mermaid diagrams, extensions, websites, books, presentations, and reports. Also use for explicit migration from or comparison with R Markdown, bookdown, blogdown, xaringan, distill, or Jupyter notebooks to Quarto. Do not use for general R Markdown or related-format questions unless Quarto or migration to Quarto is explicitly mentioned.

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

This skill should be used when working with Python projects that use uv for package and project management. Use this skill for running Python scripts and CLI tools with `uv run`, managing dependencies, creating projects, handling virtual environments, and executing commands within isolated project environments. Essential for projects with pyproject.toml files.

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

Guides agents through scorecards, outcomes, model profiles, and eval suites. Use when running /cc-scorecard or /cc:scorecard, measuring a deliverable, or checking workflow gates with suite-run.

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

Work on album artwork — reading an image's dimensions, and embedding a folder's cover file into the tags of its tracks. Use this whenever a task touches `services/artwork.py`, the cover half of `services/tags.py`, or `scripts/embed_covers.py` / `embed_covers_cron.sh`. Covers why Lyrion shows the embedded artwork and never the folder file, how covers are compared, why images are never re-encoded, and what embedding costs in rewritten files.

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

Performs set operations on genomic intervals - intersect (-wa/-wb/-wo/-wao/-loj/-c/-v/-u), subtract (-A), merge (-d, -c/-o), complement, cluster, multiinter, unionbedg, map, and groupby - with bedtools (CLI) and pybedtools/pyranges/bioframe (Python). Covers the sorted-input contract and the -sorted chromosome-order footgun, reciprocal/fractional overlap (-f/-F/-r/-e) and the A-vs-B asymmetry, -split for spliced/BED12/BAM features, and jaccard/fisher as mechanics only. Use when finding overlapping or unique regions between BED/peak/feature files, building consensus peaksets, removing blacklisted regions, transferring annotation values onto intervals, or computing interval-set similarity; route overlap-significance testing to overlap-significance.

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

Profiles a genome from raw reads BEFORE assembly with a k-mer spectrum (KMC or Jellyfish histogram), then models it with GenomeScope2 to estimate genome size, heterozygosity, repeat content, and ploidy, and Smudgeplot to infer ploidy from heterozygous k-mer pairs (diploid AB vs triploid AAB vs tetraploid AABB). Covers choosing k via Merqury best_k.sh, the k-mer-coverage vs sequencing-coverage confusion, reading het/repeat/contamination/organelle peaks, why noisy ONT must not be used for counting, and how the estimate becomes the NG50 denominator, the Flye -g value, the hifiasm --hom-cov/purge setting, and the 1.5-2x-too-big haplotig sanity check. Use when starting any de novo assembly, deciding whether short reads can work, estimating genome size for an unknown organism, diagnosing ploidy, or sanity-checking an assembly's size against expectation.

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

Load and preprocess imaging mass cytometry (IMC) and MIBI data from raw MCD/TXT through hot-pixel removal, spillover compensation, and variance-stabilizing transformation, covering readimc/steinbock ingestion, NNLS spillover compensation (CATALYST), IMC-Denoise, and the IMC arcsinh-cofactor question. Use when starting analysis from raw MCD files, building per-channel TIFF stacks, compensating channel spillover, choosing an arcsinh cofactor, or preparing single-cell intensities for phenotyping.

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

Reads, queries, and writes bigWig indexed binary signal tracks (coverage, fold-change, conservation, methylation-rate) with pyBigWig (Python) and the UCSC Kent tools (bedGraphToBigWig, bigWigToBedGraph, bigWigInfo, bigWigSummary, bigWigAverageOverBed) and deepTools (multiBigwigSummary, computeMatrix, bigwigCompare). Covers the central trap that a wide query returns a precomputed zoom-level summary (by default the mean, which annihilates narrow peaks) not per-base data, when exact=True/values() is mandatory, the NaN-not-zero gap-handling fork, choosing mean vs max vs sum vs coverage by biological question, and the sorted-bedGraph plus chrom.sizes build requirement. Use when extracting signal at regions, computing mean signal per gene/peak, building a browser track from bedGraph, comparing tracks, or building TSS/gene-body metaprofiles.

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