「hn」の検索結果

Keeping codebases healthy, performant, and maintainable - refactoring, performance optimization, and technical debt managementUse when "refactor, optimize, performance, technical debt, cleanup, architecture, speed up, bundle size, memory leak, slow query, code smell, complexity, dead code, performance, refactoring, optimization, technical-debt, architecture, cleanup, bundle, memory" mentioned.

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

World-class accessibility design expertise combining the inclusive design principles of Microsoft's Inclusive Design team, the technical rigor of the W3C WCAG working group, and the lived experience perspective of disability advocates. Accessibility is not a feature - it's a fundamental quality attribute that makes products usable by everyone. Great accessibility design is invisible to those who don't need it and essential to those who do. It benefits everyone: captions help in noisy environments, keyboard navigation helps power users, high contrast helps in bright sunlight. When you design for the extremes, you improve the experience for all. Accessibility is not a checklist - it's a mindset that asks "who are we excluding?" at every design decision. Use when "accessibility, a11y, wcag, screen reader, keyboard navigation, color contrast, alt text, aria, focus management, skip link, assistive technology, inclusive design, ada compliance, section 508, accessible, voiceover, nvda, jaws, tab order, focus trap, accessibility, a11y, wcag, inclusive-design, screen-reader, keyboard-navigation, color-contrast, aria, focus-management, assistive-technology" mentioned.

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

Technical SEO site audit via the DataForSEO On-Page API. Crawls the site (up to 100 pages by default), surfaces critical errors (broken links, redirect chains, missing meta, slow pages, schema gaps, indexability issues), and returns a Technical Score (0-100) with prioritized fixes.

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

Deep technical SEO auditing covering crawlability, indexation, Core Web Vitals, site architecture, canonicalization, structured data validation, and performance optimization. Use when the user asks about technical SEO, site audits, crawl issues, indexation problems, Core Web Vitals, page speed, or site architecture optimization. For content-focused SEO, see the seo-content-writer skill.

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

AWS Penetration Testing workflow skill. Use this skill when the user needs Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

AWS Penetration Testing workflow skill. Use this skill when the user needs Provide comprehensive techniques for penetration testing AWS cloud environments. Covers IAM enumeration, privilege escalation, SSRF to metadata endpoint, S3 bucket exploitation, Lambda code extraction, and persistence techniques for red team operations and the operator should preserve the upstream workflow, copied support files, and provenance before merging or handing off.

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

推特中文圈 AI 自媒体博主 (推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。) Master OS — automated mastery of 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 推特(X) 中文圈 AI 自媒体博主 (从业者视角) — 在 X/推特 用中文做 AI 内容的自媒体博主，重点是**怎么写推文/thread、怎么制作内容**。覆盖: (a) 选题 — AI 模型发布解读 / prompt 技巧 / AI 工具实测 / AI 出海与独立开发(build in public) / 英文一手编译翻译 / 信息差 / AI 资讯快讯 / 深度长推; (b) 文案与内容结构(核心) — 单条推(开头钩子/信息密度/短句断行/配图截图/数据图)、长推与 thread(首条钩子/编号/逻辑链/结尾关注 CTA)、引用锐评(quote tweet)、排版可读性、配图(ray.so/carbon 代码图/产品截图/对比图); (c) 内容制作工作流 — 找信息源(英文一手/arXiv/官方/Reddit/HN)→选题→编译总结加洞察→写推/thread→配图→发布→互动维护; (d) AI 工具用于内容生产 — 英文一手编译总结(GPT/Claude/Kimi)、配图(ray.so/carbon/截图美化)、thread 工具(Typefully/Hypefury)、翻译、排程分析; (e) 平台机制与涨粉 — X 算法时间线(转评赞/互动权重/外链降权)、蹭热点借势、互动与回复、build in public 涨粉、英文区搬运到中文区的信息差红利; (f) 变现(次要) — 广告 / 知识星球 / 社群 / 付费课程 / 咨询 / 导流。学派分歧: 编译搬运(英文一手翻译) vs 原创洞察、快讯资讯 vs 深度长推、锐评玩梗 vs 严肃干货、build in public vs 纯内容、全 AI 自动发 vs 人工精选。代表生态(宝玉/歸藏/向阳乔木/AI 进化论/小互/Gorden Sun 等)。不含: 英文 AI Twitter 圈(聚焦中文圈)、通用 X 增长营销、其他平台、AI 工具技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「推特 ai 博主」「推特中文 ai」「x ai 自媒体」「推特 thread」「推特爆款推文」

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

