「spa」の検索結果

Create a new component in the Modules folder from template with proper documentation and placeholders replacement.

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

Add or update the code syntax in demo app from all components

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

Launch some action before create push in git

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

Launch some action to push the code in git

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

Update the CHANGELOG.md with the description of the changes between the last released version and the new one

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

Defeats control-flow-flattening obfuscation by identifying the dispatcher/state- variable structure and reconstructing the original control flow so the logic becomes readable. Activates for requests to defeat control-flow flattening, deobfuscate an OLLVM-flattened function, or recover original control flow from a dispatcher loop.

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

SQL discipline for querying Pulp Perfetto traces (.pftrace) with trace_processor — idempotent CREATE OR REPLACE PERFETTO views, GLOB not LIKE, dur = -1 incomplete-slice handling, EXTRACT_ARG for span args, joining on stable utid/upid, SPAN_JOIN PARTITIONED, and the draft→validate→execute loop. Ships Pulp's CPU/UI trace stdlib plus closed GPU startup, health, and probe views. TRIGGER when writing or debugging SQL over a .pftrace, when `pulp trace query` returns wrong/empty rows, or when the trace-analysis skill needs a query primitive.

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

Email marketing operations and automation for B2B SaaS. Use this skill for newsletter strategy, email automation sequences, lifecycle campaigns, nurture workflows, onboarding sequences, deliverability optimization, email copywriting, lead scoring, marketing automation platform setup, and cold-email sending infrastructure — secondary sending domains, SPF/DKIM/DMARC, and domain warmup — plus the contact budget: a cross-channel frequency cap across every sender (marketing, sales sequences, customer success, in-app). Also triggers on: email, newsletter, drip campaign, lifecycle, nurture, onboarding sequence, deliverability, email automation, lead scoring, marketing automation, our emails are going to spam, SPF, DKIM, DMARC, sender reputation, sending domain, cold email domains, domain warmup, mailbox setup, blacklist, bounce rate, BIMI, brand logo in inbox, VMC, Verified Mark Certificate, Common Mark Certificate, transactional email, password reset emails going to spam, DMARCbis, RFC 9989, DMARC pct tag, DMARC t=y test mode, DMARC rollout, move DMARC to reject, frequency cap, email fatigue, customers get too many emails, too many messages, sales and marketing both emailing the same person, communication limits, send frequency safeguard, global frequency capping, quiet period, message precedence.

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

Client reporting, quality assurance, and financial operations management. Handles KPI frameworks, compliance audits, budget tracking, and launch checklists. Use when: managing client dashboards, ensuring brand compliance, conducting QA reviews, tracking marketing spend, ensuring GDPR/CAN-SPAM compliance, handling a request to delete someone's data across the marketing stack, deciding whether an AI voice or AI presenter has to be disclosed, proofreading deliverables. Also triggers on: client reporting, QA, quality assurance, brand compliance, marketing budget, financial tracking, legal compliance, GDPR, CAN-SPAM, proofreading, launch checklist, right to erasure, right to be forgotten, data deletion request, DSAR, someone asked us to delete their data, do we delete or suppress, suppression list, they unsubscribed and we emailed them again, we deleted them and they came back, restored a backup and re-emailed people, custom audience still has deleted contacts, California Delete Act, DROP, data broker deletion, enrichment records disappearing

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

Create a complete feature module with folder structure, Assembly Definition (.asmdef), test assembly, and namespace. Use when adding a new feature, system, or module to a Unity project. Triggers on requests like "create a new feature", "scaffold a module", "add a combat system", "I need a health system", "set up inventory", "create a new module for X", "add a new system", "new feature folder", or any task requiring new folders, assemblies, or namespaces for a gameplay feature — even when the user just names a system they want to build from scratch. Reads ProjectConfig.yaml for folder_strategy and MCP availability.

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

用于创建、审查或重构前端 monorepo，包括 pnpm workspace、Turborepo、Nx、多包依赖边界、任务编排、包命名或包发布；中文触发词包括 monorepo、workspace、多包。

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

Use when creating, reviewing, or restructuring frontend monorepos with pnpm workspace, Turborepo, Nx, multi-package dependency boundaries, task orchestration, package naming, or package publishing; Chinese triggers include monorepo, workspace, multi-package.

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

Use when a task needs the judgment of a Dispatcher — assigning a new job to the best available driver/technician in real time, managing an ETA slip and deciding who to notify, triaging a coverage gap in a service territory, sequencing a driver's remaining stops after a delay, or deciding whether a job needs to be reassigned versus the customer rescheduled.

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

