「spl」の検索結果

Splice-aware RNA-seq aligner producing sorted BAM and splice junction tables. Builds genome index, runs two-pass alignment for better junctions. Outputs sorted BAM, junctions (SJ.out.tab), stats (Log.final.out), optional gene counts. Use Salmon for fast pseudoalignment; STAR when a BAM is needed for variant calling, IGV, or ENCODE pipelines.

日本語の概要は準備中です。原文の説明を表示しています。

Routes official 3D Gaussian Splatting setup, data preparation, training, rendering, evaluation, and viewer workflows.

日本語の概要は準備中です。原文の説明を表示しています。

Conducts digital forensics investigations following a personal data breach, covering evidence preservation, chain of custody documentation, log analysis, scope determination, and root cause analysis. References industry-standard tools including Splunk, ELK Stack, and Wireshark. Provides forensic workflow from initial evidence collection through final investigation report. Keywords: digital forensics, breach investigation, evidence preservation, chain of custody, root cause analysis, Splunk, ELK, Wireshark.

日本語の概要は準備中です。原文の説明を表示しています。

Writes and reviews composables for Compose and CMP: the Route/Screen/leaf split, state-read placement and stability, loading/empty/error UX states, LazyColumn lists and grids, animation choice, accessibility and semantics, design-system tokens, CMP Res resources, Coil images, and keyboard/focus. Use when touching @Composable code, recomposition, stability, LazyColumn, animation, shimmer or skeleton, accessibility, theme, colors, Res.string, Coil, focus, or keyboard. Do NOT use for MVI, error tiers, or module graph (compose-architecture), ViewModel or data work (compose-feature, compose-data), Gradle or module work (compose-project), or expect/actual splits (compose-platform).

日本語の概要は準備中です。原文の説明を表示しています。

Evaluate architecture and module boundaries for volatility-based decomposition using Juval Lowy's framework (from "Righting Software", building on Parnas 1972). Use when reviewing module splits, service boundaries, new abstractions, or any decomposition decision. Trigger on phrases like "where should this boundary be", "how to split this", "module boundaries", "encapsulate change", "volatility", or references to Lowy, Parnas, or "Righting Software". Complements /hickey (interleaved concerns) with a different lens (change encapsulation).

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Medical Physicist. Use when a task calls for Medical Physicist judgment. Reasons from CTDIvol/SSDE, HU accuracy, ACR/MQSA QA, TG-126 PET/CT, TG-18/TG-270 displays, and NCRP 147 shielding across CT, MRI, mammography, NM/PET, and therapy QA while treating phantom-mismatch dose claims, SUV normalization drift, display washout, and post-upgrade MEE gaps as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Think and work like an expert Cheminformatician. Use when a task calls for Cheminformatician judgment. Reasons from Standard InChI identity and RDKit sanitization through ChEMBL pChEMBL harmonization, Morgan/ECFP fingerprints, scaffold splits and applicability domains, while treating tautomer collapse, KNIME-vs-Python canonicalization drift, and random-split QSAR leakage as first-class failure modes.

日本語の概要は準備中です。原文の説明を表示しています。

Operate AudioShake's cloud source-separation service (developer.audioshake.ai) to split a recording into stems. Use when a task involves isolating vocals, drums, bass, guitar, piano, keys, strings, or winds from music; separating dialogue / music / effects (DME) for film-TV post-production, localization, and dubbing; splitting a mixed recording into one stem per speaker; lyric transcription or word-level alignment; music detection/identification; or speech denoise/dereverb. Covers the Tasks API job lifecycle (assets, targets, formats, polling vs webhooks, credits, limits), choosing which stem targets a production actually needs, reviewing separated stems for bleed / artifacts / transient smearing / phase problems and repairing them, the rights and consent questions raised by separating copyrighted or third-party recordings, and the decision boundary for when a local open model such as Demucs is the better route than the API. Not for generating or synthesizing new audio, mixing, or mastering.

日本語の概要は準備中です。原文の説明を表示しています。

Applies ACMG/AMP 2015 framework with ClinGen SVI specifications, Tavtigian 2018/2020 Bayesian point system, Abou Tayoun 2018 PVS1 decision tree, Pejaver 2022 calibrated PP3/BP4 thresholds for REVEL/BayesDel/AlphaMissense, Brnich 2020 PS3/BS3 OddsPath, Walker 2023 SpliceAI splicing framework, and AMP/ASCO/CAP 2017 tumor tiers. Use when classifying germline variants P / LP / VUS / LB / B, applying VCEP-specific CSpec rules, computing Whiffin BS1, or assigning cancer Tier I-IV per Li 2017.

