5,053 件 ・ 関連度順
概要と使いどころ
Create or update a structured change log for a product or platform. Use when someone asks to "create a change log", "log this change", "what changed", "update the change log", "release notes", or "changelog". Reads project memory (CLAUDE.local.md Recent Changes) and meeting notes to build chronological change records. Supports init (backfill from memory), update (append new entries), and release (summarize for a version).
日本語の概要は準備中です。原文の説明を表示しています。
Detailed completeness audit of all project documents. Use when someone asks "are we ready for production", "audit our docs", "readiness check", "nfr tracker", or "what's missing". Do NOT use for a quick command listing — use /pmstudio instead. Scans every document for section-level completeness, reports staleness, and gives prioritized gap-closure recommendations.
日本語の概要は準備中です。原文の説明を表示しています。
Use when the user invokes /coco or /coco!, says catch me up, or asks what needs attention, a project status, their todos, decisions or people. Renders the PM dashboard and routes each subcommand to its platform tool or a PM skill.
日本語の概要は準備中です。原文の説明を表示しています。
PM Studio command center. Use for a quick overview of available commands and document inventory. Use when someone says "pmstudio", "show commands", "what can I generate", or "project status". Do NOT use for detailed completeness audits — use /pmstudio-nfr instead. Shows document coverage dashboard and recommends which /pmstudio-* command to run next.
日本語の概要は準備中です。原文の説明を表示しています。
Turn the project you just shipped into a short, polished, shareable launch video (an "ad") using HyperFrames. Use when someone says "/coco-ads", "make a launch video", "brag about this", "turn this into a promo", "make an ad for this", or wants to share what they built. Reads the project code directly — no live URL or screenshots needed. Renders locally.
日本語の概要は準備中です。原文の説明を表示しています。
Quick-reference card for Chisle commands. One-shot display, not a persistent mode. Use when the user says "chisle help", "how do I use chisle", "what chisle commands", or invokes /chisle-help.
日本語の概要は準備中です。原文の説明を表示しています。
One-shot efficiency audit of a file, diff, or whole repo across BOTH axes at once: over-engineered code (reinvented stdlib, needless abstractions, speculative config) AND bloated prose (verbose comments, padded docstrings, redundant doc sections). Neither a pure code-minimizer nor a pure prose compressor does both in one pass. That's the point. Ranked report, biggest saving first; changes nothing. Use when the user says "chisle audit", "/chisle-audit", "audit this for bloat", "what can I cut", "review this PR for over-engineering and verbosity".
日本語の概要は準備中です。原文の説明を表示しています。
Use when generating or editing images from Flutter/Dart with Firebase AI Logic and a Gemini image model (Nano Banana), making the first call work, choosing Gemini Developer API vs Vertex AI, hitting quota, billing or App Check failures, getting empty or image-only responses, sending a user photo as input, controlling aspect ratio or size, writing the image prompt, or deciding what to test.
日本語の概要は準備中です。原文の説明を表示しています。
Daily cross-platform rankings of AI agent skills (skills.sh, ClawHub, Tencent SkillHub, GitHub, X/HN/Bluesky). Use when the user asks which agent skill to install, what is trending, whether a skill is popular or trusted, or wants to compare skills. Read-only public CSV data; it recommends and links, it does not install anything.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly. Confirms that the registrar, the host, and the hosted database still match what the inventory says, in one read only pass per project, and names every drift with the exact screen, the exact current value, and the exact intended value. It records that a variable exists and never its value, it fixes nothing inside an account, it buys nothing in any state, and it never rotates a key.
日本語の概要は準備中です。原文の説明を表示しています。
Monthly, file work only, no browser at all. Re-reads a month of real change outcomes and rewrites the file that decides what the fix runner may change without asking first. A class the member merged unchanged repeatedly widens by exactly one step. A class they edited, closed unmerged, or that regressed narrows immediately. It never touches the outer boundary, which no volume of evidence can widen.
日本語の概要は準備中です。原文の説明を表示しています。
Monthly, and on its first run it is the whole setup, launched by hand. It discovers what the member actually runs by walking their code roots and reading the registrar, the host, and the hosted database, then writes the inventory, the domains file, the starting budgets, and the opening safe fix rules, seeds the board, builds the dashboard, and registers one scheduled job per routine. It creates no account, buys nothing, and provisions nothing.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public presence, writes the charter with a source and a date beside every conclusion, discovers the AI Employees actually installed on this machine within a bounded search, writes the map every other routine in this kit reads, seeds the priorities and the watchlist once, builds the fleet dashboard, and registers this Employee's own seven jobs. On every monthly run it re-runs discovery and reconciles the map against what is really there. It never writes into another Employee's folder, never registers a job it does not own, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces, reads the member's own already published posts, and builds the voice file from real samples rather than from an idea of a voice, then writes the plan, creates the proof inventory, seeds the opening slots, and registers the recurring jobs. On every monthly run it re reads the evidence the kit produced and rebuilds only what the evidence contradicts. It publishes only where you released the channel, never replies, spends only where you released it, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, browser heavy. Unions every sitemap each property declares without a browser, builds the candidate set from URLs not already in the indexing ledger, then drives the member's own search performance console to inspect each candidate and request indexing inside an account wide allowance. Spends what is left on sitemap health, which is unmetered. It inspects, requests, and views or submits sitemaps inside that console and does nothing else there, ever, and it never removes a sitemap.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the launch board, builds the tailored command center, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed, reconciles drift, and rebuilds. It holds every outbound action unless you released the channel, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Works the next ready card on the board, one card per run, and assembles what it needs as a complete local file ready to paste: a campaign build sheet, a negative keyword file, a conversion action specification, an audience definition, or an upload packet. The whole step happens in a text editor until you release the ad account in RELEASES.md, and then Step 6a publishes the approved package through a connection you already have and writes a receipt for every id the platform returns.
日本語の概要は準備中です。原文の説明を表示しています。
Weekdays. Produces one creative set per run against evidence rather than taste, reading the standing doctrine for the angles currently earning and the metrics ledger for what has decayed. It writes the images and the exact strings into a dated local set folder with the destination screen named, files one card, and uploads nothing to any account. It never opens an account screen, sends only where you released the channel, spends only where you released it, and never touches a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that, on the first weekday, light browser lane. On the first run it researches the business from its own public surfaces before asking anything, writes the strategy folder, seeds the pipeline, reconciles the schedule table, and registers the recurring jobs. On every monthly run it re-reads the evidence the kit produced, applies what changed to the files it owns, and carries every member written setting across verbatim. It holds every outbound action unless you released the channel, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that, light browser lane. On the first run it researches the business from its own published surfaces before asking anything, writes the strategy folder, creates the ledgers, seeds the opening cards, builds the single page dashboard, reconciles the schedule table, and registers the eight recurring jobs. On every monthly run it re-reads a month of the kit's own evidence, applies what changed, adds a tab for a channel that gained volume, rebuilds, and reconciles every registered job against the table. It holds every outbound action unless you released the channel, and it never enters a credential.
日本語の概要は準備中です。原文の説明を表示しています。
Weekly, on a Friday, read only everywhere. Scores the week from the daily metrics ledger alone, with the screen and the date range beside every number, then writes the ranked paste ready list of what to change in the account next week. Each line names one change, the exact screen, the current value, the proposed value, and the evidence row it came from. It proposes no change it cannot source, it names no action it took because it takes none, and it spends only where you released it.
日本語の概要は準備中です。原文の説明を表示しています。
Runs once by hand on the first day and once a month after that. On the first run it researches the business from its own public surfaces before asking anything, reads the account structure once, writes the plan folder, seeds the board, creates the creative doctrine, builds the dashboard, and registers the recurring jobs. It asks about exactly two things, the monthly ceiling and the daily cap, because those are the two numbers that decide how much money can leave. On every monthly run it re reads the evidence, corrects what the ledgers prove wrong, and reconciles drift.
日本語の概要は準備中です。原文の説明を表示しています。
Audit websites for SEO, technical, content, security, JS rendering, and AI readiness using SEOmator CLI. Returns LLM-optimized reports with health scores across 373 rules and 20 categories, and can diff two audits to show what a deploy changed. Use when analyzing websites, debugging SEO issues, checking site health, or comparing a site before and after a change.
日本語の概要は準備中です。原文の説明を表示しています。
Guided wizard to start a new feature. Asks what you want to build, recommends the right starting wave, and launches it.
日本語の概要は準備中です。原文の説明を表示しています。