2,450 件 ・ 関連度順
概要と使いどころ
Design consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview... (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Post-ship documentation update. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Restore working context saved earlier by /context-save. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Restrict file edits to a specific directory for the session. (gstack)
日本語の概要は準備中です。原文の説明を表示しています。
Diagnosis loop for bugs and failing behavior. Use for errors, stack traces, regressions, failed tests, issue-tracker bugs, stuck investigations after failed fixes, or asks to debug/fix a bug.
日本語の概要は準備中です。原文の説明を表示しています。
When the user needs a comprehensive marketing plan for a client, a company they advise, or their own product. Also use when the user mentions "marketing plan," "growth plan," "GTM plan," "go-to-market plan," "AARRR plan," "90-day marketing plan," "12-month marketing roadmap," "fractional CMO plan," or "fCMO plan." Generates an exhaustive 13-section plan structured by AARRR (Acquisition, Activation, Retention, Referral, Revenue), customized to the client's current budget, team, and stage, mapped to future funding milestones, cross-referenced with the 139-idea marketing-ideas library and an embedded 17-section current-state audit rubric, with a full marketing operations stack showing which skills and MCP/API integrations execute each part. Outputs a Notion-paste-ready markdown document. For positioning and ICP context before planning, see product-marketing. For stage-specific deep work, see onboarding, signup, emails, referrals, pricing.
日本語の概要は準備中です。原文の説明を表示しています。
Project onboarding - determine project type, complexity, tech stack, and route to correct phase
日本語の概要は準備中です。原文の説明を表示しています。
Scans a codebase and generates a self-contained HTML service-design journey map — NN/g combined customer journey + service blueprint format. Use when the user wants to map user journeys, create journey maps, build service blueprints, or understand user flows from code. Prompts for codebase path if not supplied. Works with any tech stack.
日本語の概要は準備中です。原文の説明を表示しています。
Use this skill when building, debugging, or answering questions about Liveblocks. Liveblocks gives you the building blocks and infrastructure to enable people and AI to work together inside your app, powering realtime collaboration. Liveblocks features include collaboration, rooms, organizations, workspaces, comments, composer, threads, notifications, multiplayer, conflict resolution, realtime presence, avatar stacks, AI collaborators, AI agents, text editors, Tiptap, BlockNote, Lexical, React Flow, Chat SDK. Common components include AiChat, Thread, InboxNotification, Composer, Toolbar (for Lexical Tiptap), FloatingToolbar, FloatingComposer, FloatingThreads, AnchoredThreads. Common hooks include useThreads, useStorage, useMutation, useOthers, useInboxNotifications, useAiChats. Common issues are related to authentication (ID tokens vs access tokens), permissions, room limits, connection errors, user info.
日本語の概要は準備中です。原文の説明を表示しています。
Clerk authentication router. Use when user asks about Clerk CLI operations, adding authentication, setting up Clerk, custom sign-in flows, Swift or native iOS auth, native Android auth, Next.js patterns, React patterns, Vue patterns, Nuxt patterns, Astro patterns, TanStack Start patterns, Expo patterns, React Router patterns, Chrome Extension patterns, organizations, billing, subscriptions, payments, pricing, plans, seat-based pricing, feature entitlements, syncing users, or testing. Automatically routes to the specific skill based on their task.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a reader needs an editorial architecture, flowchart, sequence, state, ER, swimlane, loop, layer-stack, data-flow, or process diagram as self-contained HTML/SVG. Symptoms: 'draw the system', 'architecture diagram', 'sequence of calls', 'state machine visual'. Not for logos, OG images, or Marp decks.
日本語の概要は準備中です。原文の説明を表示しています。
A curated marketing stack guide for SaaS startups — tools, channels, and metrics organized by growth stage. Know exactly which tools to adopt and when. By @WeiYipei.
日本語の概要は準備中です。原文の説明を表示しています。
How a downstream app consumes the shared @kolu/surface stack (@kolu/surface · surface-app · surface-remote · surface-mcp) — declaring a typed reactive surface, serving it, consuming it (SolidJS hooks or a CLI), and mirroring a remote surface over ssh. Grounded in the real consumers: kolu, drishti, odu, and the TUIs. Load when wiring a surface server/client/mirror, or reaching for makeSession / a link / the `.use()` hooks. CHANGING the framework is gated separately — `.claude/rules/surface.md` (a paired, CI-green drishti PR pinned to final kolu HEAD).
日本語の概要は準備中です。原文の説明を表示しています。
Analyze repo, detect stack, trace changes to user-facing entry points, generate E2E YAML test plan
日本語の概要は準備中です。原文の説明を表示しています。
Launch all services for the Retail-Agentic-Commerce project. Use when the user types setup, install, or asks to start, launch, or run the project stack.
日本語の概要は準備中です。原文の説明を表示しています。
Discoverability shim for the Retail-Agentic-Commerce setup Codex skill. Use when the user asks to setup, install, start, launch, or run the project stack.
日本語の概要は準備中です。原文の説明を表示しています。
Dispute resolution, forensic investigation, and risk assessment for autonomous AI agent transactions. Reconstruct provenance chains, adjudicate fault, generate actuarial risk profiles for agent insurance. The accountability layer of the Agent Trust Stack.
日本語の概要は準備中です。原文の説明を表示しています。
Complete architecture reference for the A3 insurance platform — file locations, data flow, conventions, microservice map, and fullstack patterns
日本語の概要は準備中です。原文の説明を表示しています。
Signal-based prospecting — read target companies' public websites for buying signals (ads running, incumbent agency, tech stack, hiring, stale content, missing booking) with evidence URLs, then build a cohort you can explain. Use when asked to "find buying signals", "profile these companies", "which accounts should we target", "build a target list from these domains", or "what changed at these accounts".
日本語の概要は準備中です。原文の説明を表示しています。
Manages the entire session lifecycle: from context loading (PRD, Tech Stack) at startup, to maintaining project memory during active sessions, and creating ultra-compact checkpoints for handoff. / Mengelola siklus hidup sesi: dari pemuatan konteks awal, pemeliharaan memori proyek, hingga pembuatan checkpoint ringkas untuk handoff.
日本語の概要は準備中です。原文の説明を表示しています。
Methodological guide for the AI Agent to safely and systematically translate, refactor, and modernize giant legacy codebases (PHP, Python 2, old React) into modern stacks.
日本語の概要は準備中です。原文の説明を表示しています。
Empowers the agent to autonomously run tests, read terminal stack traces, and self-heal code until tests pass. Transforms the agent from a passive coder to an active CI pipeline debugger.
日本語の概要は準備中です。原文の説明を表示しています。
Core programming concepts from variables through recursion. Covers data types (integers, floats, strings, booleans, arrays, objects), variables and scope (lexical, dynamic, block, function, global), control flow (conditionals, loops, pattern matching), functions (parameters, return values, closures, higher-order functions), recursion (base cases, call stack, tail recursion, mutual recursion), type systems (static vs dynamic, strong vs weak, type inference, generics), and error handling (exceptions, Result types, defensive programming). Use when teaching, reviewing, or diagnosing issues with fundamental programming constructs.
日本語の概要は準備中です。原文の説明を表示しています。
Systems programming from memory management through networking. Covers memory models (stack vs heap, manual allocation, garbage collection, ownership/borrowing), concurrency (threads, mutexes, channels, async/await, actor model, data races vs race conditions), operating system concepts (processes, virtual memory, page tables, system calls, file descriptors, signals), compilation (lexing, parsing, code generation, linking, static vs dynamic libraries), networking fundamentals (TCP/IP, sockets, HTTP, DNS, TLS), and the hardware-software boundary (caches, cache lines, false sharing, memory-mapped I/O). Use when working with low-level code, diagnosing system-level bugs, understanding performance characteristics, or bridging between high-level languages and machine behavior.
日本語の概要は準備中です。原文の説明を表示しています。