Product & Planning

rashidee Skill

Apply a free-form requirement change to the PRD.md files of a CO2 project. Takes a human-written prompt describing NEW requirements or updates to existing ones, analyzes the PRD.md of every custom application to determine which applications, modules and subsections (User Story, Non Functional Requirement, Constraint, Reference, Test) are impacted, and decides for each impacted item whether to ADD, CANCEL or MODIFY it. Automatically classifies the change complexity per application as major, minor or patch, computes the next semantic version, and writes the new/updated items under a NEW version tag layered on top of the existing versions in each PRD.md — never rewriting or deleting prior versions. Cancelled items are struck through in place and recorded in the new version. New items are tagged with unique IDs (via util-ustagger) and a CHANGELOG.md entry is appended per impacted application. Presents an impact plan for human confirmation before writing (skippable with `--auto-approve` for orchestrated runs). ALW

rashidee Skill

Tag new items in PRD.md files with unique ID codes and validate no duplicate tags exist. Applies to PRD.md documents structured with module sections containing User Stories, Non Functional Requirements, Constraints, References, and Test instructions. Each top-level bullet item gets a unique 9-character code with category prefix, application initials, and running number (interval of 3). Trigger on keywords: "tag user story", "tag user stories", "fix user story tag", "fix user story tags", "add IDs to requirements", "tag items in PRD.md", "number the requirements", "add requirement codes", "validate tags", "check duplicate tags", "verify tagging completeness". Accepts an application name and version as input (e.g., `/util-ustagger hub_middleware v1.0.3`, `/util-ustagger "Hub Middleware" v1.0.3`).

rashidee Skill

Requirement-to-code traceability generator — links every PRD requirement ID (User Stories, Non-Functional Requirements, Constraints) and bug code from a module's SPEC.md to the source code that implements it, and writes a per-application context/TRACEABILITY.md matrix. Resolves links primarily from the in-source CO2 traceability comments written by conductor-feature-develop and conductor-defect (e.g. `Implements: USHM00003`, `Bug fixes: [BUG-024]`), with a name-based source-scan fallback, and OPTIONAL precision enrichment from the codebase-memory knowledge graph when that MCP server is installed. Works fully WITHOUT codebase-memory. Takes an application name (mandatory), with optional version and module filters. Use when the user asks to "generate traceability", "update the traceability matrix", "link requirements to code", "regenerate TRACEABILITY.md", or when invoked as a sub-step by the feature/defect conductors after code or bug-fix changes.

rashidee Skill

Analyze PRD.md files for quality issues: incomplete sentences, non-existent references, cross-module inconsistencies, contradictory requirements, duplicate roles, design system validation, architecture principle violations, and process flow coverage gaps. Validates bi-directional coverage between User Stories/NFRs and High Level Process Flows — detects modules not covered by any process flow and process flow steps not covered by any User Story or NFR. Adds inline [TODO] annotations directly into the PRD.md file for each issue found. Trigger on keywords: "analyze user story", "analyze user stories", "check user story quality", "validate user stories", "find user story issues", "audit user stories", "review user stories", "check requirements quality", "find inconsistencies", "find contradictions". Accepts an application name as input (e.g., `/util-usanalyzer mainapp`, `/util-usanalyzer "Main App"`).

rashidee Bundle

Initialize a new CO2 project by validating a hand-authored brainstorm session document and setting up the file-based, turn-based BRAINSTORMING session kit around it. The ONLY valid input is the path to an EXISTING `<topic>.brainstorm.md` file the user authored from the CO2 application-development template (`brainstorm-template-appdev.md`) — free-form prompts, idea text or topic slugs are NOT accepted. The skill strictly validates the session document against the template, rejecting with a report on any deviation — it never creates or edits the session document. On a clean pass it scaffolds the rest of the brainstorm kit in the project folder: the shared `brainstorm-protocol.md`, the `co2-context-generation-guide.md` artifact rules, and the `/brainstorm-loop` slash command. The user then manually runs `/brainstorm-loop` — an iterative, token-efficient loop that converges the root `CLAUDE.md` (Phase A) and every application's `PRD.md` (Phase B) round by round. This skill seeds the project — it is the first skil

rashidee Skill

Synchronize project folder structure, PRD.md, and BUG.md files based on the canonical application and module definitions in CLAUDE.md. Validates dependencies (circular, missing, logical) and checks for orphaned services across all applications. Creates missing application folders, scaffolds new PRD.md and BUG.md files from templates, adds missing module sections to existing files. Inserts [TODO] annotations into CLAUDE.md for validation failures. Trigger on keywords: "sync project", "project sync", "sync folders", "sync modules", "sync PRD", "sync BUG", "initialize project structure", "scaffold project", "create project folders", "sync application structure", "validate dependencies". Accepts no arguments — reads all configuration from CLAUDE.md.

arc-mcp Skill

