2,398 件 ・ 関連度順
概要と使いどころ
TypeScript best practices: strict mode, ESLint rules, file naming, imports, type safety, Zod validation, error handling, and testing with Vitest. Use when writing TypeScript code, reviewing for code quality, fixing lint errors, creating types/interfaces, writing tests, or adding validation.
日本語の概要は準備中です。原文の説明を表示しています。
Silently restructures the user's natural-language prompt into the format the model CURRENTLY running this skill handles best, then answers. On activation it identifies which model family is executing it (Claude, GPT, Gemini, Llama, DeepSeek, Mistral, Qwen, Grok, Perplexity, Kimi, GLM, Command, Nova, or Phi) and loads that one model's official strategy — so the optimization always matches the model that actually runs it. Activate with /prompt-refine. Use when users want better answers without learning prompt engineering.
日本語の概要は準備中です。原文の説明を表示しています。
Monitors AWS CloudFormation stacks for configuration drift using the AWS SDK DetectStackDrift and DescribeStackResourceDrifts APIs. Generates remediation templates and integrates with AWS Config rules for continuous compliance.
日本語の概要は準備中です。原文の説明を表示しています。
Validates Ansible playbooks and roles using ansible-lint and yamllint APIs. Enforces best practices for idempotency, variable naming, and handler usage with custom rule profiles.
日本語の概要は準備中です。原文の説明を表示しています。
Give an agent a portable Git workflow playbook for branch strategy, commit hygiene, pull requests, merge choices, and CI-aware collaboration.
日本語の概要は準備中です。原文の説明を表示しています。
Expert support operations guidance for customer service excellence. Use when designing ticket management systems, creating SLA policies, building support tier structures (L1/L2/L3), optimizing knowledge bases, defining severity levels and escalation procedures, implementing support metrics (CSAT, FRT, TTR, FCR), configuring support tool stacks, or building support-to-CS feedback loops. Covers Zendesk, Intercom, Freshdesk, and help desk best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Expert sales operations and analytics guidance for revenue teams. Use when designing CRM workflows, building sales dashboards, optimizing pipeline analytics, creating lead routing rules, designing territories, calculating commissions, managing data quality, building forecasting models, or integrating sales tech stack. Covers Salesforce, HubSpot, Outreach, Gong, and RevOps best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Expert logging guidance based on Boris Tane's loggingsucks.com philosophy. Use when implementing logging, adding observability, debugging production issues, or reviewing code that includes log statements. Covers wide events architecture, structured logging, smart sampling, and high-cardinality field design.
日本語の概要は準備中です。原文の説明を表示しています。
当用户明确要求搜索、寻找、查找或推荐某个领域的 Agent Skill 时使用。对候选 Skill 进行多来源检索与比较后给出推荐。⚠️ 不适用：只想查看已有技能列表，或没有明确搜索/推荐意图。
日本語の概要は準備中です。原文の説明を表示しています。
Babel internal issue protocol — create a labeled handoff between pipeline agents. Writes designs/<name>/.handoff/<label>.md and appends to handoff_log.jsonl; best-effort gh issue create if gh available. Triggered by every guru/architect agent at handoff time.
日本語の概要は準備中です。原文の説明を表示しています。
Babel internal issue protocol — list open handoffs by label. Scans designs/*/.handoff/*.md (filtered by label) and best-effort merge with gh issue list. Used by all guru/architect agents at startup to pick up work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user wants a research-paper figure Skill Factory: build, patch, package, or use reusable specialized paper-figure-making skills from lawful literature/corpus evidence. Generated skills must use a specialized-skill-first workflow, full-feasible local PDF coverage where available, startup-plan-only first replies, target-paper candidate/final image isolation, mandatory image-embedded visual-structure explanation, mandatory non-target concept/modeling example display for abstract visual decisions, saved subtype/style illustration atlases, ChatGPT web Create image / ChatGPT Images 2.0 rendering, Codex $imagegen-first rendering, sample-image transfer rules, all-step/current-position state footers, and a mandatory first-round diverse candidate board followed by P6b/P6c paper-local best-practice optimization before final prompt construction.
日本語の概要は準備中です。原文の説明を表示しています。
Content, animation and effects best practices
日本語の概要は準備中です。原文の説明を表示しています。
Router for all Remotion skills
日本語の概要は準備中です。原文の説明を表示しています。
Security review skill: comprehensive security checklist and patterns. Use when adding authentication, handling user input, working with secrets, or creating API endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Backend development patterns for services, error handling, logging, caching. Use when building backend services, APIs, or microservices.
日本語の概要は準備中です。原文の説明を表示しています。
DevOps patterns: containerization, CI/CD, deployment strategies, monitoring. Use when containerizing apps, setting up pipelines, or deploying services.
日本語の概要は準備中です。原文の説明を表示しています。
Database design, query optimization, migrations, and indexing. Use when designing schemas, writing queries, or managing migrations.
日本語の概要は準備中です。原文の説明を表示しています。
Native app development strategies including iOS/macOS (Apple platforms), Tauri desktop apps. Use when developing native mobile or desktop applications.
日本語の概要は準備中です。原文の説明を表示しています。
Session lifecycle management. Parent skill for session-related skills: learning (pattern extraction) and compact (context compression).
日本語の概要は準備中です。原文の説明を表示しています。
Research-before-coding workflow: systematically search existing solutions before custom implementation. Use when introducing new libraries, tools, or solving unfamiliar problems.
日本語の概要は準備中です。原文の説明を表示しています。
Extracts reusable patterns from sessions. Use at session end to capture debugging insights and project-specific knowledge.
日本語の概要は準備中です。原文の説明を表示しています。
Testing strategies and methodologies including TDD and E2E testing. Use when writing tests, implementing TDD workflow, or setting up E2E test infrastructure.
日本語の概要は準備中です。原文の説明を表示しています。
Frontend patterns: component design, state management, performance, accessibility. Use when building web frontends, components, or client-side apps.
日本語の概要は準備中です。原文の説明を表示しています。