スキルを探す

Expert-level browser automation, debugging, and performance analysis using Chrome DevTools MCP. Use for interacting with web pages, capturing screenshots, analyzing network traffic, and profiling performance.

日本語の概要は準備中です。原文の説明を表示しています。

Guide for using the Microsoft Fluent UI Blazor component library (Microsoft.FluentUI.AspNetCore.Components NuGet package) in Blazor applications. Use this when the user is building a Blazor app with Fluent UI components, setting up the library, using FluentUI components like FluentButton, FluentDataGrid, FluentDialog, FluentToast, FluentNavMenu, FluentTextField, FluentSelect, FluentAutocomplete, FluentDesignTheme, or any component prefixed with "Fluent". Also use when troubleshooting missing providers, JS interop issues, or theming.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill whenever the user wants to build scroll animations, scroll effects, parallax, scroll-triggered reveals, pinned sections, horizontal scroll, text animations, or any motion tied to scroll position — in vanilla JS, React, or Next.js. Covers GSAP ScrollTrigger (pinning, scrubbing, snapping, timelines, horizontal scroll, ScrollSmoother, matchMedia) and Framer Motion / Motion v12 (useScroll, useTransform, useSpring, whileInView, variants). Use this skill even if the user just says "animate on scroll", "fade in as I scroll", "make it scroll like Apple", "parallax effect", "sticky section", "scroll progress bar", or "entrance animation". Also triggers for Copilot prompt patterns for GSAP or Framer Motion code generation. Pairs with the premium-frontend-ui skill for creative philosophy and design-level polish.

日本語の概要は準備中です。原文の説明を表示しています。

Generate three radically distinct, on-trend brand concepts for any app or product and present them as a single no-scroll hero webpage — a bento "brand book" (logo + tagline, in-app screen, out-of-home, merch, palette, type, voice) that assembles itself with a staggered pop on every toggle. Grounded in 2024-2026 design trends, not safe defaults. Triggers: "brand kit", "brand book", "brand concepts", "show me a few directions", "make it look like an agency did it", "build a brand for my app".

日本語の概要は準備中です。原文の説明を表示しています。

Terse caveman voice: answer first, fluff gone, every technical fact kept. Use for /caveman, "caveman mode", "talk like caveman", "be brief", "less tokens". Stays on until "stop caveman" or "normal mode".

日本語の概要は準備中です。原文の説明を表示しています。

Use when a coding agent (Claude Code, Cursor, Codex, Copilot CLI) burns through tokens or usage limits, sessions get slow or hit context limits, or the user asks to cut agent cost. Measures where the tokens go, then applies levers in order: session hygiene, always-loaded context (CLAUDE.md, skills, MCP), tool-output filtering, subagent delegation, output verbosity, and model/effort choice.

日本語の概要は準備中です。原文の説明を表示しています。

Compress a memory file such as CLAUDE.md or a todo list into caveman format to save input tokens, keeping a readable backup. Sends the file's text to the configured model provider. Trigger: /caveman-compress.

日本語の概要は準備中です。原文の説明を表示しています。

Use when long-lived agents, project memories, system prompts, or playbooks are repeatedly summarized, rewritten, or optimized and risk losing domain detail, provenance, or execution learnings.

日本語の概要は準備中です。原文の説明を表示しています。

Use this skill when the user explicitly asks to map, document, or onboard into an existing codebase. Trigger for prompts like "map this codebase", "document this architecture", "onboard me to this repo", or "create codebase docs". Do not trigger for routine feature implementation, bug fixes, or narrow code edits unless the user asks for repository-level discovery.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "compress context", "summarize conversation history", "implement compaction", "reduce token usage", or mentions context compression, structured summarization, tokens-per-task optimization, or long-running agent sessions exceeding context limits.

日本語の概要は準備中です。原文の説明を表示しています。