日本語の概要は準備中です。原文の説明を表示しています。

A React Native developer-platform whose marketing site reads like a quietly-confident infrastructure brand. The base canvas is pure white with a soft sky-blue gradient atmospheric wash behind the hero; near-black ink (`#171717`) carries body and display alike. The single brand voltage is **pure black** (`#000000`) for primary CTAs — minimal and editorial-feeling, paired with a small blue text-link accent (`#0d74ce`) reserved for inline body links. Type pairs Inter at modest weights (display 600, body 400) with JetBrains Mono on every code surface. The brand's strongest visual signature is the **device-mockup hero** — a centered MacBook + iPhone composite showing real Expo dev surfaces — over the gradient sky wash.

日本語の概要は準備中です。原文の説明を表示しています。

A clean, calendar-software-first interface anchored on white canvas with black primary CTAs and custom Cal Sans display typography. The system reads as friendly modern SaaS — generous whitespace, soft-rounded cards (~12px), product UI fragments shown directly inside cards, and a dark navy footer that visually closes long-scroll pages. Brand voltage comes from the Cal Sans display headline (a custom geometric face) and from product UI artifacts shown in-card rather than from accent colors.

日本語の概要は準備中です。原文の説明を表示しています。

A warm-canvas editorial interface for Anthropic's Claude product. The system anchors on a tinted cream canvas with serif display headlines, warm coral CTAs, and dark navy product surfaces (code editor mockups, model showcase cards). Brand voltage comes from the cream/coral pairing — deliberately warm and humanist where most AI brands use cool blue + slate. Type voice runs a slab-serif display ("Copernicus" / Tiempos Headline) for h1/h2 and a humanist sans for body. The signature Anthropic black-radial-spike mark anchors the wordmark.

日本語の概要は準備中です。原文の説明を表示しています。

A luxury-automotive brand whose marketing surfaces read as cinematic editorial. The base canvas is **near-black** (`#181818`) holding pure white display type; white-canvas bands appear only inside specific editorial contexts (preowned listings, pricing tables). The single brand voltage is **Rosso Corsa** (`#da291c`) — the iconic Ferrari racing red — used scarcely on primary CTAs, the Cavallino mark, and Formula 1 race-position highlights. Type runs **FerrariSans** at modest weights (display 500, body 400) — never bombastic. Spacing follows an explicit 8px token ladder (`xxxs` 4px through `super` 128px); generous editorial pacing throughout. The brand's strongest visual signature is the **full-bleed cinematic hero photograph** that fills the viewport top with car photography, model details, or trackside livery — followed by a tighter editorial body layout below.

日本語の概要は準備中です。原文の説明を表示しています。

Manages stacked PRs and splits multi-part work into reviewable branches with gh-stack. Use for stack creation, viewing, edits, push, submit, sync, rebase, merge, or checkout; when asked to split or isolate work for review; whenever a user mentions a stack, branch layers, dependent PRs, or gh stack; or when a stack is checked out.

日本語の概要は準備中です。原文の説明を表示しています。

Symfony UX Map for interactive maps with Leaflet or Google Maps in Symfony. Covers markers, polygons, polylines, circles, info windows, and LiveComponent integration. Use when displaying maps, placing markers, drawing shapes or routes, handling map events, building store locators, using custom tile layers, or making maps reactive with LiveComponent. Code triggers: <twig:ux:map />, Map(), Point(), Marker(), Polygon(), Polyline(), Circle(), InfoWindow(), MapOptionsInterface, ComponentWithMapTrait, fitBoundsToMarkers, ux:map:marker:before-create, ux:map:connect, SYMFONY_UX_MAP_DSN. Also trigger when the user asks "how to display a map", "how to add markers", "how to draw a polygon on a map", "how to handle map click events", "how to make a reactive map", "how to use Leaflet in Symfony", "how to use Google Maps in Symfony", "map not showing", "map has zero height". Do NOT trigger for SVG icons (use ux-icons) or general frontend interactivity (use stimulus).

日本語の概要は準備中です。原文の説明を表示しています。