System-wide inventory of open transport requests — every visible modifiable request, who owns it, how big it is, and supported risk signals such as empty/local requests, explicit locks, and confirmed manifest overlaps. Headers-only and cheap; NO source diffs. Use when asked "what transports are open in the system", "show all open transports", "transport backlog", "what is everyone working on", "basis transport overview", "which requests are ready to release", or "find import-order conflicts".

jiayaoqijia Skill

Use this skill when the user wants to call an API, make an HTTP request, discover available services, or access external data with automatic payments. Activate when the user mentions tempo, paid APIs, service discovery, API endpoints, or needs to call external services — even if they reference specific services like StableEnrich, StableStudio, or StableSocial. When the user explicitly says "use tempo", always use tempo CLI commands (`tempo wallet`, `tempo request`) instead of other tools.

deokjinlog Bundle

You MUST use this before creating any feature, component, or behavior change. Offers two modes — PRD (structured, default) for productisation work, or Socratic (free-form, upstream-superpowers style) for exploratory/internal work. Both modes write <slug>-requirements.md to docs/features/YYYY-MM-DD-<slug>/. Does NOT cover technical design — that belongs to tech-design.

deokjinlog Skill

Upstream-original (superpowers 5.0.7) brainstorming, exposed under intent-locked-workflow. Use when invoked via /og-brainstorm — free-form Socratic dialogue producing docs/superpowers/specs/YYYY-MM-DD-<topic>-design.md, terminal state is og-writing-plans. Identical behavior to upstream brainstorming except for the og- naming and downstream pointer. Use this when the intent-locked-workflow extended workflow (PRD + 변경이력 + 위험 주석) feels heavy and you want the original superpowers experience.

flox Skill

This skill should be used when exploring code in a project for "investigation", "design research", "finding what changed", "git log analysis", or "finding precedent". Provides git log analysis, code reading strategies, and file:line reference patterns. Do not use for Forge planning file reading.

goiltpatpat Skill

Inspect the active agent host and install or validate Patpat through its supported native plugin manager or an explicit Agent Skills directory. Use for Patpat installation, discovery, update, removal, or host compatibility questions.

guillaumemeyer Skill

Trendy scoring stage (PRD §4.2). Assigns per-dimension scores (velocity/sensitivity/competition/sustainability, each 0–10), the weighted total_score, per-category risk scores (copyright/political/adult/health/ sensitivity), the global risk_score (max of categories), lifecycle, and potential bucket for every reported trend. Run after detection/reporting; weights come from PocketBase settings (settings.scoring.weights).

guillaumemeyer Skill

X API v2 trends source (PRD §4.1, §6.8). Calls GET /2/trends/by/woeid (default WOEID 1 = worldwide) with Bearer auth from X_API_KEY. Skips gracefully when the key is absent. Capped at 20 trends per run; hashtag-only entries are filtered out.

guillaumemeyer Skill

Trendy adapter of memo `design/impeccable` (PRD §10.1). Design critique and polish pass before a store moves to store review: hierarchy, spacing, color contrast, and conversion focus.

guillaumemeyer Skill

Trendy Build stage (PRD §4.6). Builds the actual storefront deliverables for a store in `building`: final HIGH-DEF assets + print files (correct DPI per Printful specs), final blog posts, SEO/AEO/GEO first pass, GA4 wiring, and a store review package. Advances `building → store_review` on completion.

guillaumemeyer Skill

Trendy adapter of memo `brand/brand-strategy` (PRD §10.1). Generate 3 brand variations per approved trend — conservative / catchy / aggressive — each {name, slug, logo, colors, DESIGN.md}.

guillaumemeyer Skill

Chat-based refinement for the Strategy approval chat (PRD §4.5 AC3). Proxies operator messages from the back-office dashboard to Hermes /v1/chat/ completions with the trend's full context; interprets refinement requests and triggers stage re-runs (branding, creatives, products, site, blog drafts).

guillaumemeyer Skill

Trendy Strategy Approval stage (PRD §4.5). For each approved trend, generate a preview-only strategy package: 3 brand variants, 6 illustration concepts per variant (LOW-RES previews), Printful product selection with pricing, site preview, and 6 draft blog articles. Nothing is live, no Printful sync, no route. Kicked off by the build-check cron every 15 min.

guillaumemeyer Skill

Trendy adapter of memo `seo/daily-seo-analysis` (PRD §10.1). Weekly SEO/AEO review per store after live: meta/tags/sitemap/schema health, Search Console data when available, and actionable fixes written back to the store's seo fields.

guillaumemeyer Skill

Key-free Google News RSS source (PRD §4.1, §6.6). Fetches https://news.google.com/rss (hl=en-US&gl=US&ceid=US:en), parses item/entry blocks, and returns signals for clustering. Budget-aware: one feed fetch per run, capped at 25 items.

guillaumemeyer Skill

Trendy adapter of memo `google/google-analytics` (PRD §10.1). GA4 wiring: one shared property, gtag.js on every storefront page, store identity as a custom dimension, and the 8 custom events (PRD §6.3).

guillaumemeyer Skill