影视编剧 (Scriptwriting / Screenwriting) — 为电影 / 电视 / 流媒体剧集写戏剧蓝本的从业者认知操作系统: 决定「讲什么故事、人物是谁为何转变、场景如何被戏剧化、主题为何重要」的学科 —— 区别于导演 (调度 / 视觉实现)、制片 (融资 / 排期)、小说 (无格式 / 场景 / 视觉动作约束)。覆盖 (a) 故事与结构理论 (亚里士多德《诗学》情节 / 人物 / 思想 + 突转 peripeteia / 发现 anagnorisis + 净化 catharsis; Syd Field 范式 / 三幕 / 情节点; Freytag 金字塔; Egri 前提; McKee《故事》掌控性理念 / 鸿沟 / 价值正负转变 / 激励事件 / 渐进式复杂化; Truby《故事剖析》22 步 + 道德论证; Vogler/Campbell 英雄之旅; Blake Snyder《救猫咪》15 拍节拍表; Dan Harmon 故事环; John Yorke 五幕《进入森林》; Frank Daniel 八序列法; 起承转合东亚戏剧结构), (b) 人物 (想要 vs 需要 / 外在目标 vs 内在缺失, 人物弧光 正 / 负 / 平, flaw-wound-ghost 创伤背景, 主动 vs 被动主角的能动性, Egri 三维人物 生理 / 社会 / 心理, 反派是主角的镜子, 群像与关系网, 人物在压力下的选择中显形), (c) 对白 (潜台词 subtext, 对白即动作与冲突而非信息, 避免太直白 on the nose, 人物独特声口, 信息植入 exposition, Mamet/Sorkin 意图-阻碍式对白, 展示而非告知, 中文剧台词工艺), (d) 场景与序列工艺 (场景是有目标 / 冲突 / 转折的微型故事, 场景价值充能与转折点, 晚进早出, 八序列法, set piece, 转场, 场景头 / 动作行 / 括号提示 格式工艺), (e) 主题与前提 (掌控性理念 / 前提, 主题是被戏剧化的论证而非说教, 道德论证 Truby, 主题统一性, 这到底在讲什么), (f) 类型 (类型惯例是对观众的承诺, Snyder 10 类故事, 颠覆 vs 尊重套路, 类型片 vs 文艺片, 中国类型 主旋律 / 古装 / 年代 / 悬疑 / 甜宠 / 都市 / 军旅 / 历史正剧), (g) 格式与工业流程 (好莱坞剧本格式与 Final Draft, logline 一句话故事, treatment 故事大纲, 节拍表, 分场 / 分集大纲, spec 原创剧本 vs 委托, pitch, coverage, 美剧编剧室与 showrunner 制; 中国 大纲→人物小传→分集大纲→剧本, 长剧集 40 集结构, 网络电影 / 网大, 分账剧, 平台定制剧, 微短剧竖屏短剧), (h) 改稿与开发 (写作就是改写, 改稿 / 润色 / 推倒重写, 处理意见 / 改稿意见, 片方与平台 notes, 杀死你的宝贝, 围读, 开发地狱), (i) 改编 (IP改编 小说 / 漫画 / 游戏改编, 忠于精神而非字句, 压缩, 中国网文 IP 热), (j) 中国影视编剧产业现实 (审查 / 广电总局约束, 备案 / 立项, 平台定制剧 爱优腾芒, 分账, 编剧维权 署名权 / 欠薪 / 枪手, 注水剧, 流量 + 大IP 资本逻辑 vs 原创工艺, 导演中心制 vs 编剧话语权), (k) 编剧职业与工艺生涯 (spec vs 委托, 编剧 vs 编审 / 策划, 单兵 vs 编剧室, 在开发链条中的位置, WGA 与署名仲裁规范, 入行, 中国编剧地位与权益)。跨 电影 / 美剧流媒体 / 中国电影与长剧集。不含 导演 / 摄影 / 制片 / 融资 / 表演 / 电影理论批评为终点 / 泛小说写作 / 纪录片 / 新闻 —— 本 skill 是「戏剧化编剧」工艺: 故事 / 人物 / 场景 / 对白 / 主题 / 结构 / 格式 与围绕它们的产业流程。 (Scriptwriting / Screenwriting for film & TV (影视编剧) — the cognitive operating system of practitioners who write the dramatic blueprint of films, television, and streaming series: the discipline of deciding WHAT story is told, WHO the characters are and why they change, HOW the scenes are dramatized, and WHY it matters thematically — distinct from directing (staging/visual realization), producing (financing/scheduling), and prose fiction (which has no format/scene/visual-action constraints). Covers (a) story & structure theory (Aristotle's Poetics — plot/character/thought + reversal peripeteia/recognition anagnorisis + catharsis; Syd Field's paradigm/three-act/plot points; Freytag's pyramid; Lajos Egri's premise; Robert McKee's Story — controlling idea/the gap/value charge/inciting incident/progressive complications; John Truby's 22 steps & moral argument; Christopher Vogler/Joseph Campbell hero's journey; Blake Snyder's Save the Cat 15-beat sheet; Dan Harmon's story circle; John Yorke's 5-act Into the Woods; Frank Daniel's 8-sequence method; 起承转合 East-Asian dramatic structure), (b) character (want vs need/external goal vs internal lack, character arc positive/negative/flat, 人物弧光, flaw-wound-ghost backstory, agency active vs passive protagonist, Egri's 3-dimensional character physiology/sociology/psychology, antagonist as the protagonist's mirror, ensemble & relationship webs, character revealed through choice under pressure), (c) dialogue (subtext 潜台词, dialogue as action & conflict not information, 'on the nose' avoidance, distinct character voice, exposition handling, Mamet/Sorkin intention-obstacle dialogue, show-don't-tell, 台词 craft in Chinese drama), (d) scene & sequence craft (scene as a mini-story with goal/conflict/turn, scene value charge & turning point, enter-late-leave-early, the 8-sequence method, set pieces, transitions, slug line/action line/parenthetical format craft), (e) theme & premise (controlling idea/premise/前提, theme as dramatized argument not message, moral argument Truby, thematic unity, 'what is this really about'), (f) genre (genre conventions as audience promise, Snyder's 10 story types, subverting vs honoring tropes, 类型片 vs 文艺片, Chinese genres 主旋律/古装/年代/悬疑/甜宠/都市/军旅/历史正剧), (g) format & industry process (Holly

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

音乐制作 / 混音 (音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it in the mix' (heavy processing, 后期补救)**; **In-the-box 全数字 (ITB: DAW + 插件，召回方便，bedroom 可达专业) ⇄ 模拟硬件/outboard (analog console + 硬件，'mojo'/谐波染色 vs 召回噩梦)**; **人性化/groove/不完美 (humanize, push/pull, 'the feel') ⇄ 量化/网格/修音 (quantize to grid, pitch-correct, 'in the pocket' 靠编辑)**; (b) 核心工作流 / pipeline (最标准、最易蒸高质量+CLI 化) — 编曲制作 arrangement/production → 录音/编程 tracking/programming → 编辑 editing (comping 选段/quantize/pitch-correct/time-align) → 混音 mixing (gain staging → balance 平衡 → EQ → compression → 空间 reverb/delay → 自动化 automation → 总线/母线处理 bus/mix-bus) → 母带 mastering (响度/EQ/限制 limiting/dither/排序+间隔) → 交付 delivery (DDP/streaming spec/stems); (c) 工具栈 — DAW (Pro Tools 录音棚标准/Ableton Live 电子+现场/Logic Pro Mac 性价比/FL Studio beatmaker/Cubase/Studio One/Reaper); 插件 (EQ: FabFilter Pro-Q/SSL/API; 压缩: 1176/LA-2A/SSL bus comp 及其复刻 Waves/UAD/Plugin Alliance; 混响: Valhalla/Lexicon/Bricasti; 调音: Auto-Tune/Melodyne; 限制器 limiter: Pro-L 2/Ozone); 硬件 (监听音箱 monitors: Yamaha NS-10/Genelec; 声学处理 acoustic treatment; 转换器 converters: Apollo/RME; 话筒 mics: U47/SM7B/57); 采样/音色 (Splice/sample packs/Kontakt/Serum 合成器); (d) 知识正典 — Mixing Secrets for the Small Studio (Mike Senior)、The Mixing Engineer's Handbook / Recording Engineer's Handbook (Bobby Owsinski)、Zen and the Art of Mixing (Mixerman)、The Art of Mixing (David Gibson 可视化)、Modern Recording Techniques、Sound on Sound 杂志、Mix With The Masters 大师课、Pensado's Place; (e) figures/流派 — 混音大师 (Chris Lord-Alge CLA 摇滚/Andrew Scheps 'Stadium' 3-bus/Tony Maserati/Manny Marroquin/Serban Ghenea 流行隐形混音/Michael Brauer multing); 制作人 (Rick Rubin 减法/氛围、Quincy Jones、Dr. Dre 完美主义、Max Martin 流行结构、Jack Antonoff、Finneas bedroom→Grammy、Metro Boomin/trap、Timbaland、Pharrell); 母带 (Bob Katz K-system/响度战争批判、Bob Ludwig、Greg Calbi); 教育者 (Mike Senior、Pensado、Warren Huart Produce Like A Pro、Dan Worrall 技术深挖); (f) 行业话术/黑话 — gain staging/headroom/LUFS/true peak/comping/bouncing/printing/stems/DI/reamp/sidechain/parallel compression 并行压缩/mid-side/bus/aux/send-return/dry-wet/transient/sibilance/de-ess/pumping/mud 浑浊/harsh 刺耳/boxy/muddy/in the pocket/the pocket/quantize/swing/groove/vibe/mojo/reference track/A/B/recall/print/glue 胶水; (g) 争议/批判 — 响度战争 loudness war (Bob Katz/Loudness Penalty/streaming 归一化 LUFS 终结了吗)、修音/Auto-Tune 之争 (artistic vs cheating)、ITB vs 模拟玄学 (硬件 'warmth' 是否安慰剂、null test 盲测)、preset/AI 混音 (iZotope/LANDR/sample-based 是否毁了 craft)、bedroom producer 民主化 vs 录音棚消亡、'loudness'/over-compression、plugin 复刻 vs 真硬件、Spotify normalization 对母带的影响、过度依赖 reference/抄袭; (h) 创意 vs 技术张力是本行业 deep tacit 知识的核心 — 大量隐性 '听感' 知识难以言传，靠 reference/学徒/千小时积累。不含: 现场扩声 live sound/PA、音乐理论/作曲 composition (虽相关但聚焦录音棚后期制作)、配乐/film scoring (虽相关但聚焦歌曲制作)、纯硬件电子工程/合成器 DIY、音乐商业/版权/发行 (虽相关但聚焦制作技艺本身)。) Master OS — automated mastery of 音乐制作 / 混音 (Music Production & Mixing) — 录音棚与卧室工作室里把一首歌从编曲/录音/编程做到混音/母带成品的工程+艺术认知操作系统，面向制作人(producer)、混音师(mixing engineer)、母带工程师(mastering engineer)、beatmaker、唱作人/bedroom producer，以及想入行/服务这行(录音棚、plugin 厂商、sample 公司)的视角。覆盖: (a) 第一性张力 — **服务歌曲/情绪 (serve the song / emotion-first: 技术只为打动人，'if it sounds good it is good'，用耳朵不用眼睛) ⇄ 技术正确/工程纪律 (technical correctness: gain staging 增益结构、headroom 余量、相位 phase、监听校准、LUFS 响度规范)**; **黄金耳朵/直觉混音 (mix by ears, reference-driven, 不看分析仪) ⇄ 看表/分析仪/规则 (mix by metrics: EQ 曲线、频谱仪 spectrum analyzer、相关计 correlation meter)**; **少即是多/减法混音 (subtractive, 'less is more', 录好源头 = 混音成功一半) ⇄ 重度处理/'we'll fix it i

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

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

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

Counts and compares blog posts across a target and competitors, audits content freshness via sitemap lastmod dates, and maps competitor organic keywords (US, non-branded, informational) against the target to surface ranking gaps. Use when asked to compare blog counts, content volume, publishing cadence, content freshness, keyword mapping, keyword gap analysis, or competitor keyword reports — e.g. "how many blog posts does X have vs Y", "how fresh is content on X", "where does [target] rank for [competitor] keywords", "keyword gap between X and Y". Works from company names alone. Always use for blog comparison, freshness audits, and keyword mapping tasks.

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

Plan insurance technology adoption. TRIGGERS - Use when user needs help with insurance-technology-plan related tasks.

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

Evaluates insurtech business models with distribution innovation, underwriting technology, and claims automation. Use when analyzing insurtech, evaluating digital insurance, or assessing insurance technology.

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

The fifteen fundamental cooking techniques that together cover most home kitchen work. Organized by the transformation they perform (heat transfer, water management, emulsion, ferment, cut) rather than by cuisine. Covers knife work, sauté, sear, braise, roast, poach, boil, steam, grill, bake, stew, reduce, deglaze, emulsify, and pickle/ferment, each with the physics, the signal, the common failure, and a diagnostic question. Use when teaching a cook, substituting a technique, or diagnosing why a dish failed.

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

Research a specific technology, library, system, protocol, or tool to answer a concrete technical question with source-traceable evidence. Use when current implementation details, version behavior, configuration, compatibility, or authoritative technical facts must be verified rather than recalled. Also use when explicitly asked to incorporate verified findings into an existing skill.

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

One-click technical SEO audit of a website. Runs the full technical SEO audit SOP — crawlability, indexation, Core Web Vitals, schema markup, internal linking, mobile UX, and content quality. Outputs a prioritized fix list. Use when "SEO audit", "technical SEO", "site audit", "crawl issues", "indexation problems", "why aren't we ranking", "SEO health check", or any request to diagnose SEO issues on a website.

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

Technical SEO audit across 9 categories: crawlability, indexability, security, URL structure, mobile, Core Web Vitals, structured data, JavaScript rendering, and IndexNow protocol. Use when user says "technical SEO", "crawl issues", "robots.txt", "Core Web Vitals", "site speed", or "security headers".

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

Plan a comprehensive spectroscopic analysis campaign by defining the analytical question, assessing sample characteristics, selecting appropriate techniques using a decision matrix, planning sample preparation for each technique, sequencing analyses from non-destructive to destructive, and defining success criteria with a cross-validation strategy.

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

Perform controlled dismantling of rigid system structures while preserving essential capabilities (imaginal discs). Covers rigidity mapping, dissolution sequencing, knowledge extraction, interface archaeology, and safe decomposition of technical debt and organizational calcification. Use when assess-form classified the system as PREPARE or CRITICAL, when a system is so calcified that incremental change is impossible, when technical debt blocks all forward progress, or before adapt-architecture when the current form must be softened before it can be reshaped.

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

Evaluate and implement agricultural technology solutions. TRIGGERS - Use when user needs help with agricultural-technology related tasks.

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

Write or rewrite technical text with the rules of ASD-STE100 Simplified Technical English so it is clear, unambiguous, and free of AI slop. Use for documentation, READMEs, runbooks, procedures, error messages, release notes, incident reports, and API guides. Also use when the user says "STE", "Simplified Technical English", "ASD-STE100", "de-slop", "make this readable", "write for non-native readers", or asks for docs that translate well. Enforces the standard's 53 rules: 20/25-word sentence limits, one word one meaning, simple tenses, active voice, condition before command.

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

Entwurf einer BAG-konformen Abmahnung im Arbeitsrecht – konkrete Schilderung der Pflichtverletzung, klare Verhaltenserwartung, ausdrückliche Sanktionsandrohung. Use when AG eine verhaltensbedingte Sanktion vor einer Kündigung dokumentieren muss oder AN die Wirksamkeit einer empfangenen Abmahnung prüft.

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

Assume the role of Galyarder CTO (Chief Technology Officer). Technical guardian. Enforce technical integrity, architectural determinism, self-healing formal verification, and planetary computational leverage.

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

"Apply ethnographic methods including prolonged engagement, participant observation, thick description, and netnography to study cultures and communities. Use this skill when the user needs to design fieldwork with immersive observation, interpret cultural practices through thick description, study online communities via netnography, or when they ask 'how do I study a culture or community', 'what is participant observation', or 'how do I apply ethnography to online settings'.".

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