1,309 件 ・ 関連度順
概要と使いどころ
Analyze Ascend NPU schedule, operator dispatch, operator launch, and Host Bound profiling issues in Ascend profiling data. Use when need to diagnose device Free time, framework/operator dispatch latency, launch latency, PYTORCH_API/CANN_API launch gaps, aclrtSynchronizeStream stalls, task queue behavior, CPU scheduling interference, GC/lock pauses, CPU affinity, or schedule-side optimization actions.
日本語の概要は準備中です。原文の説明を表示しています。
Generate images using the brand's visual identity and Gemini API. Reads brand/creative-kit.md for visual style, crafts narrative prompts, and produces images via Nano Banana Pro (gemini-3-pro-image-preview). Supports on-brand and freestyle modes. Use when the user needs a blog header, social graphic, product shot, hero image, banner, thumbnail, or any generated image. Also use proactively when building content that would benefit from visuals. Triggers on "generate image", "create image", "make me an image", "blog header", "social graphic", "product shot", "hero image", "banner", "thumbnail", "I need an image", "visual for", or any request for generated artwork. Even if they just say "image" or "picture for this" — this is the skill.
日本語の概要は準備中です。原文の説明を表示しています。
Optimizes multi-step conversion flows including signup, onboarding, upgrade, and checkout. Maps each step, identifies friction and drop-off risks, then recommends specific copy/UX changes with A/B test plans. Use when someone says 'signup flow', 'onboarding optimization', 'checkout conversion', 'paywall optimization', 'activation rate', 'funnel analysis', 'why are users dropping off', 'registration flow', 'trial conversion', 'free to paid', 'upgrade flow', 'user journey', or wants to improve any multi-step user journey. If they mention steps, screens, or a sequence that leads to signup, payment, or activation, this is the skill. Even casual mentions like 'users aren't finishing signup' or 'our onboarding sucks' should trigger this. Use this instead of page-cro when the problem spans multiple screens rather than a single page.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `NetArchTest.Rules` library for architecture rules in .NET unit tests. Use when a repo wants lightweight, fluent architecture assertions for namespaces, dependencies, or layering.
日本語の概要は準備中です。原文の説明を表示しています。
Use the free first-party `dotnet format` CLI for .NET formatting and analyzer fixes. Use when a .NET repo needs formatting commands, `--verify-no-changes` CI checks, or `.editorconfig`-driven code style enforcement.
日本語の概要は準備中です。原文の説明を表示しています。
Use free built-in .NET maintainability analyzers and code metrics configuration to find overly complex methods and coupled code. Use when a repo needs cyclomatic complexity checks, maintainability thresholds, or complexity-driven refactoring gates.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `StyleCop.Analyzers` package for naming, layout, documentation, and style rules in .NET projects. Use when a repo wants stricter style conventions than the SDK analyzers alone provide.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `CSharpier` formatter for C# and XML. Use when a .NET repo intentionally wants one opinionated formatter instead of a highly configurable `dotnet format`-driven style model.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `ArchUnitNET` library for architecture rules in .NET tests. Use when a repo needs richer architecture assertions than lightweight fluent rule libraries usually provide.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `Roslynator` analyzer packages and optional CLI for .NET. Use when a repo wants broad C# static analysis, auto-fix flows, dead-code detection, optional CLI checks, or extra rules beyond the SDK analyzers.
日本語の概要は準備中です。原文の説明を表示しています。
Use the free built-in .NET SDK analyzers and analysis levels with gradual Roslyn warning promotion. Use when a .NET repo needs first-party code analysis, `EnableNETAnalyzers`, `AnalysisLevel`, or warning-as-error policy wired into build and CI.
日本語の概要は準備中です。原文の説明を表示しています。
Use a repo-root `.editorconfig` to configure free .NET analyzer and style rules. Use when a .NET repo needs rule severity, code-style options, section layout, or analyzer ownership made explicit. Nested `.editorconfig` files are allowed when they serve a clear subtree-specific purpose.
日本語の概要は準備中です。原文の説明を表示しています。
Use the open-source free `Meziantou.Analyzer` package for design, usage, security, performance, and style rules in .NET. Use when a repo wants broader analyzer coverage with a single NuGet package.
日本語の概要は準備中です。原文の説明を表示しています。
Plan transition from freelancer to agency with scaling. TRIGGERS - Use when user needs help with agency-builder related tasks.
日本語の概要は準備中です。原文の説明を表示しています。
Verify a PCBA BOM and proposed components before circuit or placement freeze, including exact manufacturer part numbers, pin semantics, packages, footprints, CAD and 3D models, lifecycle, live stock, MOQ, assembly class, price, and approved substitutes. Use for sourcing locks, unavailable or expensive parts, JLCPCB/LCSC matching, BOM risk, or cost-aware substitution decisions.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Use when you need deep host + certificate reconnaissance for an IP or need to run a Censys search query. Returns services, TLS certificates, ASN, and location. Free tier is severely limited (250 queries/month) — use sparingly. Retrieval only.
日本語の概要は準備中です。原文の説明を表示しています。
You are an expert in in-app paywalls and upgrade flows. Your goal is to convert free users to paid, or upgrade users to higher tiers, at moments when they've experienced enough value to justify the commitment.
日本語の概要は準備中です。原文の説明を表示しています。
Generate production-ready business documents including freelance contracts, project proposals, SOWs, NDAs, and MSAs with jurisdiction-aware clauses. Covers US (Delaware), EU (GDPR), UK, and DACH (German law) legal frameworks. Includes contract templates, clause libraries, and DOCX conversion. Use when starting client engagements, writing proposals, drafting partnership agreements, or needing GDPR-compliant data processing addenda.
日本語の概要は準備中です。原文の説明を表示しています。
"Apply Stakeholder Theory (Freeman, 1984) and the Mitchell et al. (1997) salience model to identify, classify, and prioritize stakeholders based on power, legitimacy, and urgency. Use this skill when the user needs to map stakeholders for a project or strategy, determine which stakeholders demand immediate attention, balance competing stakeholder interests, or when they ask 'who are our key stakeholders', 'how do we prioritize conflicting demands', or 'which stakeholders can block this initiative'.".
日本語の概要は準備中です。原文の説明を表示しています。
Restrict file edits to a specific directory for the session. (gstack).
日本語の概要は準備中です。原文の説明を表示しています。
"Apply organizational ecology (Hannan and Freeman) to analyze population-level dynamics of organizational founding, failure, and selection. Use this skill when the user needs to explain industry-level patterns of birth and death rates, analyze structural inertia and liabilities of newness or aging, evaluate why adaptation is rare relative to selection, or when they ask 'why do most startups fail', 'why is this industry dominated by old firms', or 'why do organizations resist change despite environmental pressure'.".
日本語の概要は準備中です。原文の説明を表示しています。
Fix bugs and technical debt with minimal ceremony. Issue GitHub optional — provide one for traceability or work free-form. Replaces /issue-fix.
日本語の概要は準備中です。原文の説明を表示しています。
Writing rules for the regelrecht docs site (docs/). Use when writing or editing prose under docs/ — RFCs, guides, component docs, concept pages, and the NL/EN landing copy. Keeps docs prose free of AI-generated tells and consistent with the site's government-technical register. Not for code, commit messages, or PR descriptions.
日本語の概要は準備中です。原文の説明を表示しています。