「cover」の検索結果

Use when the user wants to design, redesign, shape, critique, audit, polish, clarify, distill, harden, optimize, adapt, animate, colorize, extract, or otherwise improve a frontend interface. Covers websites, landing pages, dashboards, product UI, app shells, components, forms, settings, onboarding, and empty states. Handles UX review, visual hierarchy, information architecture, cognitive load, accessibility, performance, responsive behavior, theming, anti-patterns, typography, fonts, spacing, layout, alignment, color, motion, micro-interactions, UX copy, error states, edge cases, i18n, and reusable design systems or tokens. Also use for bland designs that need to become bolder or more delightful, loud designs that should become quieter, live browser iteration on UI elements, or ambitious visual effects that should feel technically extraordinary. Not for backend-only or non-UI tasks.

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

Safely evolve shared contracts with consumer discovery, migration tests, versioning checks, and downstream spec cascade validation

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

Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.

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

Applies battle-tested clean code principles to writing, reviewing, and refactoring code. Covers naming, functions, comments, error handling, class design, and the critical difference between clever code and clear code.

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

Bootstrap a new Gradle module in any Kotlin Android project. Walks the user through choosing one of three module types — library module (`com.android.library`), feature module (regular Android library that hosts a feature/UI, install-time only), or dynamic feature module (`com.android.dynamic-feature`, on-demand/conditional/instant delivery). Use whenever the user wants to add a module, modularize code, extract a util/data/ui layer, create a new feature, set up Play Feature Delivery, or asks "should this be a library or feature module?". Discovers the project's existing conventions (plugin aliases, namespaces, sibling modules, version catalog) instead of hardcoding any. Pushes back on bad combos (e.g. utility code in a dynamic feature). Stops at scaffolding; app-level wiring is out of scope.

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

Apply Gang of Four design patterns to solve architectural problems in TypeScript. Use when refactoring code architecture, implementing extensible systems, decoupling components, or following SOLID principles. Covers all 22 GoF patterns: Creational (Factory Method, Abstract Factory, Builder, Prototype, Singleton), Structural (Adapter, Bridge, Composite, Decorator, Facade, Flyweight, Proxy), and Behavioral (Chain of Responsibility, Command, Iterator, Mediator, Memento, Observer, State, Strategy, Template Method, Visitor).

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

Use Kanpeki component library in React projects. Activate when user wants to add, use, customize, or compose accessible UI components from Kanpeki (@kanpeki/*). Covers installation, component patterns, forms, theming, and dark mode with React Aria Components + Tailwind CSS 4.1 + CVA.

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

Apply SOLID principles to write flexible, maintainable, and testable code. Use when designing classes, interfaces, and module boundaries. Covers Single Responsibility, Open/Closed, Liskov Substitution, Interface Segregation, and Dependency Inversion with practical TypeScript examples and detection heuristics.

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

Continuous self-improvement through systematic logging, pattern detection, and behavioral updates. Use when: the owner corrects you, a task fails, you discover a better approach, or you notice a recurring pattern. Store raw learnings in .learnings/, update the specific skill or workflow that caused the issue when appropriate, and avoid vague promises to do better.

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

Schedule meetings, parse meeting notes, extract action items. Three distinct intents covered. Invoke when user mentions a specific meeting (past or future) by name or context. NOT for general calendar checks (use direct calendar.py), NOT for time-zone math. Triggers: "schedule with X", "minutes of the X meeting", "action items from yesterday's meeting", "prep me for meeting with X".

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

Set up a monday.com account for an OpenClaw agent and work with monday.com boards, items, and updates via the GraphQL API or MCP server. Use when: creating a monday.com workspace for a PA, connecting the PA to monday.com, querying boards and items, creating or updating items, troubleshooting monday.com API access, self-registering an agent on monday.com via HATCHA agent verification, or integrating with monday.com workflows. Covers GraphQL cookbook, column types, MCP configuration, and HATCHA self-registration. Works with any LLM model.

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

Use when building, updating, or styling any monday Builders presentation, slide deck, internal pitch, kickoff doc, or HTML deliverable that should match the official Builders brand. Provides the canonical color palette, typography, gradient stroke, cover decorations, card patterns, and layout primitives sourced from the 2026 Builders Kickoff master deck. Invoke when user mentions "Builders deck", "Builders style", "match the deck", "make it on-brand", "kickoff style", or asks to design a slide/page that should look like internal monday Builders material.

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

Generate and send a daily briefing to your owner covering today's meetings, urgent emails, open tasks, and anything that needs attention. Use when: it's the start of the owner's day, when asked for a summary, or on a scheduled cron job.

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

Unified workspace maintenance skill. Covers: (1) backing up the workspace to GitHub git repo, and (2) updating OpenClaw and skills. Use when: asked to backup, push to git, update openclaw, update skills, or run maintenance.

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

Use when working with Crowdstrike — crowdStrike Falcon endpoint detection and response, threat intelligence, host management, and incident investigation. Covers detection queries, host inventory, IOC searches, real-time response sessions, and vulnerability assessment. Use when investigating security incidents, reviewing endpoint health, analyzing threat detections, or managing CrowdStrike Falcon sensors.

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

Use when working with Cronofy — cronofy calendar API platform management covering calendars, events, availability, scheduling, and account sync health. Use when monitoring calendar integrations, analyzing scheduling patterns, reviewing availability rules, managing connected accounts, or troubleshooting Cronofy calendar sync issues.

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

Use when working with Courier — courier notification orchestration platform management covering messages, templates, brands, users, and delivery analytics. Use when monitoring notification delivery, analyzing template performance, reviewing delivery logs, managing notification preferences, or troubleshooting Courier notification issues.

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

Use when working with Dbt — dbt (data build tool) project management and monitoring. Covers model runs, test results, source freshness, documentation generation, manifest analysis, and dbt Cloud API integration. Use when checking dbt run status, investigating test failures, analyzing model lineage, or managing dbt Cloud jobs.

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

Use when working with Detox — detox React Native testing management and analysis. Covers test configuration review, device and simulator management, build configuration analysis, test result parsing, artifact collection, and test runner integration. Use when managing Detox test suites, investigating mobile test failures, or reviewing React Native E2E testing configurations.

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

Use when working with Device42 — device42 IT infrastructure management covering data center infrastructure management (DCIM), application dependency mapping, IP address management, and asset lifecycle tracking. Use when documenting data center rack layouts and power chains, mapping application dependencies and communication flows, managing IP address allocation and subnets, or tracking hardware assets from procurement through decommission.

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

Use when working with Descope — descope authentication and identity management platform covering users, tenants, access keys, flows, and audit logs. Use when analyzing user authentication patterns, monitoring tenant health, reviewing access key usage, managing Descope flows and roles, or auditing login activity.

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

Use when working with Dagster Deep — dagster deep data orchestration management covering job and asset inventory, run monitoring, schedule and sensor health, partition status, resource configuration, and daemon health checks. Use when investigating run failures, analyzing asset materialization, monitoring schedule ticks, or auditing Dagster configurations.

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

Use when working with Deno Deploy Deep — deep Deno Deploy analysis covering project inventory, deployment history, KV database usage, cron job schedules, custom domain mappings, analytics metrics, and environment variable auditing. Use for comprehensive Deno Deploy platform management.

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

Use when working with Cursor — cursor AI-powered editor management and team analytics. Covers team seat management, usage tracking, model configuration, rules file analysis, project settings review, and workspace configuration. Use when managing Cursor team licenses, reviewing AI feature adoption, or analyzing Cursor workspace and rules configurations.

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