Structured decision-making framework for technical proposals and trade-off analysis. When the user faces a choice between multiple approaches (architecture decisions, tool selection, refactoring strategies, migration paths), this skill produces a 1-3-1 format: one clear problem statement, three distinct options with pros/cons, and one concrete recommendation with definition of done and implementation plan. Use when the user asks for a "1-3-1", says "give me options", or needs help choosing between competing approaches.

日本語の概要は準備中です。原文の説明を表示しています。

Refactors and reviews SwiftUI views: consistent layout ordering, subview extraction, dependency injection, Observation, and MV versus view-model patterns. Use when SwiftUI views have grown large or inconsistent.

日本語の概要は準備中です。原文の説明を表示しています。

Audits SwiftUI performance: rendering, scrolling, CPU and memory, unnecessary view updates, body re-evaluations, and layout thrashing, with Instruments guidance when code review is inconclusive. Use when a SwiftUI screen stutters, scrolls poorly, or uses too much CPU.

日本語の概要は準備中です。原文の説明を表示しています。

Drives development with tests. Use when implementing any logic, fixing any bug, or changing any behavior. Use when you need to prove that code works, when a bug report arrives, or when you're about to modify existing functionality.

日本語の概要は準備中です。原文の説明を表示しています。

Implements, adopts, and reviews iOS 26+ Liquid Glass in SwiftUI: glassEffect, GlassEffectContainer, correctness, performance, and design fit. Use when adding Liquid Glass to a SwiftUI app or refactoring existing UI to the new design language.

日本語の概要は準備中です。原文の説明を表示しています。

Use before writing code on anything non-trivial: a new project or feature, ambiguous or incomplete requirements, a change spanning multiple modules, an architectural decision, or work over ~30 minutes. Runs a gated Specify → Plan → Tasks → Implement workflow with human review at each phase. Skip for single-line fixes.

日本語の概要は準備中です。原文の説明を表示しています。

Use when turning GitHub issues or bug reports into reproducible coding-agent repair loops with sandboxed execution, focused tests, patch generation, and regression verification.

日本語の概要は準備中です。原文の説明を表示しています。

Grounds every implementation decision in official documentation. Use when you want to verify an approach against the official docs before implementing it, or when you want authoritative, source-cited code free from outdated patterns. Use when building with any framework or library where correctness matters.

日本語の概要は準備中です。原文の説明を表示しています。

This skill should be used when the user asks to "diagnose context problems", "fix lost-in-middle issues", "debug agent failures", "understand context poisoning", or mentions context degradation, attention patterns, context clash, context confusion, or agent performance degradation. Provides patterns for recognizing and mitigating context failures.

日本語の概要は準備中です。原文の説明を表示しています。

Reviews and fixes Swift concurrency: Swift 6 strict-concurrency compiler errors, Sendable conformance, actor isolation, @MainActor, and data-race safety. Use when migrating async code to Swift 6 or resolving concurrency diagnostics.

日本語の概要は準備中です。原文の説明を表示しています。

Use when deploying to production, releasing a significant user-facing change, migrating data or infrastructure, or opening a beta. Covers the pre-launch checklist, staged rollout, monitoring, and rollback planning for deployments that carry risk.

日本語の概要は準備中です。原文の説明を表示しています。

Use when unsure which engineering-workflow skill applies to the task at hand. Routes from development phase — idea, spec, plan, implement, test, review, ship — to the right skill, and shows how they chain together across a feature or bugfix.

日本語の概要は準備中です。原文の説明を表示しています。

Explains and designs Microsoft Fabric Lakehouse solutions: Delta tables, the SQL analytics endpoint, shortcuts, and AI functions. Use when building, optimizing, or documenting a Fabric Lakehouse.

日本語の概要は準備中です。原文の説明を表示しています。

Migrates Oracle PL/SQL stored procedures to PostgreSQL PL/pgSQL. Translates Oracle-specific syntax, preserves method signatures and type-anchored parameters, leverages orafce where appropriate, and applies COLLATE "C" for Oracle-compatible text sorting. Use when converting Oracle stored procedures or functions to PostgreSQL equivalents during a database migration.

日本語の概要は準備中です。原文の説明を表示しています。