7,599 件 ・ 関連度順
概要と使いどころ
Accessibility Audit and Testing workflow skill. Use this skill when the user needs You are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Address GitHub Comments workflow skill. Use this skill when the user needs you need to address review or issue comments on an open GitHub Pull Request using the gh CLI and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
A/B Test Setup workflow skill. Use this skill when the user needs Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
2D Game Development workflow skill. Use this skill when the user needs 2D game development principles. Sprites, tilemaps, physics, camera and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Evaluation workflow skill. Use this skill when the user needs Testing and benchmarking LLM agents including behavioral testing, and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
A/B Test Setup workflow skill. Use this skill when the user needs Structured guide for setting up A/B tests with mandatory gates for hypothesis, metrics, and execution readiness and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Agent Framework Azure Hosted Agents workflow skill. Use this skill when the user needs Build persistent agents on Azure AI Foundry using the Microsoft Agent Framework Python SDK and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
Ad Creative workflow skill. Use this skill when the user needs Create, iterate, and scale paid ad creative for Google Ads, Meta, LinkedIn, TikTok, and similar platforms. Use when generating headlines, descriptions, primary text, or large sets of ad variations for testing and performance optimization and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.
日本語の概要は準備中です。原文の説明を表示しています。
半导体芯片制造工艺 (Semiconductor Process Engineering / 半导体芯片制造工艺 — 以「物理化学极限 + 良率经济双重约束」为特征的集成电路前道/后道制造工艺认知操作系统：从「器件架构与微缩路线（planar→FinFET→GAA nanosheet→CFET、等效微缩 DTCO/STCO、背面供电 BSPDN）→ 工艺整合（FEOL/MOL/BEOL 模块协同、PDK、流片 tape-out）→ 单元工艺（光刻 litho（DUV 浸没式 193i / EUV 13.5nm / 多重曝光 SADP-SAQP / OPC / mask）、刻蚀 etch（RIE/ICP/原子层刻蚀 ALE）、薄膜沉积 depo（CVD/PECVD/LPCVD/ALD/PVD/外延 epi/电镀 Cu）、掺杂 doping（离子注入 ion implant / 退火 RTA-laser anneal）、CMP 化学机械抛光、清洗 cleaning）→ 量测检测 metrology（CD-SEM / OCD / overlay / 椭偏 ellipsometry / 缺陷检测 defect inspection / e-beam）→ 良率工程 yield（缺陷密度 / SPC 统计过程控制 / FDC / APC / DOE 实验设计 / 良率爬坡 yield ramp）→ 先进封装 advanced packaging（2.5D/3D、CoWoS、HBM、混合键合 hybrid bonding、chiplet、TSV）」的完整器件-工艺-良率-量产决策链。覆盖 (a) 第一性张力 — **物理/化学/材料的硬约束（量子隧穿、短沟道效应、RC 延迟、热预算、缺陷物理、ppb 级污染控制）⇄ 良率/成本/产能的经济约束（每片晶圆成本、良率是主经济指标、D0 缺陷密度、wafer-per-hour、折旧）**；**持续微缩/摩尔定律（dimensional + equivalent scaling、节点路线图 N5/N3/N2/A16/A14、high-NA EUV）⇄ 物理极限/微缩放缓（原子尺度、漏电、功耗墙、成本墙、'摩尔定律已死'之争）**；**协同优化/整合（DTCO 设计-工艺协同、STCO 系统-工艺协同、模块间 trade-off）⇄ 单模块极致优化（单一 unit process 工艺窗口）**；**工艺配方的 tacit 手艺（process recipe 调试、工艺窗口、缺陷根因分析、量产 ramp 的经验）⇄ 可建模/可仿真/数据驱动（TCAD 仿真、ML 良率分析、APC/FDC、数字孪生）**；**性能-功耗-面积-成本 PPAC 四角权衡 ⇄ 良率/可制造性 DFM 优先**；**自主可控/国产替代（卡脖子、EUV 出口管制、设备/材料/EDA 国产化、SMIC/长江存储/长鑫/中微/北方华创/上海微电子）⇄ 全球高度分工（ASML 光刻垄断、AMAT/Lam/TEL/KLA 设备、TSMC/Samsung/Intel 代工、全球供应链）**。(b) 核心工作流 / pipeline（最标准、最易蒸高质量 + CLI 化）— 新节点/新工艺导入：器件目标与 PPAC 定义 → 工艺整合方案与 PDK → 单元工艺开发与配方调试（DOE 找工艺窗口）→ 量测建立与 SPC → 良率爬坡（缺陷分类 + 根因分析 + 工艺改善）→ 量产移交与持续改善。具体单元工艺 SOP：光刻（曝光条件 / OPC / overlay 控制 / 多重曝光分解）、刻蚀（选择比 / profile / loading effect / ALE）、沉积（台阶覆盖 / 应力 / 均匀性）、CMP（去除速率 / 碟形 dishing / 侵蚀 erosion）、量测与缺陷分析、良率分析与 FA 失效分析。(c) 工具栈 — 设备（光刻 ASML/上海微电子 SMEE；刻蚀+沉积 AMAT/Lam/TEL/中微 AMEC/北方华创 Naura；离子注入 AMAT/Axcelis；CMP AMAT/荏原 Ebara；量测检测 KLA/AMAT/中科飞测/上海精测）、EDA/TCAD/仿真（Synopsys Sentaurus/Silvaco/Coventor SEMulator3D、OPC Calibre/Synopsys）、良率与制造软件（SPC、MES、FDC/APC、缺陷分析 yield management、PWS）、材料（光刻胶 photoresist、CMP 浆料 slurry、特气、靶材、掩膜 mask blank）。(d) 知识正典 — 半导体工艺 canon 横跨器件物理与制造工程：核心教材（Plummer/Deal/Griffin《Silicon VLSI Technology》、Sze《Physics of Semiconductor Devices》《VLSI Technology》、Wolf & Tauber《Silicon Processing for the VLSI Era》、Campbell《Fabrication Engineering at the Micro and Nanoscale》、May & Spanos《Fundamentals of Semiconductor Manufacturing and Process Control》、Quirk & Serda《Semiconductor Manufacturing Technology》、肖国勇/施敏中文教材）、路线图（ITRS/IRDS、IEEE 国际器件与系统路线图）、顶会论文（IEDM、Symposium on VLSI Technology、IRPS 可靠性、SPIE Advanced Lithography、ISSCC、DAC）、行业分析（SemiAnalysis、TechInsights、IC Knowledge）。(e) figures/流派 — 学术与器件奠基（Gordon Moore 摩尔、Robert Dennard 登纳德微缩、胡正明 Chenming Hu FinFET/UTB-SOI 发明人 UC Berkeley、刘明 Tsu-Jae King Liu Berkeley、Krishna Saraswat Stanford、Mark Bohr Intel 工艺架构）、产业领袖与工艺大师（张忠谋 Morris Chang TSMC、林本坚 Burn-Jeng Lin 浸没式光刻、Martin van den Brink ASML、米玉杰/梁孟松 SMIC/三星工艺、Mark Liu/魏哲家 TSMC）、行业分析师（Dylan Patel SemiAnalysis、Scotten Jones IC Knowledge、TechInsights 拆解、Handel Jones）、科普与拆解（Asianometry、The Chip Letter、半导体行业观察）。流派分歧：等效微缩派 vs 摩尔定律已死派、前道微缩 vs 先进封装 chiplet 异构集成、dimensional scaling vs DTCO 协同优化、IDM vs 纯代工 foundry 模式、自主可控/国产替代路线 vs 全球分工。(f) 行业话术/黑话 — 制程节点 node / 流片 tape-out / 工艺窗口 process window / 良率 yield / 缺陷密度 D0 / 关键尺寸 CD / 套刻 overlay / 掩膜 reticle-mask / 光刻胶 PR / 浸没式 immersion / EUV/DUV / 多重曝光 multi-patterning SADP-SAQP / OPC / 刻蚀选择比 selectivity / profile / loading effect / 原子层刻蚀 ALE / 台阶覆盖 step coverage / 外延 epi / 离子注入 implant / 退火 anneal / RTA / CMP / dishing-erosion / FEOL-MOL-BEOL / FinFET / GAA / 纳米片 nanosheet / CFET / 背面供电 BSPDN / high-NA / PPAC / DTCO-STCO / DFM / SPC / FDC-APC / DOE / WAT-PCM / 良率爬坡 yield ramp / FA 失效分析 / particle 颗粒 / 洁净室 cleanroom-级别 / 12寸-8寸 wafer / chiplet / CoWoS / HBM / 混合键合 hybrid bonding / TSV / PDK / 等效微缩. (g) 争议/批判 — 「摩尔定律是否已死 vs 等效微缩继续」、「节点命名营销化（N3/N2 ≠ 物理 3nm/2nm，gate pitch/metal pitch 才是真尺度）」、「前道微缩 vs 先进封装异构集成谁是未来」、「自主可控/国产替代的现实（EUV 卡脖子、设备/材料/EDA 国产化进度、出口管制 entity list、良率与成熟度差距）」、「良率/成本/性能三角权衡」、「人才稀缺与工艺 know-how 的 tacit 性」、「中国大基金/产能扩张是否过剩」、「制裁与技术封锁」。(h) 大量隐性工艺手艺（process recipe 调试与工艺窗口寻找、缺陷根因分析与 FA、量产良率爬坡的经验判
日本語の概要は準備中です。原文の説明を表示しています。
红队渗透 / 攻防 — 受授权的红队作业者 + 渗透测试工程师 + 攻击型安全顾问的认知操作系统 (侦察 OSINT / 外网渗透 / 内网 AD 渗透 BloodHound + Kerberoasting + ADCS 利用 + 横向移动 / Web 应用渗透 OWASP WSTG / 移动 OWASP MASTG / 云渗透 AWS Azure GCP IAM 路径 + 容器逃逸 + K8s / C2 操作 Cobalt Strike Sliver Mythic Havoc + OPSEC / 初始访问 + AV EDR 绕过 (仅授权场景) / 无线 RF / 物理社工 / 报告与整改 / 框架 MITRE ATT&CK + D3FEND + PTES + OSSTMM + NIST 800-115 + Kill Chain / 法律伦理 CFAA + 网络安全法 + 刑法 285 286 + 数据安全法 + GDPR + 授权书 + 范围 + 交战规则 — 不含 黑产 / 未授权攻击 / 大规模 exploitation / 供应链投毒 / 未授权 DoS — 这是 重罪 + 行业封杀 + 律师吊销, 本 skill 严守 authorized-only 边界 — 也不含 蓝队 SOC + 恶意软件 即服务 / 僵尸网络 / 勒索软件作者 — 这是 cybercrime 不是 红队) (Cybersecurity Red Team / Offensive Security Operations — the cognitive operating system of authorized red team operators, penetration testers, and offensive security consultants covering (a) reconnaissance & OSINT (passive + active discovery, asset surface mapping), (b) external network pentest (perimeter, exposed services, web), (c) internal network / Active Directory pentest (AD enumeration via BloodHound, Kerberos abuse — Kerberoasting / AS-REP-roasting / Unconstrained delegation / S4U2self, NTLM relay, ADCS abuse, GPO abuse, lateral movement, privilege escalation), (d) web application pentest (OWASP WSTG, authentication, authorization, SSRF, XXE, deserialization, SSTI, prototype pollution, GraphQL, JWT, API), (e) mobile pentest (OWASP MASTG, iOS / Android, instrumentation Frida / Objection, MASVS), (f) cloud pentest (AWS / Azure / GCP — IAM enumeration, privilege escalation paths, container escape, K8s RBAC, serverless), (g) C2 operations & post-exploitation (Cobalt Strike / Sliver / Mythic / Havoc, beacon ops, malleable profiles, OPSEC), (h) initial access & evasion (phishing infrastructure, payload development, AV / EDR evasion, BYOVD, AMSI / ETW bypass — strictly for authorized engagements), (i) wireless / RF (WPA2/3, evil twin, Wi-Fi pivots), (j) physical / social engineering (badge cloning, pretexting, vishing — under engagement letter), (k) reporting & remediation (executive summary, technical findings, CVSS, MITRE ATT&CK mapping, retest), (l) frameworks & methodology (MITRE ATT&CK, MITRE D3FEND, PTES, OSSTMM, NIST SP 800-115, OWASP WSTG / MASTG, Cyber Kill Chain, Unified Kill Chain, Diamond Model), (m) law & ethics (CFAA US, Computer Misuse Act UK, 中国 刑法 285/286 + 网络安全法 + 数据安全法, GDPR for tested EU systems, engagement letter, scope, rules of engagement, safe harbor for bug bounty); NOT criminal hacking / 黑产 / unauthorized targeting / mass exploitation / supply-chain compromise / DoS against unconsented systems (这是 重罪 + 业内开除 + 律师执照吊销, 本 skill 严守 authorized-only 边界), NOT pure defensive blue team / SOC analyst tradecraft (是 平行学科, 仅做 边界标注 + ATT&CK 反推方向), NOT malware-as-a-service development / botnet ops / ransomware authoring (是 cybercrime 不是 红队), NOT 'ethical hacking' 在 'just curious 看看' 自我合理化的灰色操作 (违反 authorization 原则即不是 红队).) Master OS — automated mastery of Cybersecurity Red Team / Offensive Security Operations — the cognitive operating system of authorized red team operators, penetration testers, and offensive security consultants covering (a) reconnaissance & OSINT (passive + active discovery, asset surface mapping), (b) external network pentest (perimeter, exposed services, web), (c) internal network / Active Directory pentest (AD enumeration via BloodHound, Kerberos abuse — Kerberoasting / AS-REP-roasting / Unconstrained delegation / S4U2self, NTLM relay, ADCS abuse, GPO abuse, lateral movement, privilege escalation), (d) web application pentest (OWASP WSTG, authentication, authorization, SSRF, XXE, deserialization, SSTI, prototype pollution, GraphQL, JWT, API), (e) mobile pentest (OWASP MASTG, iOS / Android, instrumentation Frida / Objection, MASVS), (f) cloud pentest (AWS / Azure / GCP — IAM enumeration, privilege escalation paths, container escape, K8s RBAC, serverless), (g) C2 operations & post-exploitation (Cobalt Strike / Sliver / Mythic / Havoc, beacon ops, malleable profiles, OPSEC), (h) initial access & evasi
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants to know what will break if they change something, or needs safety analysis before editing code. Examples: "Is it safe to change X?", "What depends on this?", "What will break?"
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user is debugging a bug, tracing an error, or asking why something fails. Examples: "Why is X failing?", "Where does this error come from?", "Trace this bug"
日本語の概要は準備中です。原文の説明を表示しています。
Land an OpenClaw PR end-to-end using the repo landpr checklist. Use when someone requests “/landpr” or asks to merge/land a PR.
日本語の概要は準備中です。原文の説明を表示しています。
Makes small documents as shareable Tiny Little Office links, where the URL itself is the document. Covers slide decks, posters, zines, spreadsheets, charts and small-business models, letters, résumés, invoices, outlines, diagrams (mind map, org chart, family tree, swimlanes, timeline, Venn, seating, network), drawings, pixel art, animations, calendars, Gantt schedules, trip maps and a calculator that shows its working. Use when someone wants such a document as a link they can open, edit and pass on rather than a file, or names tinylittleoffice / TLO.
日本語の概要は準備中です。原文の説明を表示しています。
Interactive codebase orientation for a HUMAN who wants to learn the code. Runs the same tree-sitting + featuring pipeline as exploring-codebases but synthesizes it into guided exercises and an HTML teaching artifact rather than an analysis document. Use for "orient me to this repo", "teach me this codebase", "walk me through this code", "learning orientation", or when someone wants genuine comprehension rather than a task completed. The audience is the test: if nobody is being taught and the goal is to get work done, use exploring-codebases instead.
日本語の概要は準備中です。原文の説明を表示しています。
Interpret video content visually by sampling frames into timestamped contact sheets that can be read as images. Use when: user asks what happens in a video; asks to summarize, describe, review, or QA video content or footage; asks about scenes, actions, people, or objects in a video; needs a storyboard-style overview of a clip; asks to find where something occurs in a video. Triggers on 'watch this video', 'what's in this video', 'summarize the video', 'describe the footage', 'contact sheet', 'storyboard', 'review this clip', 'find the scene where', 'scene detection', 'shot boundaries', 'detect cuts', 'dwell points'. For converting, trimming, or transcoding video, use processing-video instead.
日本語の概要は準備中です。原文の説明を表示しています。
Analyzes an AI/ML publication — paper, preprint, article, technical blog post — and extracts what an enterprise AI engineer should do about it. Use when someone supplies a URL or document on RAG, embeddings, fine-tuning, prompt engineering, agents, or LLM deployment and asks "review this paper", "what do you make of this", "is this worth adopting", or "summarise the method and its limits". The subject matter must itself be machine learning.
日本語の概要は準備中です。原文の説明を表示しています。
Pre-change blast-radius report for a symbol or file. Walks tree-sitting references, augments with a plain-text scan over non-parsed files (configs, plain docs), and clusters affected sites by feature (`_FEATURES.md`) or top-level package. Use when about to refactor, rename, or delete something in a repo you don't own — "what breaks if I change `validateUser`", "who calls this", "is this safe to remove", "where is this used", "blast radius", "impact analysis". This is the CONVERGENT pre-change risk skill — for "what is this repo?" use exploring-codebases; for "where is X?" use searching-codebases.
日本語の概要は準備中です。原文の説明を表示しています。
Exports a Claude.ai workspace — its custom instructions and its uploaded knowledge files — into a bundle that can be re-imported elsewhere. Use for "back up my project instructions", "export my project knowledge", "copy this workspace to a new one", "migrate my project to another account", or "recreate this setup somewhere else". Operates on the Claude.ai workspace you are talking in, and reads nothing from disk.
日本語の概要は準備中です。原文の説明を表示しています。
Chooses the right FORMAT for instructions on Claude.ai — project instructions, a skill, or a standalone prompt — and gives the format-specific structure once chosen. Use when the question is which container an instruction belongs in ("should this be a skill or project instructions", "where do I put this", "how do I set up this project", "is this worth a skill"), or when someone has instructions and does not know how to package them. For the writing principles that apply inside any of the three formats, use writing-instructions. For building, testing and packaging a complete skill directory, use creating-skill.
日本語の概要は準備中です。原文の説明を表示しています。
Read Bluesky/ATProto without depending on Bluesky's AppView — interactions on a user's posts, thread replies, any repo's records, network-wide backlinks across every lexicon, an account's handle and PDS history, which collections are active network-wide, and layer-by-layer outage diagnosis. Use when bsky.app or the AppView is down or slow, when a Bluesky read returns timeouts or 5xx, when asked who liked/replied/quoted/reposted something, when pulling live Bluesky context cheaply, when reading records straight from a PDS, when asked who references a record or account anywhere on the network, whether an account has changed handle or migrated servers, or which lexicons and non-Bluesky apps are active on atproto. Complements browsing-bluesky, which routes everything through the AppView and fails when it does.
日本語の概要は準備中です。原文の説明を表示しています。
Generate hierarchical _FEATURES.md files that describe what a codebase DOES from a user/consumer perspective, anchored to source symbols via tree-sitting. Supports large complex codebases through feature-driven decomposition into sub-feature files. Uses a multi-pass synthesis: orientation → detail → overview rewrite. Use when someone says "what does this do", "document features", "feature inventory", "_FEATURES.md", or needs to understand a codebase's purpose before modifying it. Complements tree-sitting (structural) with semantic (why/what-for) layer.
日本語の概要は準備中です。原文の説明を表示しています。
Load at the start of any task whose deliverable is prose another person will read — a PR description, commit message, README, doc, postmortem, blog post, issue or review comment, report, release note or essay — before drafting it, whether the result is pushed, posted, published or saved to a file, without being asked. Draft, then run this pass on the draft before handing it over. Also use when someone says "de-claude", "de-slop", "humanize this", "this reads like AI", "make it sound human", or asks for a voice, tone or register edit. Rewrites the constructions that mark prose as model-written (staged reveals, verdict headers, aphoristic closers, "it's not X, it's Y", em-dash drama, forced triads, flat-certainty adverbs) into plain technical prose and checks the rewrite kept every claim. Not for fiction, poetry, code, or quoted text; for a full adversarial review of a deliverable use challenging.
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis loop for hard bugs and performance regressions. Use when the user says "diagnose"/"debug this", or reports something broken/throwing/failing/slow.
日本語の概要は準備中です。原文の説明を表示しています。