4,338 件 ・ 関連度順
概要と使いどころ
Competitive Ad Intelligence. Analyzes competitor advertising strategies including platform identification, landing page analysis, targeting reverse-engineering, positioning gaps, creative approach evaluation, and builds a "beat the competition" strategy with a competitor ad swipe file template.
日本語の概要は準備中です。原文の説明を表示しています。
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Gorse recommendation engine pods crashing with "user: unknown userid 65532" error. Use when: (1) Gorse master/server/worker pods show CrashLoopBackOff or Error status, (2) Logs show "failed to get user directory" with unknown userid, (3) Running gorse containers with runAsNonRoot security context and custom UID. The gorse images call os.UserHomeDir() at startup which requires the UID to exist in /etc/passwd.
日本語の概要は準備中です。原文の説明を表示しています。
Fix Gorse 0.5.x recommendation engine silently disabled or degraded due to config incompatibility with 0.4. Use when: (1) Gorse 0.5 recommendations are poor/empty despite having data, (2) collaborative filtering appears disabled even though [recommend.collaborative] section exists, (3) migrating Gorse config from 0.4 to 0.5, (4) old config keys like [recommend.popular], [recommend.neighbors], [recommend.online], [recommend.offline] are being used with Gorse 0.5. Critical: type="mf" must be explicitly set in [recommend.collaborative] or CF is silently disabled (default "none").
日本語の概要は準備中です。原文の説明を表示しています。
Fix Gorse recommendation engine failing to connect to ClickHouse Cloud with EOF errors. Use when: (1) Gorse pods crash with "failed to connect data database" and "EOF" error, (2) Using ClickHouse Cloud (*.clickhouse.cloud) as Gorse data store, (3) TLS connection works (verified with openssl) but Gorse still fails, (4) Tried secure=true, different ports (8443, 9440), timeout params without success. The Gorse ClickHouse driver is incompatible with ClickHouse Cloud's native protocol.
日本語の概要は準備中です。原文の説明を表示しています。
Fix ClickHouse Cloud migration failures caused by multi-table RENAME statements. Use when: (1) Migration fails with "Database X is Shared, it does not support renaming of multiple tables in single query", (2) golang-migrate or other migration tools show dirty database version after a table-swap migration on ClickHouse Cloud, (3) Schema migration works on self-hosted ClickHouse but fails on ClickHouse Cloud. ClickHouse Cloud uses SharedMergeTree engine which has restrictions not present in regular MergeTree.
日本語の概要は準備中です。原文の説明を表示しています。
Structure and package support escalations for engineering, product, or leadership with full context, reproduction steps, and business impact. Use when an issue needs to go beyond support, when writing an escalation brief, or when assessing whether an issue warrants escalation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when Code implementation and refactoring, architecturing or designing systems, process and workflow improvements, error handling and validation. Provide tehniquest to avoid over-engineering and apply iterative improvements.
日本語の概要は準備中です。原文の説明を表示しています。
Optimize website content for search engine visibility and user engagement. Conduct keyword research, implement on-page SEO tactics, analyze content gaps, write compelling meta descriptions, and develop internal linking strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Apply Andrej Karpathy-inspired coding-agent guidelines in Codex. Use when writing, reviewing, debugging, or refactoring code to surface assumptions, avoid overengineering, keep edits surgical, and define verifiable success criteria.
日本語の概要は準備中です。原文の説明を表示しています。
Turn vague or partially formed AI, computer-science, data-driven, and engineering-method research directions into evidence-grounded, falsifiable, paper-ready Research Idea Briefs through heuristic questioning, staged confirmation, literature positioning, novelty attack, and method-figure planning. Use when the user needs to clarify a research idea, formalize inputs/outputs/objectives/constraints, frame background and motivation, select 3-5 anchor papers, identify a defensible gap, derive 2-3 contributions, stress-test novelty, or design an input-to-output method framework and core-paper figure. Also trigger on requests such as 明确科研 idea、启发式梳理 idea、互动追问科研问题、梳理论文创新点、定义研究任务、找对标论文、把研究方向变成论文方案、画方法框架图. Do not use as the primary workflow for running experiments, exhaustive systematic reviews, drafting full manuscript sections, or polishing finished prose.
日本語の概要は準備中です。原文の説明を表示しています。
Design scale-adaptive game architecture with engine systems and networking. Use when the user says "game architecture" or "design architecture"
日本語の概要は準備中です。原文の説明を表示しています。
Game systems architect for technical architecture, engine design, and infrastructure. Use when the user asks to talk to Cloud Dragonborn or requests the Game Architect.
日本語の概要は準備中です。原文の説明を表示しています。
Create platform-native content systems for X, LinkedIn, TikTok, YouTube, newsletters, and repurposed multi-platform campaigns. Use when the user wants social posts, threads, scripts, content calendars, or one source asset adapted cleanly across platforms.
日本語の概要は準備中です。原文の説明を表示しています。
UE (user experience engineering) skill for defining end-to-end user experience behavior and interaction logic. Use for tasks like flow design, interaction models, state machines, error recovery, input validation, usability heuristics, accessibility, and turning UX intent into testable acceptance criteria for implementation.
日本語の概要は準備中です。原文の説明を表示しています。
generate, refine, validate, and render diagrams from natural language, notes, code snippets, schemas, tables, or existing diagram source. use for flowcharts, swimlanes, sequence diagrams, state diagrams, er diagrams, class diagrams, architecture/c4-style diagrams, dependency graphs, gantt charts, mind maps, user journeys, sankey-style flows, org charts, network graphs, and other visual models. supports mermaid by default, graphviz dot for complex graph layout, plantuml for uml-heavy engineering diagrams, and svg output when direct markup is more reliable.
日本語の概要は準備中です。原文の説明を表示しています。
Creates task-oriented technical documentation with progressive disclosure. Use when writing READMEs, API docs, architecture docs, or markdown documentation. Also use this skill at the END of any completed reverse engineering, penetration testing, CTF, or security analysis task to generate a formal report in the user's project directory. Trigger keywords: 写报告, 写文档, 出报告, writeup, 技术文档, report, documentation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user asks for an HTML-first visual design deliverable or design judgment: interactive prototype, slide deck, motion demo, infographic, dashboard, landing page, whitepaper, changelog, business card, social cover, brand system, design critique, multi-variant exploration, or export to MP4, GIF, PPTX, PDF, or SVG. It is optimized to make AI agents do the routing, template selection, verification, and export prep so humans spend less time prompt-engineering. Do not use for production web apps, SEO sites, backend systems, or pure copy edits.
日本語の概要は準備中です。原文の説明を表示しています。
An engineering-grade marketing system organized around two surface modes — a deep black canvas for hero and footer chapters and a flat paper-white canvas for body content — connected by a single, almost violently saturated NVIDIA Green accent that carries every CTA, every active tab, and the small decorative corner squares that mark out cards. The system is unapologetically angular: 2px radius across every surface, tight bold sans-serif typography in NVIDIA's proprietary EMEA cut, and a hairline gray rule that separates dense multi-column technical content. There is no decorative gradient, no atmospheric mesh, no soft drop shadow — just black, white, gray, and green stacked into a structured editorial grid that scales from product cards to massive industry landing pages without bending its rules.
日本語の概要は準備中です。原文の説明を表示しています。
.NET / C# 二进制逆向。当目标是 .NET assembly（PE 头含 CLR、.exe/.dll 托管程序）、C# 编译产物（含 NativeAOT）、红队 Sharp* 工具（Rubeus / SharpHound / SharpHound 等）、.NET 混淆程序（ConfuserEx / SmartAssembly / Babel / Eazfuscator）、.NET loader / info-stealer / 套壳 malware 时使用。优先用 dnSpyEx + de4dot，需要 AI 直接操作时联动 dnSpy MCP。不用于纯 native 二进制（走 reverse-engineering / ida-reverse）。
日本語の概要は準備中です。原文の説明を表示しています。
Build production-ready LLM applications, RAG systems, and intelligent agents. Use when implementing AI features, chatbots, vector search, or agent orchestration.
日本語の概要は準備中です。原文の説明を表示しています。
Production-grade Python and AI engineering standards. Use for ANY Python work — FastAPI services, LangChain/LangGraph agents, RAG pipelines, LLM API integrations, document processing, or data scripts — whether writing new code, reviewing, refactoring, or debugging. Enforces typed Pydantic boundaries, structured errors and logging, LLM call timeouts/retries/output validation, secret management, async correctness, and tested code.
日本語の概要は準備中です。原文の説明を表示しています。
奶油纸 + 锈红 + 蓝图网格 mask + 黑边硬卡片 + pipeline 盒
日本語の概要は準備中です。原文の説明を表示しています。
AI code reviewer grounded in classic software engineering books for catching design smells, coupling issues, and architectural risks.
日本語の概要は準備中です。原文の説明を表示しています。