2,791 件 ・ 関連度順
概要と使いどころ
Produce a short executive summary for the current rolling-wave project. Use when the user wants a concise status update, investor/team-friendly summary, leadership summary, project progress snapshot, or TL;DR of completed slices, the current slice plan, and upcoming slices.
日本語の概要は準備中です。原文の説明を表示しています。
Create or maintain a source-grounded kpopper knowledge model as a versioned plugin. Use when a reusable domain model should ship independently of any one project.
日本語の概要は準備中です。原文の説明を表示しています。
The complete AI Business Mentor.
日本語の概要は準備中です。原文の説明を表示しています。
Expert-level medicinal chemistry knowledge. Use when working with drug design, structure-activity relationships, ADMET properties, pharmacophores, lead optimization, target identification, drug metabolism, or pharmaceutical development. Also use when the user mentions 'SAR', 'drug design', 'pharmacophore', 'ADMET', 'lead compound', 'hit to lead', 'drug metabolism', 'bioavailability', 'selectivity', 'binding affinity', 'scaffold hopping', or 'bioisostere'.
日本語の概要は準備中です。原文の説明を表示しています。
Use for any question about a codebase, its architecture, file relationships, or project content — especially when graphify-out/ exists, where the question should be treated as a graphify query first. Turns any input (code, docs, papers, images, videos) into a persistent knowledge graph with god nodes, community detection, and query/path/explain tools.
日本語の概要は準備中です。原文の説明を表示しています。
Performs a final quality pass fixing alignment, spacing, consistency, and micro-detail issues before shipping. Use when the user mentions polish, finishing touches, pre-launch review, something looks off, or wants to go from good to great.
日本語の概要は準備中です。原文の説明を表示しています。
Design relational database schemas (and choose when to go NoSQL) that stay maintainable and fast. Use this skill whenever the user mentions tables, DDL, entities and relationships, normalization (1NF/2NF/3NF), primary and foreign keys, UUID vs bigint IDs, indexes (B-tree, composite, covering, partial), EXPLAIN, constraints (CHECK, UNIQUE, exclusion), transactions and isolation levels, migrations (Alembic, Prisma, Flyway, expand-contract, backfilling), or SQL vs NoSQL (MongoDB, DynamoDB, Cassandra, graph databases). Also trigger for "design the database", "model this domain", "which database should I use", or writing ORM models and migration files for PostgreSQL, MySQL, SQLite, or SQL Server.
日本語の概要は準備中です。原文の説明を表示しています。
Install or upgrade the event4u agent-config suite. This marketplace plugin is a bootstrap shim — it ships hooks plus this pointer only; ALL skills, rules, and commands are installed via `npx -y @event4u/agent-config init`. Use when the user asks to install, set up, or upgrade agent-config, or wonders why this plugin contains no other skills.
日本語の概要は準備中です。原文の説明を表示しています。
Turn a shipped changelog into a release narrative — value-not-feature framing, audience-segmented surfaces. Triggers on 'announce the release', 'write changelog post'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when creating and embedding a documentation screenshot — detect and redact sensitive data, human-gate data-bearing shots before ship. Triggers 'screenshot for docs', 'screenshot admin panel'.
日本語の概要は準備中です。原文の説明を表示しています。
Use before merging a release-shaped PR — pre-merge checklist, rollout plan, rollback criteria, ops handoff. Triggers on 'ready to ship', 'launch checklist', 'rollout plan for X'.
日本語の概要は準備中です。原文の説明を表示しています。
Black-box evaluation of a shipped LLM feature — adversarial probes for hallucination, prompt-injection, and cost-runaway vs stated expectations. Not RAG/embedding. Triggers 'review my chatbot'.
日本語の概要は準備中です。原文の説明を表示しています。
Writing/reviewing client-side UI (React/Vue/vanilla) — insecure-render + client-trust gaps AI ships: XSS via innerHTML, client secrets, client-only auth, CORS wildcard, token in localStorage
日本語の概要は準備中です。原文の説明を表示しています。
Use when the feature is implementation-complete and the next step is 'ship it' — verifies, cleans up, routes to merge/PR/park/discard; never destroys work without explicit confirmation.
日本語の概要は準備中です。原文の説明を表示しています。
Use when writing Eloquent models, relationships, scopes, or queries via Model:: — 'fetch users with their orders'. NOT for PHPStan output, non-Eloquent services, or raw SQL questions.
日本語の概要は準備中です。原文の説明を表示しています。
Use when reviewing authorization end-to-end — route → gate → policy → query scope → response filter — before changes to permissions, tenants, ownership, or admin flows.
日本語の概要は準備中です。原文の説明を表示しています。
Before finishing any code (endpoint, query, migration, render, file, infra, dependency, test) — the senior pre-ship checklist of invisible cross-cutting controls AI omits, with backstop greps
日本語の概要は準備中です。原文の説明を表示しています。
Use when designing churn defence — health-score signals, churn-cause split (involuntary / value / relationship / fit), early-warning loop. Triggers on 'why are accounts leaving'.
日本語の概要は準備中です。原文の説明を表示しています。
Multiple agents draft a structured document through federated co-authorship and formal voting.
日本語の概要は準備中です。原文の説明を表示しています。
Kit de ferramentas de product ownership ágil para Senior Product Owner, incluindo geração de histórias de usuário compatíveis com INVEST, planejamento de sprints, gerenciamento de backlog e rastreamento de velocidade. Use para escrita de histórias, planejamento de sprints, comunicação com stakeholders e cerimônias ágeis.
日本語の概要は準備中です。原文の説明を表示しています。
Modos operacionais de IA (brainstorm, implement, debug, review, teach, ship, orchestrate). Use para adaptar o comportamento com base no tipo de tarefa.
日本語の概要は準備中です。原文の説明を表示しています。
A set of resources to help me write all kinds of internal communications, using the formats that my company likes to use. Claude should use this skill whenever asked to write some sort of internal communications (status reports, leadership updates, 3P updates, company newsletters, FAQs, incident reports, project updates, etc.).
日本語の概要は準備中です。原文の説明を表示しています。
[Code Intelligence] Use when you need to query code relationships and connections using the structural knowledge graph.
日本語の概要は準備中です。原文の説明を表示しています。
Divides records into geographic or account-ownership territories. Use when the user provides records with location or account data and wants consistent territory assignments with unresolved locations flagged.
日本語の概要は準備中です。原文の説明を表示しています。