4,569 件 ・ 関連度順
概要と使いどころ
Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Codex's capabilities with specialized knowledge, workflows, or tool integrations.
日本語の概要は準備中です。原文の説明を表示しています。
Build and maintain a persistent, interlinked markdown wiki (second brain / research notebook / personal knowledge base) from raw sources. Use this skill when the user wants to ingest an article / paper / note / URL / PDF into their wiki, ask a question against their wiki, lint/health-check their wiki, or set up a new wiki from a folder. Triggers include phrases like "add this to my wiki", "ingest this", "file this article", "update my notes with this", "what does my wiki say about X", "health-check my wiki", "find stale/orphan pages", or any workflow involving a `raw/` source folder, `wiki/` markdown folder, `index.md`, or `log.md`. Compatible with Obsidian vaults.
日本語の概要は準備中です。原文の説明を表示しています。
国内电商提示词融合工作流。用于为国内微信生意、微信视频号、朋友圈、淘宝/天猫/京东风格商品展示，生成给豆包使用的中文商品主图提示词、商品宣传图提示词、商品功能细节图提示词、朋友圈营销文案和带货短视频脚本。用户提到国内电商、大牌商品展示感、朋友圈卖货、视频号、商品图、商品宣传图、功能细节图、带货短视频脚本、营销文案、豆包提示词时使用。
日本語の概要は準備中です。原文の説明を表示しています。
Operate a logged-in Miaoshou ERP workflow for TikTok Shop Malaysia product discovery, product screening, profit estimation, listing preparation, and reviewed publishing. Use when the user asks to search or select products in 妙手 ERP, evaluate low-price traffic products, prepare Malaysian TikTok Shop listings, move products into the TikTok collection box, or publish approved listings. Prefer browser operation through the user's existing login; never store credentials or call undocumented private endpoints.
日本語の概要は準備中です。原文の説明を表示しています。
Create a bilingual Notion job application tracker and organize job links, full JDs, screenshots, and application updates into it. Use for bulk job tracking, exhaustive employer-requirement extraction, and CPT/OPT/sponsorship recording.
日本語の概要は準備中です。原文の説明を表示しています。
Use when customizing Django Admin - save_formset, get_search_results, formsets, queryset optimization, db_index, custom URLs
日本語の概要は準備中です。原文の説明を表示しています。
Backend specification planning frameworks. Use when a spec touches API endpoints, database schema, middleware, or auth. Covers endpoint contracts with request/response shapes, error catalogs, auth per endpoint, schema design with constraints and indexes, migration strategy, and middleware pipeline ordering.
日本語の概要は準備中です。原文の説明を表示しています。
Pinecone serverless vector database -- index management, vector operations, metadata filtering, namespaces, hybrid search, inference API
日本語の概要は準備中です。原文の説明を表示しています。
Elasticsearch patterns -- client setup, index management, search DSL, aggregations, vector search, bulk operations, deep pagination
日本語の概要は準備中です。原文の説明を表示しています。
Query optimization, caching, indexing, connection pooling, async patterns
日本語の概要は準備中です。原文の説明を表示しています。
Meilisearch search engine patterns -- client setup, indexing, search, filtering, facets, geo search, multi-tenancy, task management
日本語の概要は準備中です。原文の説明を表示しています。
Native MongoDB driver (the mongodb npm package) - MongoClient lifecycle, typed collections, CRUD result shapes, cursors, aggregation pipelines, index design, transactions
日本語の概要は準備中です。原文の説明を表示しています。
General workflow for auditing ML CI failures, experiment regressions, training run failures, golden metric failures, and telemetry-backed ML work-product claims from local repositories, logs, metrics, configs, and artifacts. Use when Codex needs to decide whether an ML failure is a model/convergence issue, correctness bug, data/config issue, infrastructure/runtime issue, evaluation/gating policy issue, or unsupported claim, and produce structured evidence-backed outputs.
日本語の概要は準備中です。原文の説明を表示しています。
Edit the Prisma Next data contract — add models, fields, relations, indexes, enums, value objects (composite types), type aliases, namespaces (Postgres schemas), cross-contract foreign keys (cross-space FK), polymorphic types (`@@discriminator` / `@@base`), use extension namespaces (`pgvector.Vector(...)`, `cipherstash.EncryptedString(...)`), wire `prisma-next.config.ts` with `defineConfig` from the `@prisma-next/<target>/config` façade, and run `prisma-next contract emit`. Use for schema, models, fields, attributes, soft delete, paranoid, scopes, validations, callbacks, prisma schema, PSL, contract.prisma, contract.ts, contract.json, contract.d.ts, façade imports, `@prisma-next/postgres/config`, `@prisma-next/postgres/contract-builder`, `@prisma-next/postgres/control`, `@prisma-next/mongo/config`, `@prisma-next/mongo/contract-builder`, `extensions:`, `extensionPacks`, pgvector, cipherstash, postgis, paradedb, supabase, `@prisma-next/extension-supabase`, `@@control`, control policy, managed, tolerated, external, observed, PN-CLI-4002, PN-CLI-4003, PN-CLI-4011.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating, naming, or placing a file or folder in libs/*, or when modifying or adding a file to an existing component (even when the barrel isn't touched) — component vs utility naming, the one-responsibility-per-file layout, when a folder needs an `index.ts` barrel (public API only), and the required set of files a component needs per lib. Load this before scaffolding or restructuring a component so the layout matches the codebase.
日本語の概要は準備中です。原文の説明を表示しています。
This repo is indexed by graft/. For ANY task here, whether understanding how something works, finding where code lives, tracing what calls a symbol or what a change breaks, or scoping an edit, get your context from graft before grepping or reading source files.
日本語の概要は準備中です。原文の説明を表示しています。
UI design and implementation for real product surfaces with taste-first critique, reference routing, project-specific design briefs, variation comparison, and implementation verification. Use when Codex should redesign, build, polish, or critique frontend UI by reading project context, exploring taste, routing through `references/catalog.md`, synthesizing `PROJECT_DESIGN.md` or `design.md`, using investment gates to avoid wrong taste/reference/scope, implementing in the existing stack, and evaluating whether the result is actually better. Best for app screens, dashboards, landing pages, query tools, product surfaces, and design explorations; not for backend-only work or tiny cosmetic edits.
日本語の概要は準備中です。原文の説明を表示しています。
Run any installed skill on several models at once — you, OpenAI Codex, OpenCode and whoever else the profile names — and show what each one made of it side by side. Every model gets the same prepared copy of the skill and works read-only. Use for "/multi:skill <name>", "run this skill on every model", "run <skill> through multi", or any skill whose answer you want from more than one model.
日本語の概要は準備中です。原文の説明を表示しています。
Divergent ideation across model families — the same brainstorm, but each cognitive frame is handed to a different model (Claude sub-agent, OpenAI Codex, a cheap third via OpenCode) so the ideas diverge by frame and by model priors at once. Use for open design questions, architecture and API shape, naming, schema choices, fuzzy bugs with no known root cause, or on "multi adhd", "brainstorm with everyone", "wide ideas from all models". Skip for lookups, syntax, and anything phrased as "quick", "standard" or "canonical".
日本語の概要は準備中です。原文の説明を表示しています。
Walks a user through connecting the judge models this plugin can use — Codex, OpenCode, OpenRouter (or any compatible endpoint: 9router, z.ai, Moonshot), Gemini — and through picking models, including "research current models for me". Use for "multi setup", "set up multi", "configure judges/reviewers/ backends", "connect 9router", "change/pick models", "onboarding", or whenever a probe shows missing backends and the user needs to know what to do about it.
日本語の概要は準備中です。原文の説明を表示しています。
Put one question to several models at once — you, OpenAI Codex, and a cheap third via OpenCode — and show all the answers side by side. No judging, no consensus: three opinions, the user picks. Use for "ask everyone", "what do the other models think", "second opinion", "multi ask", or any open question where one model's answer is not enough.
日本語の概要は準備中です。原文の説明を表示しています。
Code review by several models at once — Claude sub-agents, OpenAI Codex, and a cheap third reviewer via OpenCode — reconciled into one report. Reviews whatever is named: a diff, a branch, specific files, one function, a legacy module, a whole repo. Use for any review request, a second or third opinion, a cross-check before a PR, or "code-review", "multi", "consensus review".
日本語の概要は準備中です。原文の説明を表示しています。
Execute a project from a folder of raw materials. Use when the user drops messages, screenshots, documents, drafts, and references into a project directory and wants Codex to identify the real goal, build a plan, do the work, drive the project to a submission-ready state, verify completion, and return a clear final summary of what was required, what was completed, and how it was done.
日本語の概要は準備中です。原文の説明を表示しています。
Pull latest origin/main into the current local branch and resolve merge conflicts (aka update-branch). Use when Codex needs to sync a feature branch with origin, perform a merge-based update (not rebase), and guide conflict resolution best practices.
日本語の概要は準備中です。原文の説明を表示しています。