3,125 件 ・ 関連度順
概要と使いどころ
Configures GKE observability, including Cloud Logging, Cloud Monitoring, and managed Prometheus. Use when configuring GKE monitoring, setting up GKE logging, or configuring Prometheus metrics collection. Don't use to configure local application logging frameworks or external APMs outside GKE.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when configuring, applying, or troubleshooting NPSP Engagement Plans — the framework that automatically generates standard Salesforce Task records on a timed schedule to guide donor stewardship and constituent outreach. Trigger keywords: engagement plan, donor stewardship tasks, NPSP task automation, engagement template, major donor follow-up. NOT for designing the cultivation and stewardship stages — use admin/fundraising-process-mapping. NOT for recording and receipting gifts — use admin/gift-entry-and-processing.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill to select the right Salesforce integration pattern — from point-to-point to event-driven to hub-and-spoke — by applying the official Salesforce two-axis decision framework (integration type × timing) to a business integration scenario. Trigger keywords: integration pattern decision, choose integration approach, Salesforce integration architecture, when to use platform events vs API, integration type selection. NOT for implementation of any specific integration pattern (use domain-specific integration skills), MuleSoft architecture (use architect/mulesoft-anypoint-architecture), or middleware vendor selection. More triggers: integration decision record, Bulk API vs REST for a nightly load, external Id upsert, Named Credential vs Remote Site Setting, platform event vs CDC, who calls whom.
日本語の概要は準備中です。原文の説明を表示しています。
Detects analytics or tracking SDKs present without the required App Tracking Transparency prompt, enforcing Guideline 5.1.2(i) which requires user consent before any cross-app or cross-site tracking.
日本語の概要は準備中です。原文の説明を表示しています。
Detects usage of private Apple APIs, undocumented frameworks, and runtime introspection patterns that bypass the public SDK, enforcing Guideline 2.5.1. Private API usage causes automated binary rejection at upload.
日本語の概要は準備中です。原文の説明を表示しています。
Explore and debate options with fresh documentation and research before committing. Use when facing a real decision with multiple plausible approaches — library/framework choice, architecture call, API or schema design, algorithm selection, or any communication / strategy call where being wrong has cost. Enumerates relevant research domains, looks up current docs and evidence-based methods, weighs options on correctness and elegance, resists bloat. Do NOT use for divergent ideation (brainstorm), extracting user intent (elicit), or reviewing already-written code (quality-review).
日本語の概要は準備中です。原文の説明を表示しています。
Add a short, project-specific rule, convention, or override to .unikit/RULES.md — the quick-capture inbox for this project's rules (common rules always load; topic files in .unikit/rules/ load when the work matches), automatically loaded by /unikit-implement (later promotable via /unikit-memory migrate-rules). Works only with a rule typed as a prompt — it does NOT read files, folders, URLs, or PDFs. Cross-checks against the knowledge base (RULES_INDEX.md) to avoid duplicating core/stack entries. Use for fast, one-line conventions and corrections: "add a rule", "remember this", "convention", "always do X", "never use Y", "from now on do Z", or when the user corrects agent behavior and wants it remembered; also "split the rules into topics" (optimise), "clean up the rules" (prune), "shorten RULES.md" (compact). If the user points to a source (file, folder, URL, PDF, article, book) or wants to research/document framework usage, use /unikit-memory; for architecture decisions use ARCHITECTURE.md.
日本語の概要は準備中です。原文の説明を表示しています。
Perform a code review on {{engine_name}} {{engine_code_language}} code. Checks for bugs, security issues, performance problems, and best practices against the project's coding rules, design principles, and framework-specific conventions. Supports four modes — staged changes, a pull request, a commit range, or individual files. Use when the user says "review code", "check my code", "code review", "review PR", "review staged changes", "review these commits", or "is this code okay". Optional +check flag validates findings via a fresh-context subagent.
日本語の概要は準備中です。原文の説明を表示しています。
เตรียมสัมภาษณ์งาน — STAR framework, behavioral Q&A, "เล่าเรื่องตัวเอง", 50 common Q, salary negotiation
日本語の概要は準備中です。原文の説明を表示しています。
AI Growth Hacker — north star metric, AARRR funnel, viral loop, experimentation framework, retention hook สำหรับ startup และ e-commerce ไทย
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive tarot expert covering Major and Minor Arcana, spreads, symbolism, and interpretative frameworks from Rider-Waite to Thoth traditions
日本語の概要は準備中です。原文の説明を表示しています。
Dream analysis expert covering Jungian, Freudian, and symbolic interpretation frameworks
日本語の概要は準備中です。原文の説明を表示しています。
Write, restructure, or review documentation — tutorials, how-to guides, reference pages, concept/explanation docs, API references, READMEs, changelogs, release notes, and troubleshooting guides. Distills documentation craft from Mintlify's guides (compiled from technical writers at Stripe, GitHub, Amplitude, and Anaconda), the Diátaxis framework (including the compass and per-type voice), the Google and Microsoft style guides, Every Page Is Page One, Write the Docs, and Docs for Developers: audience analysis, content-type selection, style and word-level rules, procedure writing, structure for humans and AI agents, code-example standards, page templates (templates.md), mechanical enforcement and llms.txt (mechanics.md), maintenance, and success metrics. Use this skill when the user asks to "write docs", "document this feature", "improve this page", "review these docs", "write a tutorial / how-to / reference page", "structure the docs", "write API documentation", "write a README / changelog", or when authoring any file under a `docs/` tree. For SKMTC docs specifically, this skill governs the *craft* (what makes the page good); the content split between skills, `llms.md`, and the docs tree is governed by `docs/skills/README.md`. Distinct from `skmtc-retro` (captures observations about work) and the `skmtc-*` operational skills (guide doing the work) — this skill guides writing *about* the work for readers.
日本語の概要は準備中です。原文の説明を表示しています。
Building production-quality CLI tools with Cobra command framework and Viper configuration management
日本語の概要は準備中です。原文の説明を表示しています。
Web browser game development principles. Framework selection, WebGPU, optimization, PWA.
日本語の概要は準備中です。原文の説明を表示しています。
Architectural decision-making framework. Requirements analysis, trade-off evaluation, ADR documentation. Use when making architecture decisions or analyzing system design.
日本語の概要は準備中です。原文の説明を表示しています。
Python development principles and decision-making. Framework selection, async patterns, type hints, project structure. Teaches thinking, not copying.
日本語の概要は準備中です。原文の説明を表示しています。
Node.js development principles and decision-making. Framework selection, async patterns, security, and architecture. Teaches thinking, not copying.
日本語の概要は準備中です。原文の説明を表示しています。
Migrate API controller scope checks to framework-enforced authorization policies while preserving ownership checks.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive AI prompt engineering safety review and improvement prompt. Analyzes prompts for safety, bias, security vulnerabilities, and effectiveness while providing detailed improvement recommendations with extensive frameworks, testing methodologies, and educational content.
日本語の概要は準備中です。原文の説明を表示しています。
Database Architect skill. Use this when you need to modify the database schema, add tables, or seed data. This project uses RAW SQL SCRIPTS orchestrated by .NET Aspire, NOT Entity Framework Migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive Mastra framework guide. Teaches how to find current documentation, verify API signatures, and build agents and workflows. Covers documentation lookup strategies (embedded docs, remote docs), core concepts (agents vs workflows, tools, memory, RAG), TypeScript requirements, and common patterns. Use this skill for all Mastra development to ensure you're using current APIs from the installed version or latest documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Apply this opinionated workflow when modernizing legacy systems: strangler fig pattern, branch by abstraction, characterization tests, incremental monolith decomposition, framework upgrades, feature-flagged migration with rollback.
日本語の概要は準備中です。原文の説明を表示しています。
Vitest fast unit testing framework powered by Vite with Jest-compatible API. Use when writing tests, mocking, configuring coverage, or working with test filtering and fixtures.
日本語の概要は準備中です。原文の説明を表示しています。