Use when a task needs the judgment of a Bridge and Lock Tender — deciding whether to open a movable span for a vessel signal during a restricted-hours window, sequencing a lock chamber's fill/empty and valve staging, verifying an interlock/gate cycle before commanding span movement, resolving a marine-traffic-vs-vehicle-traffic conflict, or coordinating a vessel passage over VHF.

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

Use when a task needs the judgment of an airline pilot — checking whether an ETOPS diversion-time rating still holds against a current MEL downgrade, deciding whether to accept or query a dispatch release, applying sterile-cockpit discipline and Pilot Flying/Pilot Monitoring role separation on a two-pilot flight deck, resolving a captain-dispatcher operational-control disagreement, or checking Part 117 flight-duty-period legality against an irregular-operations delay.

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

Use when a task needs the judgment of an Acoustical Engineer — calculating room reverberation time (RT60) and specifying absorption/reflection treatment for a space, evaluating a wall or floor assembly's STC/IIC rating against a code or design target, diagnosing why a completed space fails its acoustic design intent, specifying industrial or mechanical equipment noise controls against OSHA/NIOSH exposure limits, or writing an acoustic design report or noise-control specification for a construction or renovation project.

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

Use when a task needs the judgment of an Aerospace Engineer — reconciling a vehicle mass/weight budget against a certification limit, computing a structural margin of safety, choosing a means of compliance for an FAA certification basis, tracing a weight-growth overrun back to a design decision, or evaluating a propulsion/aerodynamics tradeoff against a range or payload requirement.

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

Vira's design system — TailwindCSS conventions, color palette, typography, spacing, components, and accessibility rules. Use when working on UI components, styling, or layout in this project (Lucid HTML in Haskell sources under packages/vira).

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

Audit a 911 dispatch or emergency response system for operational reliability and compliance. Triggers: building or reviewing CAD systems, PSAP software, dispatch platforms, or emergency operations center tools.

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

Review custom components and layouts against shadcn design patterns, visual style conventions (Vega, Nova, Maia, Lyra, Mira), composition rules, design token usage, and Radix/Base UI composition patterns. Use PROACTIVELY after writing or modifying any custom UI component, page layout, or variant of a shadcn component. Use when the user says "review this component", "check my spacing", "does this follow shadcn patterns", "audit this layout", "is this shadcn-idiomatic", or shares a component for feedback. Catches spacing drift, hardcoded colors, missing data-slot attributes, inconsistent theme application, and composition anti-patterns that shipping-fast-with-AI tools often miss.

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

Document a machine learning model in a structured, transparent format for stakeholders, reviewers, and future maintainers. Use when the user says "document this model", "write a model card", "model documentation", "how should I document my ML model", "bias and fairness report", "model transparency", "what does this model do", "model handoff", "production model documentation", or needs to communicate what a model does, how it was built, where it works, and where it fails.

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

**WORKFLOW SKILL — MANDATORY for ANY hook work.** Create, configure, edit, debug, or review lifecycle hooks for VS Code Copilot (default) and Claude Code. USE FOR: criar/configurar/editar hook, hook do Copilot/Claude/agente, lifecycle hook, PreToolUse, PostToolUse, SessionStart, SubagentStop, Stop hook, UserPromptSubmit, PreCompact, bloquear comando, validar tool call, injetar contexto, guard, .agent.md frontmatter hooks, hooks.json, .github/hooks, .claude/settings.json, hook Node.js, cross-platform, hook não dispara/silencioso/ignorado, permissionDecision, hookSpecificOutput, additionalContext. **DEFAULT = VS Code GitHub Copilot.** Switch to Claude Code only when user explicitly says "Claude" OR workspace has `.claude/`. NEVER assume Claude. DO NOT USE FOR: general coding, creating agents (use agent-creator), creating skills (use skill-creator).

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

Research competitor paid-ad presence, messaging, creative, formats, landing pages, keyword and auction signals, transparent ad libraries, and strategic gaps across supported platforms. Use for competitor ads, ad libraries, ad spy, competitive PPC analysis, competitor creative, Google Ads Transparency, Meta Ad Library, or paid-media competitor research.

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

Assists in provisioning instances and databases, designing performant schemas, and querying data in Spanner. Use when designing primary keys, writing SQL queries or client library code, or diagnosing performance issues.

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