2,351 件 ・ 関連度順
概要と使いどころ
Use for .NET application development involving services, managers, dependency injection, Microsoft.Extensions.Hosting, dependency direction, MiniDb persistence, DTOs, Mapster mapping, shared entities/helpers, MCP tools, module workflows, solution analysis, cancellation, logging, and logic shared by CLI and Blazor.
日本語の概要は準備中です。原文の説明を表示しています。
威胁建模时使用。适用于新功能 / 新系统的安全设计评审。融合 STRIDE + Attack Tree + Microsoft SDL。
日本語の概要は準備中です。原文の説明を表示しています。
选择多工作流编排模式时使用。适用于跨工作流协同任务、决定任务串行/并行/动态规划。优先使用 Microsoft Azure 的四种 Agent 编排模式（顺序/并发/交接/动态）。
日本語の概要は準備中です。原文の説明を表示しています。
Ultimate UI/UX design intelligence: an Anti-Slop layer that kills AI tells (em-dash, AI purple glow, generic names, template layouts), tunable Design Dials (variance/motion/density) and Style Modes (functional, minimalist, brutalist, soft-premium, marketing), 161 industry color palettes in a shadcn-aligned semantic token schema, 48 UX Laws, 37 Design Tests, UX Heuristics (Nielsen + Krug), Harvester extraction, Figma & Google Stitch integration, MCP server, Component Generator, and BM25 search across 17 domains + 19 framework stacks. One command = complete design system. Use when designing or reviewing UI/UX, choosing colors/typography, fixing generic AI-looking designs, or building Web App / SaaS / Mobile screens.
日本語の概要は準備中です。原文の説明を表示しています。
Synchronizes service metadata into Spotify Backstage catalog using catalog-info.yaml generation and the Backstage Catalog REST API. Manages component, API, and system entity relationships across teams.
日本語の概要は準備中です。原文の説明を表示しています。
This skill uses OpenClaw's healthcheck workflow to inspect the host running the assistant, surface risky exposure, and turn the findings into a staged hardening plan. It is for operator-style audits with explicit approval gates, not a generic software listing or a replacement for OS administration.
日本語の概要は準備中です。原文の説明を表示しています。
Agno is a high-performance Python framework for building, running, and managing agentic software at scale. It provides a three-layer architecture — framework, runtime, and control plane — enabling developers to go from agent prototype to production API in roughly 20 lines of code.
日本語の概要は準備中です。原文の説明を表示しています。
Strategic sales leadership guidance for B2B SaaS and enterprise software companies. Covers sales strategy, team building, pipeline management, enterprise selling, discovery calls, demos, proposals, negotiations, and sales operations. Use when building sales teams, designing sales processes, improving win rates, or scaling revenue operations. Use for "sales strategy", "sales process", "pipeline review", "deal strategy", "sales hiring", "quota planning".
日本語の概要は準備中です。原文の説明を表示しています。
Expert product demonstration specialist for SaaS and B2B software. Use when preparing demos, structuring demo presentations, tailoring to stakeholders, handling objections during demos, managing live vs sandbox environments, or improving demo conversion rates. Covers remote and in-person demos, multi-stakeholder presentations, technical deep-dives, and executive briefings.
日本語の概要は準備中です。原文の説明を表示しています。
Generate structured software specifications for features, bug fixes, and products. Use when the user wants to create a spec, PRD, feature brief, requirements document, or when starting any new implementation that needs a specification first. Invoke via /spec-writer or when the user says "write a spec", "spec this out", "create a spec", "I need a spec for...", or describes a feature they want to build. Produces adaptive-complexity specs with Job Stories, Gherkin acceptance criteria, and three-tier boundaries. Output is a markdown file ready for agent execution or human review.
日本語の概要は準備中です。原文の説明を表示しています。
Network reachability and pivoting after an operator already has a foothold. Use to make previously unreachable hosts, subnets, services or listener directions reachable via Ligolo-ng, Chisel, GOST v3, SSH/native forwarding, socat/netsh, Microsoft Dev Tunnels, DNS/HTTP/QUIC fallback transports, and multi-hop routing. This module does not exploit services, obtain credentials, or own C2/persistence. Its success condition is changed reachability: the operator can route/connect to the intended internal network/service through the selected foothold.
日本語の概要は準備中です。原文の説明を表示しています。
Systematic root-cause isolation and minimal fix proposal for software bugs.
日本語の概要は準備中です。原文の説明を表示しています。
Create or update a Wardley Map of how any domain delivers value. Maps the needs it serves, the capabilities involved, how each is evolving (genesis to commodity), and strategic plays. Applies to any domain, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Map the Jobs to be Done (functional, emotional, and social) that people are trying to get done. Based on Christensen's JTBD theory — applies to any object, not only software.
日本語の概要は準備中です。原文の説明を表示しています。
Assess delivery health metrics. For software: DORA + APEX. For content/AI/service products: product-type-appropriate metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Repurpose existing content into a native Threads post or thread. Take a LinkedIn post, X thread, blog, YouTube script, or newsletter and rewrite it for Threads: warm the tone, de-corporate it, refit to a short post or light thread, rebuild the hook to clear the soft fold, strip off-platform artifacts, run the humanizer, publish via Publora on approval. Not for writing from scratch (use threads-post-writer), auditing a draft (use threads-humanizer), or a hook teardown (use threads-hook-extractor).
日本語の概要は準備中です。原文の説明を表示しています。
Use when verifying that a model in the imp inference engine produces coherent output without repetition loops, token-stuck states, or state corruption across turns or streams. Triggers on "degenerates", "check degeneration", "repetition loop", "own own own", "stuck token", "empty content", "multi-turn regression", "does it still work", "NIAH", and after enabling CUDA graphs / changing forward pass / MoE routing / KV cache or KV dtype / GDN state or scan / sparse attention / PDL / speculation (MTP, n-gram) / ragged prefill / batched-decode kernels (smallm, producer quantize) / FA2 softmax.
日本語の概要は準備中です。原文の説明を表示しています。
Write, run, or repair .NET tests that use TUnit. Use when a repo uses `TUnit`, `TUnit.Playwright`, `[Test]`, `[Arguments]`, `ClassDataSource`, `SharedType.PerTestSession`, or Microsoft.Testing.Platform-based execution.
日本語の概要は準備中です。原文の説明を表示しています。
Deconstructs SaaS operating metrics including ARR, NRR, gross retention, magic number, rule of 40, and cohort economics. Use when analyzing SaaS businesses, benchmarking software metrics, or evaluating subscription model health.
日本語の概要は準備中です。原文の説明を表示しています。
Convert files to Markdown using Microsoft's MarkItDown library
日本語の概要は準備中です。原文の説明を表示しています。
Two-step self-review at every task lifecycle phase. Step 1 (this skill) runs in-context to gather session signals — files read vs grepped, user pushback, build evidence, degradation signs. Step 2 launches a forked subagent for unbiased code/plan review with fresh eyes. Combined report classifies findings as hard blocks or soft warnings.
日本語の概要は準備中です。原文の説明を表示しています。
Semantic versioning and changelog formatting for software releases. Use when: preparing releases, updating version numbers, writing changelogs. Keywords: version, release, changelog, semver, major, minor, patch, 版本, 發布, 變更日誌.
日本語の概要は準備中です。原文の説明を表示しています。
Managing complexity is software's primary technical imperative - all other goals are secondary
日本語の概要は準備中です。原文の説明を表示しています。
Spot-check citations in library files for obvious hallucinations. Resolves DOIs against the DOI registry, validates arXiv IDs, checks the format of journal references. Soft-fails on transient lookup failures rather than blocking. Recommended after kb-ingest and as part of periodic library hygiene.
日本語の概要は準備中です。原文の説明を表示しています。