Trendy detection stage (PRD §4.1). Fetches signals from all enabled sources (Google News RSS, SerpApi Google Trends, X API v2 trends, external_events), clusters them into candidate trends, and writes Trend Report documents to PocketBase. Daily cadence via Hermes gateway cron. Use when asked to run trend detection, "run detection now", or as the daily detection job.

guillaumemeyer Skill

Trendy adapter of memo `images/images-generation` (PRD §10.1). Generate LOW-RES previews at Strategy and final HIGH-DEF assets + print files at Build, with bounded cost: previews first, HD only after approval.

guillaumemeyer Skill

Trendy marketing analysis stage (PRD §4.3). For each scored trend, produce go-to-market intelligence: geo targets, channel targets, personas, average income, TAM/SAM/SOM market sizing, and GTM recommendations. Loads the marketing-strategist agent profile for framing. Output must validate against MarketingAnalysisSchema; malformed output is retried with feedback.

guillaumemeyer Skill

Weekly trend reassessment (PRD §4.10.1). For each LIVE store, re-evaluate the trend behind it on current data (signals + GA4 + orders KPIs), re-score dimensions/risk/lifecycle, and write a SUGGEST-ONLY refresh proposal (refresh_proposals). Nothing on a live store changes until the operator approves a proposal.

guillaumemeyer Skill

Trendy adapter of memo `creative/creative-concepts` (PRD §10.1). Generate 6 illustration concepts per brand variant (18 per trend at Strategy), each a single dominant motif that keeps the trend legible on a tshirt/mug/tote.

guillaumemeyer Skill

Trendy adapter of memo `medias/media-asset-tagging` (PRD §10.1). Tag every generated asset with store, trend, product-type and usage tags so assets are queryable across stores and stages.

guillaumemeyer Skill

Trendy adapter of memo `aeo-geo/aeo-geo-optimization` (PRD §10.1). First AEO/GEO pass at Build: schema markup, structured Q&A content, entity coverage — making store pages answerable by AI assistants and search engines.

guillaumemeyer Skill

Manages the curated external_events collection in PocketBase (PRD §4.1, §5.4) and feeds events as signals. Tier filter: Tier 1/2 for candidate trends, Tier 3 optional. Key-free. Also used to add/update events from the back-office manual entry form.

guillaumemeyer Skill

Trendy adapter of memo `creative/creative-brief-organic` (PRD §10.1). Build the organic-content brief for the blog drafts: angle, audience, SEO target, and CTA that ladder up to the store's products.

guillaumemeyer Skill

Trendy adapter of memo `content/organic-content-pipeline` (PRD §10.1). End-to-end organic blog content: 6 drafts at Strategy → final at Build → publish 3/week after live, each with SEO/AEO/GEO meta and an Unsplash illustration.

guillaumemeyer Skill

Trendy adapter of memo `creative/creative-image-tech-specs` (PRD §10.1). Printful production specs for generated assets: DPI, file format, size and safe-zone rules per product type (tshirt/mug/tote), used by the Build stage when finalizing HIGH-DEF assets + print files (PRD §4.6 AC2).

guillaumemeyer Skill

Trendy adapter of memo `creative/creative-image-art-direction` (PRD §10.1). Art-direct the image prompts for each concept: composition, color, lighting, and mood boards consistent with the selected brand variant's DESIGN.md.

iamzifei Bundle

📐 詹明明·找对标 ——找对标。给一个方向就去抖音/小红书/视频号搜人，给一个名字就去认人；三筛过滤（赚钱 / 看懂 / 能仿）挑出真正值得抄的那个，然后把他的**三批内容**全扒下来——最早 10 条（他怎么起的号）、数据最好 10 条（什么能爆）、最新 10 条（他现在在哪）——封面、大字、逐字稿、互动数据一条不落，最后出完整拆解和抄袭路线图。 触发方式：/zmm-benchmark、/找对标、/对标、「我该学谁」「帮我找个对标」「这个号值不值得学」「把这个博主拆一下」「他是怎么起号的」「扒一下这个账号」 Find and dissect a benchmark creator: search by direction or by name, filter on money/understandable/copyable, then pull the earliest 10, best-performing 10, and latest 10 posts with covers, cover text, transcripts and engagement data, and produce a full teardown plus a copy roadmap. Trigger: /zmm-benchmark, "find me a benchmark account", "is this creator worth learning from", "tear down this account" —— 📐 詹明明 · 不给公式，给判据。每条规则都标了实测代价。

ievo-ai Skill

Use this skill when the user asks "what does owner/repo contain", "inspect this skill before install", "show me what's in owner/repo", "summarise owner/repo without installing", "what skills does this repo have", or invokes /ievo:inspect <owner>/<repo> — not for listing your own project's already-installed evolution overlays (use /ievo:overlay-status for that). Pre-install structured summary of a remote skill/plugin repo. Fetches the repo tree and key files via gh API, then renders a human-readable capability overview — skills, agents, commands, scripts, permission footprint — without triggering discovery, security scan, or install.