2.7万 件 ・ 関連度順
概要と使いどころ
Track what a competitor actually shipped — "watch this competitor", "track what they ship", "what changed at". Compares against the last snapshot and reports only real moves: launches, pricing changes, positioning shifts.
日本語の概要は準備中です。原文の説明を表示しています。
Pull quotable lines from a source — "pull quotes from this", "give me quotes from this interview", "find the quotable lines", "best lines from this transcript". Reads pasted text directly or extracts from long documents.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim UI Styling Intelligence — shadcn/ui components, Tailwind CSS, CSS architecture, responsive design, dark mode, accessibility-compliant styling (WCAG 2.1 AA), animation and motion design, theming systems. Activate for component building, layout implementation, theme customization, dark mode, CSS architecture decisions, UI polish. Powered by Maxim behavioral science + Fitts' Law + Color Psychology.
日本語の概要は準備中です。原文の説明を表示しています。
UX and interaction design — UI, interface, wireframe, mockup, prototype, user experience, user journey, usability, accessibility audit, onboarding flow. The "how users think and move through it" domain.
日本語の概要は準備中です。原文の説明を表示しています。
Maxim Design System Intelligence — token architecture (primitive→semantic→component), component library governance, CSS variable systems, Tailwind integration, design-to-code handoff, Storybook, Figma token export. Activate for design system creation, token audits, component specs, dark mode systems, brand-to-token sync. Powered by Maxim behavioral science + Atomic Design + TOGAF governance.
日本語の概要は準備中です。原文の説明を表示しています。
Status overview of an .aiwork/ task folder — what is done, what is awaiting the human, what is blocked, and the one next action. Auto-detects the most recent task folder when no argument is given.
日本語の概要は準備中です。原文の説明を表示しています。
Structure AI work artifacts under .aiwork/{YYYY-MM-DD}_{slug}/ folders using the project's protocol (intent, triage, research, spec, prd, areas, plan, review, notes, docs/). Use when the user asks to plan, capture an intent, make a spec, triage, research a task, write a report, code review, summarize findings, save the work, document decisions, record this, write that down, persist findings, or references any path under .aiwork/. Also use when starting a non-trivial task that needs a plan or spec before implementation, or when finishing one and capturing notes.
日本語の概要は準備中です。原文の説明を表示しています。
Create a feature branch from an Azure DevOps ticket. Fetches ticket title, slugifies, creates `feature/<id>-<slug>`, and optionally transitions ticket to Active. Trigger when user says "feature branch", "create branch", "/dev-azdo:feature-branch", or provides a ticket id/URL to start work on.
日本語の概要は準備中です。原文の説明を表示しています。
Automate browser interactions, test web pages and work with Playwright tests.
日本語の概要は準備中です。原文の説明を表示しています。
Test-driven development. Use when the user wants to build features or fix bugs test-first, mentions "red-green-refactor", or wants integration tests.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when the user asks to test, verify, interact with, or automate web pages and browsers. Trigger for requests involving Chrome automation, browser testing, web scraping, screenshot capture, element selection, or checking web applications. Also trigger when user mentions "browser tools" explicitly.
日本語の概要は準備中です。原文の説明を表示しています。
PostgreSQL-specific code review assistant focusing on PostgreSQL best practices, anti-patterns, and unique quality standards. Covers JSONB operations, array usage, custom types, schema design, function optimization, and PostgreSQL-exclusive security features like Row Level Security (RLS).
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive guide for creating professional UI/UX designs in Penpot using MCP tools. Use this skill when: (1) Creating new UI/UX designs for web, mobile, or desktop applications, (2) Building design systems with components and tokens, (3) Designing dashboards, forms, navigation, or landing pages, (4) Applying accessibility standards and best practices, (5) Following platform guidelines (iOS, Android, Material Design), (6) Reviewing or improving existing Penpot designs for usability. Triggers: "design a UI", "create interface", "build layout", "design dashboard", "create form", "design landing page", "make it accessible", "design system", "component library".
日本語の概要は準備中です。原文の説明を表示しています。
Visual whiteboard collaboration for Copilot CLI. Creates an interactive whiteboard that opens in your browser — draw, sketch, add sticky notes, then share everything back with Copilot. Copilot sees your drawings and text, and responds with analysis, suggestions, and ideas.
日本語の概要は準備中です。原文の説明を表示しています。
Python JSON parsing best practices covering performance optimization (orjson/msgspec), handling large files (streaming/JSONL), security (injection prevention), and advanced querying (JSONPath/JMESPath).
日本語の概要は準備中です。原文の説明を表示しています。
End-to-end skill for building, testing, linting, versioning, and publishing a production-grade Python library to PyPI. Covers all four build backends (setuptools+setuptools_scm, hatchling, flit, poetry), PEP 440 versioning, semantic versioning, dynamic git-tag versioning, OOP/SOLID design, type hints (PEP 484/526/544/561), Trusted Publishing (OIDC), and the full PyPA packaging flow. Use for: creating Python packages, pip-installable SDKs, CLI tools, framework plugins, pyproject.toml setup, py.typed, setuptools_scm, semver, mypy, pre-commit, GitHub Actions CI/CD, or PyPI publishing.
日本語の概要は準備中です。原文の説明を表示しています。
Guide users through creating high-quality GitHub Copilot prompts with proper structure, tools, and best practices.
日本語の概要は準備中です。原文の説明を表示しています。
Comprehensive technology-agnostic prompt generator for documenting end-to-end application workflows. Automatically detects project architecture patterns, technology stacks, and data flow patterns to generate detailed implementation blueprints covering entry points, service layers, data access, error handling, and testing approaches across multiple technologies including .NET, Java/Spring, React, and microservices architectures.
日本語の概要は準備中です。原文の説明を表示しています。
Microsoft Store Developer CLI (msstore) for publishing Windows applications to the Microsoft Store. Use when asked to configure Store credentials, list Store apps, check submission status, publish submissions, manage package flights, set up CI/CD for Store publishing, or integrate with Partner Center. Supports Windows App SDK/WinUI, UWP, .NET MAUI, Flutter, Electron, React Native, and PWA applications.
日本語の概要は準備中です。原文の説明を表示しています。
Interface for MCP (Model Context Protocol) servers via CLI. Use when you need to interact with external tools, APIs, or data sources through MCP servers, list available MCP servers/tools, or call MCP tools from command line.
日本語の概要は準備中です。原文の説明を表示しています。
Four-phase framework for onboarding enterprise customers from contract to value realization. Use when implementing new enterprise customers, preventing churn during onboarding, or solving the adoption cliff that kills deals post-go-live. Includes the Week 4 ghosting pattern.
日本語の概要は準備中です。原文の説明を表示しています。
Get best practices for JUnit 5 unit testing, including data-driven tests
日本語の概要は準備中です。原文の説明を表示しています。
Get best practices for developing applications with Spring Boot and Kotlin.
日本語の概要は準備中です。原文の説明を表示しています。
Generate a complete Model Context Protocol server project in Java using the official MCP Java SDK with reactive streams and optional Spring Boot integration.
日本語の概要は準備中です。原文の説明を表示しています。