小説、シナリオ、ブログ、推敲、校正（1,833 件）
Use when shaping a capital-raise pitch — why-now / why-us / why-this framing, market-size reasoning, traction-story construction. Triggers on 'tighten the pitch', 'why-now is weak'.
日本語の概要は準備中です。原文の説明を表示しています。
Use when a release review needs machine-derived evidence from git history — hotspot risk and change-coupling analyzers. Triggers on 'hotspot', 'what changes together', 'release forensics'.
日本語の概要は準備中です。原文の説明を表示しています。
Define a brand identity constraint set from a confirmed strategy — colour story, type story, logo direction, imagery direction. Defines the tokens that token emission and asset generation consume.
日本語の概要は準備中です。原文の説明を表示しています。
Draft release summaries, changelog summaries, version PR notes, and changeset-friendly package release notes for npm packages or monorepos. Use this whenever the user asks to write a release summary, 发版说明, release notes, changelog entry, version PR summary, package publish notes, or wants the agent to summarize what will be released from git history, diffs, or changesets, especially for ui libraries, design systems, and multi-package workspaces.
日本語の概要は準備中です。原文の説明を表示しています。
Generate or update CHANGELOG.md from landed git history. Use when the user asks to "write a changelog", "update the changelog", or summarize what changed over the last week/period.
日本語の概要は準備中です。原文の説明を表示しています。
Product Owner - scans codebase and creates or amends GitHub issues with PRD. Use when: PRD, feature, issue, create issue, amend issue, what should we build, plan feature, design feature, scope, requirements, user story.
日本語の概要は準備中です。原文の説明を表示しています。
[Project Management] Use when a workflow step or the user asks for task refinement, story slicing, HTML mockups, draft challenges, artifact review or readiness checks via --mode={refine|story|mockup|challenge|review|dor}.
日本語の概要は準備中です。原文の説明を表示しています。
Implements any user intent, requirement, story, bug fix or change request by producing clean working code artifacts that follow the project's existing architecture, patterns and conventions. Use when the user wants to build, fix, tweak, refactor, add or modify any code, component or feature.
日本語の概要は準備中です。原文の説明を表示しています。
Scrum master for sprint planning and story preparation. Use when the user asks to talk to Bob or requests the scrum master.
日本語の概要は準備中です。原文の説明を表示しています。
Senior software engineer for story execution and code implementation. Use when the user asks to talk to Amelia or requests the developer agent.
日本語の概要は準備中です。原文の説明を表示しています。
Creates a dedicated story file with all the context the agent will need to implement it later. Use when the user says "create the next story" or "create story [story identifier]"
日本語の概要は準備中です。原文の説明を表示しています。
Execute story implementation following a context filled story spec file. Use when the user says "dev this story [story file]" or "implement the next story in the sprint plan"
日本語の概要は準備中です。原文の説明を表示しています。
Map existing materials into a first knowledge record, or investigate a subject's history in depth. Use whenever the user asks to map, survey, go through, reconstruct or investigate what already exists - folders of documents, decision records, meeting notes, emails, exports, code - or wants a starting record built from existing materials, even when the word 'record' is never said: consult this before listing or reading the files yourself, because a map has an agreed scope, a protocol and a report. Also, once, at a suitable moment, to offer the starting choices where a workspace has no record and the work is clearly ongoing - never on a greeting. Learning while working needs no map. Requests come in any language.
日本語の概要は準備中です。原文の説明を表示しています。
[Git] Use when creating release notes or a release document from git history at any scope (tag, branch, time range), as markdown plus a standalone HTML presentation.
日本語の概要は準備中です。原文の説明を表示しています。
Reconstruct your recent working context from your own chat history, live state, and the shared record (user reports, prior fixes, incidents), then hand back a tight current-state brief. Use for 'recall my work on X', 'catch me up', 'what have I been working on', 'where did I leave off', before starting or resuming work.
日本語の概要は準備中です。原文の説明を表示しています。
- Track aircraft and vessels from public ADS-B and AIS broadcasts using ADS-B Exchange, Flightradar24, FlightAware,… Use when following a tail number or flight, looking up an ICAO 24-bit hex code, registration or callsign, tracing a ship by IMO number or MMSI, checking a flag of convenience or port-call history, finding who owns a private jet or vessel
日本語の概要は準備中です。原文の説明を表示しています。
- Mine GitHub, GitLab and git history for identities, infrastructure and leaked credentials using commit author emails, GitHub code search, the commit… Use when investigating a developer or organisation on GitHub, finding leaked API keys, AWS keys or tokens in code, enumerating org members and their personal repos, or recovering secrets deleted from HEAD but still present in history or forks
日本語の概要は準備中です。原文の説明を表示しています。
- End-to-end passive reconnaissance for a domain, website or IP — builds an asset inventory covering registration, DNS, subdomains, infrastructure, tech stack, history and ownership without sending a single packet to the target. Use when asked to research or profile a domain or website, map what an organisation runs, or investigate a suspicious site without alerting its operator
日本語の概要は準備中です。原文の説明を表示しています。
Pull Anton's Grok (grok.com / SuperGrok) conversation history into the Obsidian vault from an official Grok data export (prod-grok-backend.json). Trigger on “/grok-sync“, “синкани grok“, “подтяни grok“, “забери чаты из grok“, “обнови grok“, “sync grok“, “что нового в grok в волт“
日本語の概要は準備中です。原文の説明を表示しています。
Write an evergreen teaching longform for non-technical readers built from your own real material (systems you run, dated failures, numbers), structured as a stitched lesson that can live as a blog post, a GitHub guide hub and a newsletter issue. Use when turning lived engineering experience into a durable how-to. Triggers: /guide, make a guide, build a lesson, evergreen guide.
日本語の概要は準備中です。原文の説明を表示しています。
Recover a session after a hard crash (app died, machine rebooted, context lost mid-work): replay the turn-state ledger for the last requests, files and decisions, run a green/red health ping over the system map, file sync and MCP connectors, then rebuild the previous session history for pickup. Triggers: "/1", "resume after crash", "wake".
日本語の概要は準備中です。原文の説明を表示しています。
CRM-lite for managing GEO agency prospects and clients. Track leads through the full sales pipeline: Lead → Qualified → Proposal Sent → Won → Lost. Store audit history, notes, deal values, and generate pipeline summaries. Use when user says "prospect", "lead", "client", "pipeline", "crm", "nuovo prospect", "aggiungi cliente", or when managing the business side of GEO services.
日本語の概要は準備中です。原文の説明を表示しています。
Creates LinkedIn posts, thought leadership content, and editorial calendars for SME marketing. Covers 7 post types (Awareness, Personal Story, Education, Conversion, How We Do It, Building In Public, Lead Magnet) with complete graphic prompts, first comments, and CTAs. Use when user asks to write social media posts, plan content calendars, create LinkedIn content, or develop thought leadership pieces.
日本語の概要は準備中です。原文の説明を表示しています。
Use the local Apple Music MCP server to browse or manage the user's library and playlists, search the catalog, discover music, control playback, or edit the Up Next queue. Trigger whenever the user asks about their Apple Music account, listening history, playlists, library, playback, recommendations, or queue.
日本語の概要は準備中です。原文の説明を表示しています。