Plantilles
Plantilles de projectes i de codi
daily-journal
mycelium-hq
Use when the user wants to journal, do a daily or end-of-day check-in, reflect on or vent about their day, brain-dump feelings, log what happened today, or says /journal. Also fires for quick one-line captures and a second session the same day (resumes that day's entry). Not for meeting notes (use meeting-todos), morning priorities (use rise), weekly/monthly reviews (use insights), or cross-entry pattern analysis (use patterns).
handoff
bdfinst
Compress or split off context for another session to pick up. Use to compress conversation history when context utilization approaches 40% (continue mode), or to split off a distinguishable out-of-scope side-task to an independent session (fork mode) — write a structured artifact for the other session and free the current one.
dating-profile-coach
davepoon
'Review and improve a dating profile on Tinder, Hinge or Bumble — rank the user''s photos and pick the lead photo, check them against the app''s official photo and AI-photo rules, then tighten the bio and suggest openers. Use when the user asks "which photo should be my first", "rate my dating photos", "can I use AI photos on Hinge/Bumble/Tinder", "fix my dating profile", or shares profile photos or a bio for feedback. Uses the free DatePhotos.AI MCP for official rules and photo scores when connected; falls back to a built-in checklist when it is not.'
manual-tester
tronghieu
Plan and run manual tests of the project's running app. Runs a session in one of five modes: exploratory, verification, smoke, assessment (UX, localization, accessibility, improvement review), or AI probe. Also writes a manual test plan that holds only what automated tests cannot judge. Use whenever the user asks, in any language, for something to be tested by hand or for a manual test plan — "manual test", "exploratory test", "bug hunt", "verify the bug fix", "smoke test", "QA this screen", "review this screen's UX", "what would you improve", "check the localized copy", "test the AI agent's answers", "write manual test cases", "kịch bản test manual" — or assigns a test design, test plan or test-case IDs to execute by hand. Not for writing automated tests.
gr-product-dev-ops
Gingiris-1031
🇺🇸 Your dev team ships features nobody asked for while user-reported bugs pile up for months. Operations blames engineering for ignoring users; engineering blames operations for not understanding technical constraints. This gives you the complete Product × Engineering × Operations alignment SOP — from unified backlog to 10-day sprint cadence to veto power rules. What's inside: • Dual-layer Kanban system (master backlog + sprint board with unified tagging) • 10-day sprint standard process (Day 1 dev → Day 6 testable build → Day 10 ship) • Issue template with reproducibility requirements (3x reported = auto-severe) • Tri-party alignment meetings (daily standup / sprint planning / sprint review) • Operations veto power on releases (P0 bug = block shipping) • User feedback → product iteration closed loop (beta testing + interview SOP) • Core metrics framework (acquisition → activation → retention → monetization → referral) • Technical debt management (20-30% sprint capacity reserved) • Ready-to-use templates: Bug Report, Sprint Planning, Responsibility Matrix Built from: Real product strategy meetings + beta testing frameworks. References Supabase sprint model, Manus/DeepSeek commercialization alignment. By @WeiYipei. 🇨🇳 你的研发团队在做没人要的新功能，用户反馈的 Bug 堆了三个月没人动。运营觉得研发不听用户，研发觉得运营不懂技术。这份 SOP 给你从统一看板到 10 天迭代节奏到一票否决权的完整产研运协同框架。 🇯🇵 開発チームは誰も求めていない機能を作り、ユーザーから報告されたバグは何ヶ月も放置。このSOPは、統一バックログから10日スプリント、リリース拒否権まで、プロダクト×エンジニアリング×オペレーションの完全な連携フレームワークを提供します。 🇰🇷 개발팀은 아무도 요청하지 않은 기능을 만들고, 사용자가 보고한 버그는 몇 달째 방치됩니다. 이 SOP는 통합 백로그부터 10일 스프린트, 릴리스 거부권까지 제품×개발×운영 완전 협업 프레임워크를 제공합니다. Triggers: "product ops" "engineering operations" "product development SOP" "sprint planning" "iteration management" "cross-functional alignment" "product engineering ops" "dev ops collaboration" "产研运协同" "迭代管理" "产品研发运营" "プロダクト開発運営" "제품개발운영"
community-ambassador-playbook
Gingiris-1031
You launched an ambassador program. 3 applications. One ghosted after week 2. Should you lower the bar? Offer more perks? Spam influencers? This gives you the complete community & ambassador operations SOP — from pre-launch checklist to recruitment to tiered management to retention to governance. Built from Notion (20M users, real ambassador interviews), AFFiNE (60K stars), Asana, and ClickUp programs. By @WeiYipei. 🇨🇳 你搞了个大使计划。来了3个申请。一个第二周就消失了。该降门槛？加福利？群发KOL？这份SOP给你从启动前置条件到招募到留存到治理的完整社区/大使运营方法论。基于 Notion（2000万用户，大使真实访谈）、AFFiNE（60K stars）、Asana、ClickUp 实战案例。 🇯🇵 アンバサダープログラムを立ち上げた。応募3件。1人は2週間で消えた。基準を下げる？特典を増やす？このSOPは、事前チェックリストから採用、段階管理、リテンション、ガバナンスまでの完全なコミュニティ＆アンバサダー運営フレームワークを提供します。Notion（2000万ユーザー）、AFFiNE（60K stars）の実例から構築。 🇰🇷 앰배서더 프로그램을 시작했습니다. 지원 3건. 하나는 2주 만에 사라졌습니다. 기준을 낮출까요? 이 SOP는 사전 체크리스트부터 모집, 단계별 관리, 리텐션, 거버넌스까지 완전한 커뮤니티 & 앰배서더 운영 프레임워크를 제공합니다. Notion(2000만 사용자), AFFiNE(60K stars) 실전 사례에서 구축. Triggers: "ambassador program" "community building" "community management" "DevRel" "developer relations" "community growth" "大使计划" "社区运营" "社区搭建" "コミュニティ運営" "アンバサダー" "커뮤니티 운영" "앰배서더" "open source community" "user retention"
gr-social-distill
Gingiris-1031
把一篇已发布的博客拆成 4 个社媒变体：X thread（10-15 推）、小红书笔记（3-5 图）、LinkedIn carousel、 dev.to / Zenn 二发。目标：在不新写博客的前提下激活 Organic Social 分发渠道。 当用户说"把这篇博客改成推特"、"做小红书版本"、"社媒分发"、"复用博客到多平台"时调用。
community-building-playbook
Gingiris-1031
Build and grow developer and user communities from scratch — covering ambassador programs, community-led growth (CLG), event operations, content strategy, and health metrics. Grounded in real playbooks from Notion, Lovable, AFFiNE, ClickUp, Asana, and Lark. Use when: building a community for an open-source project, SaaS product, or brand; recruiting and managing ambassadors or community leaders; planning community events (online/offline meetups, AMAs, hackathons); designing ambassador tier/points systems; setting community health KPIs; launching a Build-in-Public strategy; setting up Discord, Slack, or Lark communities; running developer relations (DevRel); or when the user asks about community operations, ambassador programs, CLG, user advocacy, KOC/KOL cultivation, UGC flywheels, community monetization, or any variation of "how do I grow my community".
gingiris-user-interview
Gingiris-1031
🇺🇸 User Interview & Cold-Start Operations Playbook — Battle-tested framework from HeyGen's 937 interviews to PMF. Complete SOP for user screening, interview execution, Beta testing methodology, cold-start user operations, churn analysis, and user grading systems. 🇨🇳 用户访谈与冷启动运营实战手册 — 基于 HeyGen 937 场访谈验证的 PMF 方法论。包含用户筛选、访谈执行、Beta 测试设计、冷启动用户运营、流失分析、用户分级体系完整 SOP。 🇯🇵 ユーザーインタビュー＆コールドスタート運営プレイブック — HeyGenの937回インタビューで検証されたPMF方法論。ユーザースクリーニング、インタビュー実行、Betaテスト設計、コールドスタートユーザー運営、離脱分析、ユーザーグレーディング。 🇰🇷 사용자 인터뷰 & 콜드 스타트 운영 플레이북 — HeyGen 937회 인터뷰로 검증된 PMF 방법론. 사용자 스크리닝, 인터뷰 실행, Beta 테스트 설계, 콜드 스타트 사용자 운영, 이탈 분석, 사용자 등급 시스템. Triggers: "user interview" "user research" "customer discovery" "PMF" "product-market fit" "beta test" "beta testing" "cold start users" "cold start operations" "churn analysis" "user grading" "用户访谈" "用户调研" "冷启动" "冷启动运营" "Beta测试" "流失分析" "用户分级"
critical-thinking
tronghieu
Audit the reasoning of a document or argument (memo, proposal, investment analysis, board paper, article, the user's own draft): claims, evidence, unstated assumptions, logical gaps, fallacies, and what would falsify it, each anchored to quoted text. Use whenever the user wants reasoning examined, in any language ("audit this argument", "is this analysis sound", "poke holes in this proposal", "review the logic of my draft"; Vietnamese "phản biện giúp tôi", "soi lập luận này", "tài liệu này có lỗ hổng gì", "góp ý bản nháp của tôi"), even when they never say "critical thinking". Also use when the user drops a document and asks whether to trust or act on it, or asks to see their reasoning profile. Not for company-level strategic bets (strategy-board) or learning a topic through dialogue (socratic-questor).
fiction-studio
tronghieu
A complete fiction-writing studio, run as a team of named specialist agents, that guides an author from a bare idea to a polished prose manuscript. Use this skill whenever the user wants to write, plan, or revise fiction — a novel, novella, short story, or series. Trigger on requests like "help me write a novel", "I have an idea for a story", "develop my characters", "build a world for my fantasy", "outline my plot", "fix this scene", "my dialogue feels flat", "give me beta-reader feedback", or any time the user is doing creative storytelling and would benefit from structured, craft-aware guidance. Also trigger when the user names a studio member (Homer, Aristotle, Fyodor, Tolkien, Scheherazade, Oscar, Max, Virginia, Borges, Bloom) or asks to switch creative roles / bring in a specialist.
template-manager
Kodria
"Administra las plantillas de documentación del proyecto. Úsala cuando necesites crear un nuevo formato de documentación transversal o mejorar uno existente. Supports plan-driven execution with subdelegation to support skills."
Prompting
danielmiessler
Meta-prompting system for dynamic prompt generation using templates, standards, and patterns. USE WHEN meta-prompting, template generation, prompt optimization, or programmatic prompt composition.
risk-assessment-methodology
Hack23
Systematic risk identification, analysis, evaluation, and treatment aligned with ISO 27005, NIST RMF, and Hack23 ISMS risk register
clay
sachacoldiq
Expert Clay platform consultant for B2B data enrichment and workflow automation. Use when the user asks about Clay tables, waterfall enrichment, Clay credits, Clay pricing, Claygent, Clayscript formulas, Clay CRM sync, Clay enrichment workflows, Clay integrations, Clay Chrome extension, Clay templates, or building data pipelines in Clay. Also triggers on "Clay workflow", "enrichment waterfall", "Clay credits", "Claygent", "Clayscript", "Clay + HubSpot", "Clay + Salesforce", "Clay table", "Clay providers", "enrich in Clay", "Clay API", "Clay column", "Clay formulas", "find emails", "email waterfall", "phone waterfall", "lead scoring", "Clay debugging". Do NOT use for general CRM questions without Clay context, standalone email tools (Findymail, Hunter), or non-Clay enrichment platforms.
email-1-variations-7
sachacoldiq
7 Email 1 variations from ColdIQ core framework plus Email 2 and Email 3 templates. Use when crafting the first email in a sequence, testing different opening structures, or building complete email cadences.
coldiq-messaging-templates
sachacoldiq
6 ColdIQ messaging templates - Ask Before Pitch, Not Too Different Persona, Upfront Value, Leverage Content, and Why Are You Paying. Use when creating outreach campaigns, A/B testing message structures, or choosing a messaging approach.
cold-email
sachacoldiq
Expert cold email strategist for B2B outbound campaigns. Use when the user asks about cold email writing, email sequences, email deliverability, domain warmup, SPF/DKIM/DMARC setup, email personalization, cold email templates, email copywriting frameworks, email compliance (CAN-SPAM, GDPR), bounce management, inbox placement, email infrastructure, sequencing tools (Instantly, Smartlead, Lemlist), or cold outreach strategy. Also triggers on "cold email", "email sequence", "deliverability", "warmup", "SPF", "DKIM", "DMARC", "bounce rate", "spam", "inbox placement", "email template", "follow-up email", "outbound email", "Instantly", "Smartlead", "email copy", "subject line", "personalization". Do NOT use for marketing emails or newsletters.
lead-sources-guide
sachacoldiq
Lead sources by use case with Clay delivery-ready templates - Apollo, LinkedIn Sales Navigator, Clay, Ocean.io, Openmart, and Local Directories. Use when choosing lead sources, building prospecting workflows, or setting up data enrichment.
list-building-tips
sachacoldiq
Pro tips for B2B list building - source mixing, enrichment workflow, template usage, and efficiency principles. Use when building prospect lists, optimizing data quality, or improving prospecting efficiency.
personalization-playbooks
sachacoldiq
Camp Personalization vs No Personalization playbooks by outreach category - Inbound, Postbound, Bridgebound, and Outbound. Use when deciding personalization level, building automated sequences, or creating messaging templates.
ai-personalization-prompts
sachacoldiq
6 AI personalization prompts (lemlist style) plus 2 email templates - ICP Identification, Company Description, Similar Product, Top 3 Problems, Subject Line, Case Study Reference, and Similar Company Approach. Use when setting up AI-powered personalization, building Clay/lemlist workflows, or automating research.
book-architect
robertguss
Design the structural and emotional architecture for nonfiction books. Use when an author has a validated book concept and needs to create the blueprint before drafting. Triggers include requests to structure a book, create a chapter outline, design a table of contents, map the reader's journey, or plan book organization. Requires upstream documents from book-ideation (Book Concept Document) and optionally from idea-validator (Validation Report) and market-research (Market Research Report).
writing-assistant
yunshu0909
写作助手 - 当用户说"我想写XX"、"帮我梳理选题"、"怎么形成框架"、"给我组织思路"时触发。根据观点清晰度自动选择最优路线：清晰观点走"框架→内容"，模糊观点走"挖掘→选题→框架→内容"。