2,882 件 ・ 関連度順
概要と使いどころ
Mint an identifier or a name of a requested type out of a free-text hint: a UUID, a SHA-1 digest, a constant, variable, function, or class identifier, a path component, or a product-like name. Use when the user wants an identifier, id, symbol, slug, or name "minted", "coined", "derived", or "generated" from a description.
日本語の概要は準備中です。原文の説明を表示しています。
Discover additional, third-party components (libraries/frameworks) for the technology stack to provide needed functionality.
日本語の概要は準備中です。原文の説明を表示しています。
Analyze the documents for spelling, capitalization, punctuation, word break, or grammar errors. Use when the user wants to "proofread" or "spellcheck" a document.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to analyze a file, a directory, or the whole codebase to understand structure, architecture, dependencies, complexity, duplication, dead code, or technical debt — e.g. "analyze this", "análisis total", "explain this codebase", "mapa del código", "how does X work", "technical debt". Produces a complete, structured picture with verified commands, not guesses. Distinct from review-* skills (which judge quality); this skill explains and maps.
日本語の概要は準備中です。原文の説明を表示しています。
Use when proofreading, copy-editing, or verifying English in any docs/**/*.mdx chapter or code comment in this repo. Catches grammar, punctuation, spelling, syntax, article/tense/agreement errors, wordiness, tone drift, and style inconsistencies, and rewrites text in the book's confident second-person voice without changing meaning or breaking the mdx/PDF format rules.
日本語の概要は準備中です。原文の説明を表示しています。
Use when asked to map or analyze flows, pipelines, processes, or sequences of events in this repo — e.g. "mapa el flujo", "flow", "pipeline", "ciclo de vida", "trace the request", "how does the build/release flow work", "diagrama del flujo". Maps data flows, request lifecycles, CI/CD pipelines, and state transitions with verified file:line evidence. Distinct from analyze-code (which maps code structure); this skill maps movement over time.
日本語の概要は準備中です。原文の説明を表示しています。
You MUST use this before any creative work - creating features, building components, adding functionality, or modifying behavior. Explores user intent, requirements and design before implementation.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill whenever the user wants to analyze binaries with radare2/r2 from the command line, including reverse engineering, disassembly, function analysis, strings/import inspection, patching, binary diffing, hex inspection, or r2 scripting. Also use it when the user mentions PE/ELF/Mach-O/DEX/WASM files together with CLI analysis, `rabin2`, `rasm2`, `radiff2`, `r2pipe`, or asks for radare2 command help on Windows/Linux/macOS.
日本語の概要は準備中です。原文の説明を表示しています。
Ultimate UI/UX design intelligence: an Anti-Slop layer that kills AI tells (em-dash, AI purple glow, generic names, template layouts), tunable Design Dials (variance/motion/density) and Style Modes (functional, minimalist, brutalist, soft-premium, marketing), 161 industry color palettes in a shadcn-aligned semantic token schema, 48 UX Laws, 37 Design Tests, UX Heuristics (Nielsen + Krug), Harvester extraction, Figma & Google Stitch integration, MCP server, Component Generator, and BM25 search across 17 domains + 19 framework stacks. One command = complete design system. Use when designing or reviewing UI/UX, choosing colors/typography, fixing generic AI-looking designs, or building Web App / SaaS / Mobile screens.
日本語の概要は準備中です。原文の説明を表示しています。
Customer discovery framework using Jobs-To-Be-Done theory — uncover the functional, social, and emotional jobs customers hire products to do. Produces JTBD canvases with job statements, outcome metrics, and competing solutions. Use alongside cm-brainstorm-idea for evidence-based product decisions.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite is an open-source, self-hosted backend platform that provides authentication, databases, storage, functions, messaging, and realtime APIs out of the box. It serves as a privacy-first alternative to Firebase and Supabase, packaged as Docker microservices for full data ownership.
日本語の概要は準備中です。原文の説明を表示しています。
Appwrite is an open-source backend platform for web, mobile, and AI apps. This skill helps agents use Appwrite's real services—Auth, Databases, Storage, Functions, Messaging, Realtime, and Sites—instead of inventing a generic backend workflow.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product management guidance for day-to-day PM work. Use when creating roadmaps, prioritizing features, managing stakeholders, planning sprints, grooming backlogs, scoping features, planning releases, defining OKRs, managing technical debt, or coordinating go-to-market. Covers RICE, ICE, MoSCoW frameworks, cross-functional collaboration, and product metrics.
日本語の概要は準備中です。原文の説明を表示しています。
Expert product launch strategist for SaaS and technology companies. Use when planning product launches, coordinating cross-functional launch teams, managing beta programs, creating launch communication plans, planning launch day execution, setting up post-launch monitoring, running launch retrospectives, or defining launch metrics. Covers launch tiering, internal enablement, rollback planning, and contingency strategies.
日本語の概要は準備中です。原文の説明を表示しています。
Generates animation configurations for Remotion including spring configs, interpolations, easing functions, and timing logic. Focuses ONLY on animation parameters, NOT component implementation. Use when defining animation behavior or when asked to "configure animations", "setup spring configs", "define easing curves".
日本語の概要は準備中です。原文の説明を表示しています。
Decompose dense codebase-wide, multi-document, PDF, and aggregation work even when the input fits the context window, following Recursive Language Models (Zhang, Kraska, Khattab, 2025). Use when the user asks to analyse all files, a whole repo, all docs, large PDFs, or to aggregate or multi-hop across scattered sources. Skip one file, one function, a single needle, or a one-page PDF conversion. Triggers: long context, context rot, large codebase, many files, all files, big document, multi-document, PDF, aggregate, summarize everything, codebase-wide, multi-hop, recursive, sub-agents, map-reduce.
日本語の概要は準備中です。原文の説明を表示しています。
Multi-backend database security auditor. Audits Supabase, Firebase (Firestore/RTDB/Storage/Functions/Remote Config), MongoDB (self-hosted + Atlas), self-hosted PostgreSQL, and self-hosted MySQL for RLS/rules misconfigurations, exposed credentials, auth bypasses, MongoBleed (CVE-2025-14847), pgBouncer CVE-2025-12819, mysql_native_password drift, ghost auth, and storage exposures. Use this skill whenever the user mentions database security, RLS or rule audits, security review, penetration testing a vibe-coded app, checking if their DB is exposed, hardening a backend, fixing security rules, or auditing apps built with Lovable/Bolt/Replit/Cursor/Claude Code on any of these backends. Trigger on phrases like 'is my app secure', 'check my database', 'audit my Firebase', 'audit my MongoDB', 'audit my Postgres', 'audit my Supabase', 'is my DB exposed', or any cross-backend variant ('audit my full stack').
日本語の概要は準備中です。原文の説明を表示しています。
World-class practice research. This skill should be used when the user asks what the best in the world does about a specific problem, technique, or situation — covering product, engineering, design, marketing, compliance, operations, org design, and any other domain. Use when the goal is to understand elite-tier practice, not to make a strategic decision. Distinct from best-in-world-strategy, which is for choosing between options.
日本語の概要は準備中です。原文の説明を表示しています。
解析 Verilator coverage.dat + sim log，输出 functional + code coverage 数值，判断是否 100% 达标。触发场景：(1) bb-invoke-verilator 后；(2) 每次回归后；(3) 显式 /bb-collect-coverage。
日本語の概要は準備中です。原文の説明を表示しています。
Use for a weekly operating review (Friday wrap or Monday plan) — review progress against the 90-day priorities, surface stalled open loops, and set next week's focus. This is the PERSONAL operating review; distinct from /audit (checks the kit's connections/freshness) and /level-up (finds one automation to build). Trigger on "/weekly", "weekly review", "weekly planning", "how did this week go", "plan my week".
日本語の概要は準備中です。原文の説明を表示しています。
Nature-style climate and ecology manuscript reviewer skill for testing biodiversity, ecosystem-function, carbon-cycle, conservation, global-change and ecological-inference claims against sampling, causal design, model structure, uncertainty and management scope.
日本語の概要は準備中です。原文の説明を表示しています。
Create distinctive, production-grade frontend interfaces with high design quality that avoids generic AI aesthetics. Use when the task involves `build web components`, `create frontend interface`, `build web page`, `build web application`, `frontend design`, `create UI component`, or `design web interface`.
日本語の概要は準備中です。原文の説明を表示しています。
Display input/output args, return object and cost time of a Python method invocation in a live process. Use this to observe function behavior at runtime — see what arguments go in, what comes back, and how long it takes. This is the most frequently used diagnostic command.
日本語の概要は準備中です。原文の説明を表示しています。
Trace execution time of Python method invocations in a live process with call stack visualization. Use this to see a hierarchical call tree showing which sub-calls are slow and where time is spent within a function.
日本語の概要は準備中です。原文の説明を表示しています。