8,857 件 ・ 関連度順
概要と使いどころ
Implement GitOps continuous delivery for Kubernetes using ArgoCD or Flux. Use for automated deployments with Git as single source of truth, pull-based delivery, drift detection, multi-cluster management, and progressive rollouts.
日本語の概要は準備中です。原文の説明を表示しています。
Convert .NET projects and solutions (.sln, .slnx) to NuGet Central Package Management (CPM) using Directory.Packages.props. USE FOR: converting to CPM, centralizing or aligning NuGet package versions across multiple projects, inlining MSBuild version properties from Directory.Build.props into Directory.Packages.props, resolving version conflicts or mismatches across a solution or repository, updating or bumping or syncing package versions across projects. Also activate when packages are out of sync, drifting, or inconsistent -- even without the user mentioning CPM. Provides baseline build capture, version conflict resolution, build validation with binlog comparison, and a structured post-conversion report. DO NOT USE FOR: packages.config projects (must migrate to PackageReference first) or repositories that already have CPM fully enabled.
日本語の概要は準備中です。原文の説明を表示しています。
USE ONLY for (1) two or more projects with repeated MSBuild policy, targets, or package versions, or (2) an existing Directory.Build.props/targets/rsp hierarchy with an import, placement, or layering defect. A one-project repo without an existing Directory.Build file is outside scope; do not load this skill. Covers centralizing shared policy and targets, Directory.Packages.props across projects, parent hierarchy/import structure, props-versus-targets placement, and folder/project exceptions. An existing hierarchy defect remains in scope when only one project is affected. For property value or condition semantics use property-patterns. Exclude legacy-to-SDK migration and non-MSBuild systems.
日本語の概要は準備中です。原文の説明を表示しています。
Use SharpConsoleUI to build full terminal (TUI) applications in .NET — equally suited to full-screen single-window apps and multi-window desktops with overlapping draggable windows — using a compositor, a DOM layout engine, and 40+ reactive controls (data tables, tree views, forms, an embedded PTY terminal, markdown, charts, video). USE FOR: interactive console apps, full-screen TUIs, multi-window terminal desktops, dashboards, wizards, and admin/monitoring UIs that need focus, mouse, and flicker-free rendering over local terminals or SSH; NativeAOT console tools. DO NOT USE FOR: simple line-based CLI output or argument parsing; non-interactive scripts; GUI/desktop (WPF/WinForms) or web UIs. INVOKES: inspect the project, add the SharpConsoleUI package, scaffold a window/control tree, and build/run to verify the app renders.
日本語の概要は準備中です。原文の説明を表示しています。
Manage Azure DevOps projects, work items, repos, PRs, pipelines, wikis, test plans, security alerts, variable groups, environments/approvals, branch policies, and attachments. Use when user asks to: manage sprints, create/update work items, list repos, create PRs, run pipelines, search code, manage wiki pages, check security alerts, manage variable groups, approve deployments, or configure branch policies. Covers 13 domains with 99 tools via REST API.
日本語の概要は準備中です。原文の説明を表示しています。
Implement GitOps workflows with ArgoCD and Flux for automated, declarative Kubernetes deployments with continuous reconciliation. Use when implementing GitOps practices, automating Kubernetes deployments, or setting up declarative infrastructure management.
日本語の概要は準備中です。原文の説明を表示しています。
Turn hand-made first-50 traction into self-reinforcing acquisition loops, so the next 5,000 users come from usage, not founder hours. Use when growth stalls the moment the user stops pushing, every signup traces back to a DM or one launch spike, or they're reaching for "more channels" when the real gap is that using the product creates no new users.
日本語の概要は準備中です。原文の説明を表示しています。
Implement GitOps with ArgoCD for declarative Kubernetes deployments.
日本語の概要は準備中です。原文の説明を表示しています。
Autonomous DevSecOps & FinOps Guardrails. Orchestrates Gemini 3 Flash to audit Linux Kernel patches, Terraform cost drifts, and K8s compliance.
日本語の概要は準備中です。原文の説明を表示しています。
DevOps and CI/CD expert. Use when setting up pipelines, containerizing applications, deploying to Kubernetes, or implementing release strategies. Covers GitHub Actions, Docker, K8s, Terraform, and GitOps.
日本語の概要は準備中です。原文の説明を表示しています。
AlertOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AlertOps data.
日本語の概要は準備中です。原文の説明を表示しています。
AirOps integration. Manage data, records, and automate workflows. Use when the user wants to interact with AirOps data.
日本語の概要は準備中です。原文の説明を表示しています。
Think and work like an expert MLOps Engineer. Use when a task calls for MLOps Engineer judgment. Reasons from data contracts, feature parity, evaluation gates, and rollback-readiness through MLflow/W&B registries, Feast feature stores, KServe/Triton serving, Great Expectations/TFDV validation, and Evidently PSI/KS drift monitors while treating train-serve skew, data leakage, silent degradation, and schema/concept drift as first-class failure modes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when building or editing a devopsdays event's schedule - adding talks, ignites, open spaces, breaks, and evening events to the program, or moving time slots around.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a devopsdays event that is already listed on the site has to be cancelled or postponed, and its pages need to stop advertising dates, registration, and sponsorship.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a devopsdays event has finished and the slides or video recordings need to be attached to the talk pages, or when a speaker sends a link to their deck afterwards.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a city is setting up its devopsdays event for a new year and needs its data file, pages, redirect, and asset directories created from scratch.
日本語の概要は準備中です。原文の説明を表示しています。
Use when event content or site changes are finished and need to reach devopsdays.org - covers branching, rebasing on upstream main, local preview, committing, pushing to a fork or to upstream, opening the pull request, and interpreting a failing check.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a sponsor has rebranded or sent an updated logo and it must change on current and future events without altering how they appeared at past devopsdays events.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a devopsdays event has confirmed a speaker and their talk, workshop, ignite, or keynote needs to appear on the event site - covers the speaker bio page, the talk page, the headshot, and multi-speaker talks.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a devopsdays event has sold or confirmed a sponsorship and the sponsor needs to appear on the event's site - covers both sponsors already in the shared directory and brand-new ones needing a logo and data file.
日本語の概要は準備中です。原文の説明を表示しています。
Internal — for Boundless team members only. Cross-reference Boundless indexer API data, broker telemetry, and service logs to investigate production and staging operational issues. Use when the user wants to understand why slashings happened on prod/staging, diagnose prover or service failures in deployed environments, correlate market events with broker behavior, investigate fulfillment rate drops, look at prover/service logs, or perform any analysis that requires combining on-chain indexer data with off-chain broker telemetry and CloudWatch logs. Also use when the user asks to "investigate", "diagnose", or "find root cause" for prover, service, or market issues on live networks. Do NOT use for debugging local code changes, reviewing PRs, or investigating issues in the codebase itself.
日本語の概要は準備中です。原文の説明を表示しています。
Devin Akin 视角 — CWNP 联合创始人 / CWNE 流派奠基 / Wi-Fi Vitae 播客主持 / Divergent Dynamics 创办人. 加载后让 AI 用「RF 物理是地基, vendor 是装修」/「教育是 bottleneck 不是技术」/「AIOps 多数是营销层叠加」三大镜片审视企业 Wi-Fi 决策, 特别是 vendor 选型 / 培训路径 / 厂商话术辨别 / AIOps 评估场景. 反 marketing 倾向 + 25 年 instructor 视角 + vendor-neutral 立场. 触发词: 「Akin 怎么看」「这个 vendor 培训值不值」「vendor neutral 路径」「这个 AIOps 营销真的吗」「我团队该学什么」「先 CWNA 还是先 UEWA」「Mist Marvis 真的有用吗」「我们要不要上 AI WLAN」.
日本語の概要は準備中です。原文の説明を表示しています。
小红书 AI 自媒体博主 (小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。) Master OS — automated mastery of 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。: top builders' mental models, tool stack, current workflows, jargon, and where to keep up. Trigger this skill when the user works on 小红书 AI 自媒体博主 (从业者视角) — 在小红书做『AI 赛道』内容的自媒体博主，重点是**怎么写文案、怎么制作内容**。覆盖: (a) AI 赛道选题 — AI 工具测评 / AI 绘画 / AI 教程与 prompt / AI 副业变现 / AI 资讯解读 / AI 效率，按小红书用户(偏年轻女性 + 泛知识)重构选题; (b) 文案与内容结构(核心) — 封面(第一眼/大字报/对比图)、标题(数字/痛点/好奇缺口/关键词前置)、正文(钩子开头/分点/口语化/emoji/利他价值)、标签与 SEO 关键词、CTA 与互动引导、人设 voice; (c) 内容制作工作流 — 选题(对标爆款/找选题)→标题封面→脚本或正文→制作(图文/口播/录屏/数字人)→标签发布→数据复盘迭代; (d) AI 工具用于内容生产 — 文案(豆包/Kimi/DeepSeek/GPT)、生图(即梦/MJ/可图)、口播数字人、剪辑(剪映)、封面(Canva/创可贴)、选题与 SEO(新红/千瓜/灰豚); (e) 平台机制与起号 — 推荐算法(收藏率/互动率/完播/搜索)、薯条投放、违禁词/限流/避坑、起号与涨粉、垂直度; (f) 变现(次要) — 蒲公英广告 / 知识付费 / 引流私域 / AI 工具带货。学派分歧: 图文 vs 短视频、干货教程 vs 测评种草 vs 资讯搬运、真人出镜 vs 数字人/无人起号、原创 vs 搬运洗稿、AI 全自动批量 vs AI 辅助精做。不含: 通用小红书运营(已有 xiaohongshu-ops skill, 本 skill 聚焦 AI 赛道 + 文案/内容生产)、电商带货全流程、其他平台、AI 工具本身的技术原理。 problems and wants industry-grade thinking, tool selection, or workflow guidance. 触发词：「小红书 ai 博主」「小红书 ai 自媒体」「小红书 ai 赛道」「小红书爆款文案」「小红书 ai 教程」
日本語の概要は準備中です。原文の説明を表示しています。