Expert in building 3D experiences for the web - Three.js, React Three Fiber, Spline, WebGL, and interactive 3D scenes. Covers product configurators, 3D portfolios, immersive websites, and bringing depth to web experiences. Use when "3D website, three.js, WebGL, react three fiber, 3D experience, spline, product configurator, " mentioned.

日本語の概要は準備中です。原文の説明を表示しています。

🔨 Andru.ia Skill-Smith (The Forge) workflow skill. Use this skill when the user needs Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

🔨 Andru.ia Skill-Smith (The Forge) workflow skill. Use this skill when the user needs Ingeniero de Sistemas de Andru.ia. Diseña, redacta y despliega nuevas habilidades (skills) dentro del repositorio siguiendo el Estándar de Diamante and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

日本語の概要は準備中です。原文の説明を表示しています。

DevOps 与站点可靠性工程 (SRE) — 平台 / 基础设施 / 可靠性工程师的认知操作系统, 覆盖软件交付 + 运维全生命周期 (CI/CD 与发布工程 trunk-based + 渐进式发布 canary/blue-green/feature flag + GitOps Argo CD/Flux / 基础设施即代码 Terraform/OpenTofu/Pulumi/Ansible + policy-as-code OPA / 容器与编排 Docker/Kubernetes + Helm/Kustomize + service mesh Istio/Linkerd / 可观测性 Prometheus + Loki + OpenTelemetry + Honeycomb + eBPF + RED/USE / SLO-SLI-error budget 与可靠性工程 Google SRE 学科 + 容量规划 + 优雅降级 / 事件管理与 on-call 事件指挥 + PagerDuty + runbook + 无指责复盘 + MTTR / 云平台与 FinOps AWS/GCP/Azure + 成本优化 + 弹性伸缩 / 平台工程与开发者体验 IDP + Backstage + golden path + Team Topologies / DevSecOps 与供应链安全 shift-left + SBOM + SLSA + sigstore + Vault / 韧性与混沌工程 fault injection + game day + 安全科学 / DORA 指标与工程效能 部署频率 + 变更前置时间 + 变更失败率 + Accelerate 研究 / 数据库与有状态运维 schema 迁移 + 备份容灾) — 不含 通用应用开发 / 纯云销售认证速成 / 'DevOps = 跑 Jenkins 的岗位' 窄化误解 / ITIL 工单文化传统运维 (旧范式仅做边界) / 把手工运维 ClickOps 当稳态 (是 toil, 本 skill 核心反模式) (DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, Helm / Kustomize, service mesh Istio / Linkerd), (d) observability (the three pillars + beyond — metrics Prometheus / VictoriaMetrics, logs Loki / ELK, traces OpenTelemetry / Jaeger / Tempo, high-cardinality observability Honeycomb, eBPF, RED / USE methods, SLO-based alerting), (e) SLO / SLI / error budgets & reliability engineering (Google SRE discipline — service level objectives, error budget policy, toil budgets, capacity planning, load shedding, graceful degradation), (f) incident management & on-call (incident command, PagerDuty / Opsgenie, runbooks, blameless postmortems, MTTR / MTTD, error budget burn), (g) cloud platforms & FinOps (AWS / GCP / Azure well-architected, multi-region, cost optimization, autoscaling), (h) platform engineering & developer experience (internal developer platforms, Backstage, golden paths, self-service, Team Topologies), (i) DevSecOps & supply-chain security (shift-left, SAST / DAST, SBOM, SLSA, sigstore / cosign, secrets management Vault), (j) resilience & chaos engineering (chaos experiments, fault injection, game days, resilience engineering / safety science), (k) DORA metrics & engineering effectiveness (deployment frequency, lead time, change failure rate, MTTR, the Accelerate research), (l) databases & stateful operations (schema migrations, backups / DR, replication); NOT generic software development / app feature coding (是 平行学科, DevOps/SRE 关注 delivery + operability 不是 product feature), NOT pure cloud sales / certification cram without operational depth, NOT 'DevOps = a job title that runs Jenkins' 的窄化误解 (DevOps 是 文化 + 实践, SRE 是 Google 对 reliability 的工程化具体实现), NOT ITIL-heavy 传统运维 工单文化 (是 被 DevOps 取代的旧范式, 仅做边界标注), NOT manual ops / ClickOps as a steady state (是 toil, 本 skill 的核心反模式).) Master OS — automated mastery of DevOps & Site Reliability Engineering — the cognitive operating system of platform / infrastructure / reliability practitioners who own the full software delivery + operational lifecycle, covering (a) CI/CD & release engineering (build pipelines, trunk-based development, progressive delivery — canary / blue-green / feature flags, GitOps with Argo CD / Flux), (b) Infrastructure as Code (Terraform / OpenTofu, Pulumi, CloudFormation, Ansible, Crossplane — module design, state management, drift, policy-as-code OPA / Sentinel / Checkov), (c) containers & orchestration (Docker / OCI, Kubernetes — scheduling, networking CNI, storage CSI, operators / CRDs, He

日本語の概要は準備中です。原文の説明を表示しています。

谈判与议价 (谈判与议价 (Negotiation & Bargaining) — 面向要亲自坐上谈判桌的从业者（销售、采购、创业者、法务与商务、HR、投融资、以及为自己谈薪谈房谈合同的个人）的『把一次利益分歧，谈成一个双方都愿意签、签完还愿意执行的结果』的判断体系；不是某一个行业的成交话术合集，也不是博弈论课程，更不是把心理学包装成读心术的培训话术。覆盖：(a) 第一性张力 —— 这行最深的世界观分歧：**创造价值 ⇄ 攫取价值**（同一场谈判里，把饼做大和把饼切走用的是相反的动作：做大要交换信息、暴露优先级，切走要隐藏底线、制造稀缺；哈佛原则式谈判一派主张先做大再切，实战议价派认为在多数一次性交易里做大只是让步的遮羞布，这条张力叫谈判者困境，是整个学科的中心问题）；**原则式谈判 ⇄ 战术共情**（Getting to Yes 主张对事不对人、按客观标准而非意志力定输赢；Chris Voss 从人质谈判带出的路线针锋相对，书名 Never Split the Difference 直接反对折中，主张先用标签与校准问题把对方的情绪与安全感处理掉再谈条件，并公开批评双赢框架让谈判者被真正强硬的对手吃掉；两派对同一个动作——比如要不要说出你的底线——给出相反指令）；**关系先行 ⇄ 条款先行**（中文语境里做生意常常先建立关系、找中间人引荐、酒桌上定调、合同只是关系的书面确认，人情与面子既是润滑剂也是隐性负债；跨国与合规语境里条款先行、把一切写进合同，两种作业习惯在同一张桌上相遇时的误读，是中外商务谈判失败最常见的原因之一；学术上关系到底是效率替代品还是寻租温床，证据本身就是对立的，且反腐与合规收紧之后酒桌路径的风险显著上升）；**先出价 ⇄ 后出价**（实验研究普遍支持先出价能形成锚定优势，但在信息高度不对称的真实交易里，先出价可能暴露自己远低于对方预期，实务派与研究派对这条给出的条件不同）；**BATNA 是地基 ⇄ BATNA 被高估**（最佳替代方案是原则式谈判的支点，没有替代方案就没有说不的能力；反对者指出过度盯着替代方案会把谈判做成线性比价，且强替代方案在长期关系里会损害对方的信任）；**情绪是噪音 ⇄ 情绪是议题**（早期理性决策路线要求把人和问题分开，后来的研究把情绪重新请回桌上：愤怒有时确实能提取让步，代价是长期关系与对方的报复动机，实验证据两个方向都有）；**谈判是技能 ⇄ 谈判是性格**（培训产业的立身之本是可训练，而研究显示某些结果差异与性别、地位与社会代价强相关：女性主动发起薪酬谈判在部分情境会被惩罚，这不是话术能解决的结构问题，近年多地薪酬区间披露立法正在改变这条起点）；**诚实边界在哪**（虚构竞标者、夸大授权上限、拖延签约制造紧迫，这些在培训里被当技巧、在法律上可能构成欺诈性陈述，法域不同边界不同）。(b) 工具栈 —— 这一行最重要的工具是纸笔：议题清单与优先级打分表、替代方案与保留价的估算表、可交换筹码矩阵、同时抛出的多个等值报价、让步阶梯与理由库、授权与升级路径表、复盘表；软件侧则是合同全生命周期管理与条款库（Ironclad、DocuSign、Juro、LinkSquares，中国侧法大大、e签宝）、采购电子寻源与反向拍卖（SAP Ariba、Coupa、Keelvar，以及已在大企业跑通的自动化议价机器人 Pactum）、销售侧的折扣审批矩阵与 deal desk、薪酬与职级数据（Levels.fyi、Mercer、Radford 以及各地薪酬透明披露）、可比交易与市场价数据、调解与仲裁机构（CIETAC、SIAC、香港 HKIAC）、以及正在快速变化的大模型陪练与合同审查；选型的真正分岔从来不是功能表，而是『这场谈判赢在信息、赢在替代方案，还是赢在流程设计』。(c) 心智模型层 —— 结果在坐上桌之前就决定了大半；谈的是利益不是立场；议价区间是估计出来的不是给定的；让步是信息不是善意；说不出口的常常是面子与安全感而不是价格；代表别人谈判的人激励与授权跟本人不同；一次性交易与长期关系的最优打法不同而多数人搞错了自己在玩哪一种。(d) 工作流 —— 立项与利益相关方梳理、准备与对手画像、替代方案与保留价、议题打分与打包设计、开场与锚定、探询与试探性提议、让步管理、僵局与第三方介入、收口与防止反悔加码、合同化与争议解决条款、复盘与关系维护，以及薪资谈判、采购年度框架议价、并购价格与条款、多方与联盟、跨文化与远程邮件谈判这些特化路径。(e) 表达 DNA、质量基准（什么算一次好的谈判：不是拿到最低价，而是可执行、可复盘、不透支关系）、反模式（外行最容易犯的错：不准备就上桌、把立场当利益、单方面让步买好感、把折中当公平、拿假竞标者施压、口头承诺不落纸、赢了条款输了执行）、智识谱系（哈佛谈判项目与原则式谈判、行为决策与实验社会心理学派、危机谈判与战术共情派、谈判分析与博弈论派、销售采购的实战议价培训派、争议解决与调解派、跨文化谈判派、中文语境的关系与人情派）。) Master OS — automated mastery of 谈判与议价 (Negotiation & Bargaining) — 面向要亲自坐上谈判桌的从业者（销售、采购、创业者、法务与商务、HR、投融资、以及为自己谈薪谈房谈合同的个人）的『把一次利益分歧，谈成一个双方都愿意签、签完还愿意执行的结果』的判断体系；不是某一个行业的成交话术合集，也不是博弈论课程，更不是把心理学包装成读心术的培训话术。覆盖：(a) 第一性张力 —— 这行最深的世界观分歧：**创造价值 ⇄ 攫取价值**（同一场谈判里，把饼做大和把饼切走用的是相反的动作：做大要交换信息、暴露优先级，切走要隐藏底线、制造稀缺；哈佛原则式谈判一派主张先做大再切，实战议价派认为在多数一次性交易里做大只是让步的遮羞布，这条张力叫谈判者困境，是整个学科的中心问题）；**原则式谈判 ⇄ 战术共情**（Getting to Yes 主张对事不对人、按客观标准而非意志力定输赢；Chris Voss 从人质谈判带出的路线针锋相对，书名 Never Split the Difference 直接反对折中，主张先用标签与校准问题把对方的情绪与安全感处理掉再谈条件，并公开批评双赢框架让谈判者被真正强硬的对手吃掉；两派对同一个动作——比如要不要说出你的底线——给出相反指令）；**关系先行 ⇄ 条款先行**（中文语境里做生意常常先建立关系、找中间人引荐、酒桌上定调、合同只是关系的书面确认，人情与面子既是润滑剂也是隐性负债；跨国与合规语境里条款先行、把一切写进合同，两种作业习惯在同一张桌上相遇时的误读，是中外商务谈判失败最常见的原因之一；学术上关系到底是效率替代品还是寻租温床，证据本身就是对立的，且反腐与合规收紧之后酒桌路径的风险显著上升）；**先出价 ⇄ 后出价**（实验研究普遍支持先出价能形成锚定优势，但在信息高度不对称的真实交易里，先出价可能暴露自己远低于对方预期，实务派与研究派对这条给出的条件不同）；**BATNA 是地基 ⇄ BATNA 被高估**（最佳替代方案是原则式谈判的支点，没有替代方案就没有说不的能力；反对者指出过度盯着替代方案会把谈判做成线性比价，且强替代方案在长期关系里会损害对方的信任）；**情绪是噪音 ⇄ 情绪是议题**（早期理性决策路线要求把人和问题分开，后来的研究把情绪重新请回桌上：愤怒有时确实能提取让步，代价是长期关系与对方的报复动机，实验证据两个方向都有）；**谈判是技能 ⇄ 谈判是性格**（培训产业的立身之本是可训练，而研究显示某些结果差异与性别、地位与社会代价强相关：女性主动发起薪酬谈判在部分情境会被惩罚，这不是话术能解决的结构问题，近年多地薪酬区间披露立法正在改变这条起点）；**诚实边界在哪**（虚构竞标者、夸大授权上限、拖延签约制造紧迫，这些在培训里被当技巧、在法律上可能构成欺诈性陈述，法域不同边界不同）。(b) 工具栈 —— 这一行最重要的工具是纸笔：议题清单与优先级打分表、替代方案与保留价的估算表、可交换筹码矩阵、同时抛出的多个等值报价、让步阶梯与理由库、授权与升级路径表、复盘表；软件侧则是合同全生命周期管理与条款库（Ironclad、DocuSign、Juro、LinkSquares，中国侧法大大、e签宝）、采购电子寻源与反向拍卖（SAP Ariba、Coupa、Keelvar，以及已在大企业跑通的自动化议价机器人 Pactum）、销售侧的折扣审批矩阵与 deal desk、薪酬与职级数据（Levels.fyi、Mercer、Radford 以及各地薪酬透明披露）、可比交易与市场价数据、调解与仲裁机构（CIETAC、SIAC、香港 HKIAC）、以及正在快速变化的大模型陪练与合同审查；选型的真正分岔从来不是功能表，而是『这场谈判赢在信息、赢在替代方案，还是赢在流程设计』。(c) 心智模型层 —— 结果在坐上桌之前就决定了大半；谈的是利益不是立场；议价区间是估计出来的不是给定的；让步是信息不是善意；说不出口的常常是面子与安全感而不是价格；代表别人谈判的人激励与授权跟本人不同；一次性交易与长期关系的最优打法不同而多数人搞错了自己在玩哪一种。(d) 工作流 —— 立项与利益相关方梳理、准备与对手画像、替代方案与保留价、议题打分与打包设计、开场与锚定、探询与试探性提议、让步管理、僵局与第三方介入、收口与防止反悔加码、合同化与争议解决条款、复盘与关系维护，以及薪资谈判、采购年度框架议价、并购价格与条款、多方与联盟、跨文化与远程邮件谈判这些特化路径。(e) 表达 DNA、质量基准（什么算一次

日本語の概要は準備中です。原文の説明を表示しています。

Suede Labs skill that finds and organizes the rights gaps in a creator project before packaging: ownership, contributors, splits, samples, licenses, provenance, metadata, licensing readiness, and royalty-routing readiness, each marked confirmed or unknown against an evidence trail. Use when a song, release, or creative project needs a rights check before registry, licensing, sync, or payout discussion; when splits, sample clearance, or chain of title are unclear; or when someone asks whether they have the rights to release, license, or get paid for a work. Organizes evidence only: clears no rights, confirms no ownership, moves no money, writes to no registry. NOT FOR: building the transfer package itself (use suede-rights-passport); linting a release folder's files and metadata (use suede-release-linter); a sync one-sheet or pitch (use suede-sync-packaging).

日本語の概要は準備中です。原文の説明を表示しています。

Suede Labs skill that lints a local music or media release folder and scores it for release readiness: missing files, weak or malformed metadata, artwork and stem problems, split gaps, rights blockers, and platform-delivery issues, produced by a bundled offline script as a scored markdown and JSON report. Use when a creator has one or more release folders of tracks, artwork, and stems and wants to know what is missing before distributing, delivering, or handing it off; when metadata quality or a delivery rejection is the question; or when a release-readiness score is asked for. Reports what is present, missing, or unknown; never upgrades unknown to confirmed and never means legal clearance. NOT FOR: organizing the evidence behind a rights or split gap the report surfaces (use suede-rights-audit); building the transfer package (use suede-rights-passport); a sync one-sheet (use suede-sync-packaging).

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "animate our logo", "make a logo intro/stinger", "build a brand reveal", "create an app splash animation", "loop a loader logo", "draw on our SVG mark", "morph an icon into the wordmark", or "sync the logo to a sound-logo". Covers web (SVG/Lottie), video, and app-splash delivery.

日本語の概要は準備中です。原文の説明を表示しています。

Use when an approved analiz spans more than one repository - split the work per repository and open one or more tasks per repository, each carrying its own plan slice

日本語の概要は準備中です。原文の説明を表示しています。