Guide for using the Pinecone CLI (pc) to manage Pinecone resources from the terminal.
Reference for the Pinecone MCP server tools.
Autonomous adversarial build↔review loop between a builder and a reviewer using git commits as the baton, until a clean verdict — then ship.
Use the `pingcode` CLI to work with PingCode (研发管理): 敏捷项目管理 (pjm) projects and work items — list and search work items (工作项), read a…
Comprehensive guide for building high-performance Solana programs using Pinocchio - the zero-dependency, zero-copy framework.
Official Pinterest Gestalt Design System guidelines, React component patterns, masonry grids, pin cards, color tokens, and design-md…
Autonomous pipeline orchestrator — runs one or more milestones end-to-end by composing ccb, plan-milestone, milestone, epic, and issue…
Design or audit B2B sales pipeline — define stage names, entry/exit criteria, qualification standards, and CRM field requirements.
Map the full CI/CD pipeline — triggers, build, test, deploy flow — with risk assessment.
Generate investor-ready pitch decks as branded PPTX files from founder meeting notes, uploaded decks, DD reports, and strategy docs.
Product marketer — positioning, messaging, value prop, GTM strategy, and launch copy.
Strict per-page visual-conformance audit at the verify phase — ONE page/route against a source of truth (Figma MCP nodes, or reference…
Diagnose Pixel and Shannon IMS Wi-Fi Calling failures with read-only ADB evidence, distinguish ePDG/IKE/IPsec failures from IMS/SIP…
Generate pixel art assets via the PixelLab REST API v2 — animations, UI elements, sprites, and image editing.
Pixel-art asset generation for game projects, MCP-first via the connected pixellab MCP server (mcp__pixellab__* tools).
Rewrites complex concepts into jargon-free, plain language while automatically generating structured Org-mode notes.
Use before any implementation — understands the request, discovers project context, and proposes a concise plan for user approval before…
Planning and clarification workflow for requested code changes.
Use when renaming routes, packages, modules, APIs, configuration keys, or persisted contracts while existing consumers may remain.
Carmack-level plan review via RepoPrompt or Codex.
Carmack-level plan review via rp-cli context builder + chat.