4,184 件 ・ 関連度順
概要と使いどころ
Use when writing, editing, cleaning, or refactoring Tailwind classes, components, or configuration. Not for read-only audits of Tailwind code, or general CSS without Tailwind.
日本語の概要は準備中です。原文の説明を表示しています。
Use when implementing a multi-file change, building a feature from a breakdown, or writing a large amount of code. Not for a single settled ticket: use work.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or verifying framework-specific code, boilerplate, or a documented, correct implementation. Not for remote, credential, publish, deploy, or irreversible changes.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing or restructuring code, before adding a helper, wrapper, config key, or dependency, or when the user asks for minimal or DRY code. Not for performance tuning: use optimize.
日本語の概要は準備中です。原文の説明を表示しています。
Use when modernizing APIs, removing compat shims, killing feature flags, or rewriting a subsystem cleanly. Not for additive refactors that must preserve the old path.
日本語の概要は準備中です。原文の説明を表示しています。
Fix silent metadata issues in RFDB node storage. Covers two traps: (1) metadata flattening — nested metadata fields become top-level after serialization, so node.metadata.field is undefined but node.field works. (2) reserved keys — fields named "type", "id", "name", "file", "exported" are silently stripped from metadata by _parseNode() to prevent overwriting top-level node fields.
日本語の概要は準備中です。原文の説明を表示しています。
Fix nodes silently disappearing from RFDB when an enricher or post-resolution pass writes new nodes via BatchHandle. Use when: (1) writing a TypeScript enricher that should ADD nodes/edges to existing files, (2) after calling `client.createBatch()` + `batch.addNode({file: 'X', ...})` + `batch.commit()` the original nodes in file X have vanished, (3) tests that load a graph fixture, run an enricher, then query original nodes get empty results, (4) a verification step shows expected nodes pre-enrichment but 0 post-enrichment. Root cause: `BatchHandle.commit()` invokes RFDB's `commit_batch` which AUTO-POPULATES `changed_files` from each added node's `file` field, then the server DELETES all existing nodes whose `file` matches before inserting new ones — file-level upsert semantics. This is correct for the JS/Haskell analyzers (which fully re-emit a file's contents) but catastrophic for enrichers that only ADD to existing files.
日本語の概要は準備中です。原文の説明を表示しています。
Azure Cosmos DB performance optimization and best practices guidelines for NoSQL, partitioning, queries, SDK usage, and vector search. Use when writing, reviewing, or refactoring code that interacts with Azure Cosmos DB, designing data models, optimizing queries, or implementing high-performance database operations.
日本語の概要は準備中です。原文の説明を表示しています。
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
日本語の概要は準備中です。原文の説明を表示しています。
Read project data documentation (data dictionaries, dbt manifests, model docs, column descriptions, lineage, metric definitions) before writing analytics SQL. Use for mapping business and product terms to concrete models and columns.
日本語の概要は準備中です。原文の説明を表示しています。
Transform academic papers into in-depth technical articles with multiple writing style options. Use the MinerU Cloud API for high-precision PDF parsing, automatically extracting images, tables, and formulas. Optional formula explanations and GitHub code analysis, generating Markdown and HTML formats.
日本語の概要は準備中です。原文の説明を表示しています。
Read project data documentation (data dictionaries, dbt manifests, model docs, column descriptions, lineage, metric definitions) before writing analytics SQL. Use for mapping business and product terms to concrete models and columns.
日本語の概要は準備中です。原文の説明を表示しています。
Perform actions in Linear (read, create, update, search issues, projects, comments, teams, cycles, labels, etc.) by writing and running small Node scripts against the official @linear/sdk TypeScript SDK with a personal API key. Use this when the user wants to do Linear work from the terminal without the Linear MCP server, or asks to list/open/create/update/close Linear issues, leave comments, or query teams, projects, users, or workflow states.
日本語の概要は準備中です。原文の説明を表示しています。
Use for ANY bug bounty, penetration test, or web/API/mobile security assessment: recon, testing endpoints, analyzing Burp traffic or any bug-bounty platform's MCP (HackerOne, Intigriti, Bugcrowd, YesWeHack, Immunefi), reviewing APKs, bypassing a WAF, enforcing scope, hunting a specific vuln class, validating findings, writing reports, or when you are stuck on a target and about to give up. Activates automatically for all bug-bounty and pentest sessions. Runs an autonomous, never-surrender predator methodology: refuses to conclude "secure", exhausts each vuln class to depth, proves a real attacker-path with impact and no false positives, tracks coverage so nothing is re-tested or skipped, diagnoses failed tooling from full logs, and hunts at maximum effort with intelligent token use until the goal is found. Activates and follows instructions in ANY language the operator writes in (the skill itself is English). Bundles a per-class web-exploitation KB, a writeup library, and PayloadsAllTheThings.
日本語の概要は準備中です。原文の説明を表示しています。
This skill should be used when the user asks to "make a whiteboard animation", "draw-on explainer", "VideoScribe style", "hand-drawn explainer video", "animate a sketch being drawn", "do a doodle/scribe video", "show a hand drawing the illustration", or "animate handwriting appearing on a whiteboard". Covers SVG stroke draw-on, a marker hand that follows the path tip, staggered reveal, erase/wipe transitions, and narrated export.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing, reviewing, refactoring, or modernizing CSS/Tailwind. Apply a policy-first approach: semantic tokens, explicit cascade order, static CSS, intrinsic component layouts, accessible state, measured performance, and progressive enhancement backed by current sources.
日本語の概要は準備中です。原文の説明を表示しています。
Find the root cause of a bug before writing any fix.
日本語の概要は準備中です。原文の説明を表示しています。
Strip AI writing patterns; add real voice to prose.
日本語の概要は準備中です。原文の説明を表示しています。
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.
日本語の概要は準備中です。原文の説明を表示しています。
Bun runtime, package manager, bundler, and test runner. Use when running scripts with bun, managing packages, serving HTTP with Bun.serve, querying databases with Bun.sql/bun:sqlite/Bun.redis, shell scripting with $, using S3/file I/O, writing tests with bun:test, bundling or compiling to executable, or using any Bun-specific API (spawn, glob, semver, FFI, workers, plugins, HTMLRewriter).
日本語の概要は準備中です。原文の説明を表示しています。
Type-safe URL query state management with nuqs 2.x. Use when writing or reviewing code that uses useQueryState, useQueryStates, URL search params, query parameters, nuqs parsers, createLoader, createSearchParamsCache, createSerializer, or URL state in Next.js, React, Remix, React Router, or TanStack Router.
日本語の概要は準備中です。原文の説明を表示しています。
Редактирует русский текст по инфостилю Ильяхова. Убирает стоп-слова, штампы, канцеляризмы, голословные утверждения. Заменяет конкретикой: фактами, цифрами, пользой. Адаптирует строгость под контекст: UI, лендинги, email, статьи, саппорт. Вызывай, когда пользователь просит отредактировать, улучшить, вычистить или проверить русский текст. Also triggers on: edit Russian text, improve copy, review UX writing, fix marketing text, rewrite landing page, clean up email.
日本語の概要は準備中です。原文の説明を表示しています。
降低中文学术写作（本/专科毕业论文）AIGC检测率的专项 skill。 基于真实论文改写实验（AIGC率从 >50% 降至 11%）归纳的规律，并参考 Wikipedia「Signs of AI writing」项目的系统性模式分类。 检测并修复中文AI写作的典型模式；默认保量润色（避免为降AIGC大幅删短）； 含中英术语与缩写规范、会话记忆库（避免重复释义、滚动段落摘要防前后不一致）、 LaTeX 源文件保护规则。支持：降低AI率、人工润色、降低AIGC、 humanize、去AI味、学术写作润色、论文降重、AIGC检测、AI痕迹消除、学术文本 人工化处理、AIGC检测报告。
日本語の概要は準備中です。原文の説明を表示しています。
Find the angle that makes something sell. Use this skill whenever the user mentions positioning, angles, differentiation, unique selling proposition, 'how do I stand out', 'what makes us different', value proposition, messaging framework, or 'find the hook'. Also trigger when copy isn't converting (often a positioning problem), when marketing feels generic, when launching a product, creating a lead magnet, writing a landing page, or entering a crowded market. Even if the user is about to write copy without established positioning, run this first — the angle informs everything downstream. Generates 3-5 positioning angles with competitive web research and validation.
日本語の概要は準備中です。原文の説明を表示しています。