Productivity

pproenca Skill

This skill should be used when the user asks to "create worktree", "remove worktree", "work in worktree", "switch to worktree", "clean up worktree", mentions "repo--branch pattern", or during plan execution when worktree isolation is needed. Documents the sibling directory worktree pattern for simple, safe git worktree workflows.

pproenca Skill

This skill should be used when the user reports a "bug", "not working", "fix this", "debug", "test failing", or when investigating unexpected behavior. Four-phase framework ensuring root cause understanding before attempting solutions.

pproenca Skill

This skill should be used when processing code review feedback, responding to reviewer comments, or when feedback seems unclear or technically questionable. Requires verification before implementing.

pproenca Skill

This skill should be used when reviewing test code, the user asks "is this test good", "test quality", "mock properly", or when tests behave unexpectedly. Identifies common testing mistakes.

pproenca Bundle

This skill should be used when the user mentions "flaky tests", "race condition", "timing issues", "wait for", "test sometimes fails", or when tests have inconsistent pass/fail behavior. Replaces arbitrary timeouts with condition polling.

pproenca Skill

Use this skill when implementing any feature, bug fix, or plan task. Triggers on "write tests", "add a test", "do TDD", "test-driven", "implement with tests", "implement task", or when dispatched as a subagent for plan execution. Write test first, watch it fail, write minimal code to pass.

pproenca Skill

Guide completion of development work by presenting merge/PR options. Use when "I'm done", "merge this", "create PR", "finish up", or when implementation is complete and tests pass.

pproenca Skill

This skill should be used when claiming a task is "done", "complete", "finished", "fixed", "passing", or before committing. Requires running verification commands before making success claims.

rongxinzy Bundle

将会议录音文字稿、笔记或聊天记录等原始材料整理为结构化会议纪要，自动提取议题、讨论要点、结论以及包含负责人与截止日期的行动项。当用户提供会议素材并提及会议记录、纪要、meeting minutes、会议总结、行动项、整理会议或会后跟踪等关键词时触发。

rongxinzy Bundle

Read and send email via IMAP/SMTP. Check for new/unread messages, fetch content, search mailboxes, mark as read/unread, and send emails with attachments. Works with any IMAP/SMTP server including Gmail, Outlook, 163.com, vip.163.com, 126.com, vip.126.com, 188.com, and vip.188.com.

rongxinzy Bundle

飞书多维表格（Base）操作：建表、字段、记录、视图、统计、公式/lookup、表单、仪表盘、workflow、角色权限；遇到 Base/多维表格/bitable 或 /base/ 链接时使用。文件导入转 lark-drive，认证/授权转 lark-shared。

fudesign2008 Skill

Git commit unified entry point. Triggers when user says 「提交代码」「git commit」「帮我提交」「写 commit message」「生成 commit」「提交一下」「git-commit」「自动提交代码」「git-commit-auto」 (commit code / help me commit / write commit message / generate commit / auto commit), or when invoked by jira-fix-workflow phase 7.

fudesign2008 Skill

Triggers when the user says「批量修复」「批量 jira-fix」「jira-fix-queue」「jira-fix-batch」「批量修复多个 Jira」「批量修复以下 bug」/ batch fix, batch jira-fix, jira-fix-queue, jira-fix-batch. Thin trigger shell: parse Jira IDs/URLs and enqueue them into goal-driven-queue with Engine jira-fix-workflow. Does not run fixes or merge. Do NOT use for a single issue (jira-fix-workflow) or a non-Jira queue (goal-driven-queue).

fudesign2008 Bundle

Eight-stage PDCA workflow for systematically solving bugs, refactors, and feature-development tasks: clarify → analyze → explore solutions → review → plan → execute → verify → retrospect. Manual mode (default) pauses for user confirmation at each stage exit; auto mode runs end-to-end; ai-proxy overlay (thin freeze then occupy) is available independently. Triggers — 「明确问题」「分析问题」「探索方案」「审查方案」「制定计划」「执行计划」「检查验证」「复盘改进」(alias「回顾总结」)；「继续分析」「深入分析」「修改方案」「完善方案」「优化方案」「更新计划」「修订计划」「修改计划」；「自动模式」「自动分析」「自动解决」；「ai-proxy 模式」「AI 代理模式」「切换 ai-proxy」 / clarify problem, analyze problem, explore solutions, review solution, make plan, execute plan, verify, retrospective, auto mode, ai-proxy mode, switch to ai-proxy.

fudesign2008 Skill

TypeScript type-checking workflow. Use this skill whenever the user works with TypeScript and mentions type errors, type checking, or says "类型检查" (type check), "type-check", "tsc", "检查类型" — even if they don't explicitly ask for a "type check" but are encountering compilation or type issues in a TypeScript project.

fudesign2008 Bundle

End-to-end Jira bug-fix workflow (stages 0-10), driven by a single Jira link, from intake through PR/MR merge and Jira writeback. Manual mode (default) pauses for confirmation between stages; auto/force modes run end-to-end; ai-proxy overlay (thin freeze then occupy) is available independently. Triggers — 「修复这个 bug [URL]」「帮我修复 [URL]」「jira-fix [URL]」「自动修复 [URL]」「强制修复 [URL]」「继续修复」「从上次继续」；「ai-proxy 模式」「AI 代理模式」「切换 ai-proxy」 / fix this bug, jira-fix, auto fix, force fix, resume fix, ai-proxy mode, switch to ai-proxy. Do NOT use for batch fixes across multiple issues — use jira-fix-queue instead (it enqueues into goal-driven-queue; confirm, then run the queue).

fudesign2008 Bundle

Structured retrospective and knowledge sediment for completed work (the Act phase of PDCA). Run a disciplined post-work review (Keep-Problem-Try / Stop-Start-Continue / After-Action Review by context), judge which lessons are worth solidifying, pick the right carrier, validate the sediment gets reused, and feed improvements back. Use whenever finished work needs reflection — as a PDCA host closeout/review stage via frontmatter dependencies, or standalone on any completed task. Triggers — 「回顾总结」「复盘」「经验沉淀」「总结经验教训」「改进闭环」「沉淀规则」「项目复盘」 / learn and improve, lessons learned, retrospective, post-mortem, debrief.

fudesign2008 Skill

Ensure the current project has a proper test suite — detect tech stack & framework, scaffold if needed, generate unit tests (required, logic code only), and optionally generate/run E2E tests. Triggers when user says "test-suite-ensure", 「补全测试」「生成测试」「确保测试」「补充单元测试」「添加单元测试」「检查测试覆盖」 (complete tests / generate tests / ensure tests / add unit tests / check test coverage). Also callable by solve-workflow and opsx-solve-workflow in their execution-stage test steps.

fudesign2008 Bundle

Design-to-plan host: thin wrap of Superpowers brainstorming, then hard handoff to solve-workflow Make a Plan. Use for new features and fuzzy design before coding. Triggers — 「头脑风暴」「设计头脑风暴」「brainstorm」「brainstorm workflow」「先设计再计划」「头脑风暴工作流」. Do NOT use for bug root-cause PDCA (solve-workflow / opsx-solve-workflow) or when you only need a one-line edit.

fudesign2008 Skill

Triggers when the user says「opsx 批量修复」「批量 opsx-jira-fix」「opsx-jira-fix-queue」「opsx-jira-fix-batch」「批量 OpenSpec Jira 修复」/ opsx batch fix, batch OpenSpec Jira fix, opsx-jira-fix-queue, opsx-jira-fix-batch. Thin trigger shell: parse Jira IDs/URLs and enqueue them into goal-driven-queue with Engine opsx-jira-fix-workflow. Does not run fixes or merge. Do NOT use for a single issue (opsx-jira-fix-workflow) or a non-Jira queue (goal-driven-queue).

fudesign2008 Bundle

Eight-stage PDCA problem-solving workflow that persists analysis, proposal, design review, plan, execution, and verification into OpenSpec artifacts (openspec/changes/<name>/, archived into openspec/specs/) instead of leaving them only in chat context. Use for feature work, bug fixes, refactors, and complex engineering tasks that need long-term behavioral-contract traceability, team review, or auditability. Do NOT use for a quick one-off edit with no traceability need — use solve-workflow instead. Triggers：「opsx解决」「OpenSpec解决」「规范化解决」「创建OpenSpec变更」「创建opsx变更」「用OpenSpec分析」「用OpenSpec修复」「opsx自动解决」「OpenSpec自动解决」「opsx-solve」「opsx-solve-workflow」；「ai-proxy 模式」「AI 代理模式」「切换 ai-proxy」 / opsx solve, OpenSpec solve workflow, create an OpenSpec change, ai-proxy mode, switch to ai-proxy.

fudesign2008 Bundle

OpenSpec-flavored end-to-end Jira bug-fix workflow that persists root cause, behavior change, fix plan, verification, and archive into OpenSpec artifacts (openspec/changes/<name>/, archived into openspec/specs/) instead of leaving them only in chat context or Jira comments. Use when a Jira issue needs long-term behavioral-contract traceability, team review, or auditability. Do NOT use for a quick fix needing no traceability — use jira-fix-workflow instead. Triggers：「opsx-jira-fix」「OpenSpec Jira 修复」「规范化修复 Jira」「opsx修复Jira」「Jira OpenSpec 修复」「opsx自动修复Jira」「用OpenSpec修复Jira」「opsx-jira-fix-workflow」；「ai-proxy 模式」「AI 代理模式」「切换 ai-proxy」 / opsx jira fix, OpenSpec Jira fix workflow, ai-proxy mode, switch to ai-proxy.

jaygptpro Skill

Generate a structured negotiation script for Alibaba, Canton, or domestic suppliers. Covers 7 levers (unit price, MOQ, payment terms, lead time, packaging, QC, tariff sharing) and produces email templates per negotiation round. Use when a user asks how to negotiate with a supplier, Alibaba negotiation, MOQ negotiation, supplier email scripts, or getting better terms. Trigger phrases: "negotiate supplier", "Alibaba", "MOQ", "payment terms", "supplier script", "supplier email". Works with zero tools.

77cinc Bundle

Satoshi Nakamoto's thinking framework and expression DNA. Based on 575 Bitcointalk posts, the 2008 Whitepaper, and final email correspondences. Refines 5 core mental models, 5 decision heuristics, and a 3-stage Expression DNA. Use when analyzing trustless systems, incentive design, or decentralized architecture. Trigger words: "Satoshi perspective", "What would Satoshi do?", "Trustless consensus view".

mizchi Bundle

Use when working with the `dotenvx` env-var management tool — encrypting .env files, juggling multiple environments (.env.production / .env.staging / .env.ci), committing encrypted secrets to git with `.env.vault` / `.env.keys` / `.env.encrypted`, or wiring dotenvx into GitHub Actions. Trigger on `.env.vault` / `.env.keys` / `dotenvx` commands or symptoms (env-var leak risk, env per-stage management, encrypted secrets workflow) even if the user does not say "dotenvx" by name.

salesforcecommercecloud Bundle

Write efficient data queries in B2C Commerce for products, customers, and orders. Use this skill whenever the user needs to search products on a storefront page, look up customer profiles, query orders, paginate search results, or fix slow category pages. Also use when they ask about performance problems with data access, replacing database-intensive APIs with index-backed alternatives, or choosing between search vs query methods — even if they just say "my category page is slow" or "how do I find customers by email".

salesforcecommercecloud Bundle

Create custom job steps for B2C Commerce batch processing. Use this skill whenever the user needs to write a batch job, data export script, scheduled cleanup task, or any server-side processing that runs on a schedule. Also use when they ask about steptypes.json, chunk-oriented vs task-oriented job steps, read/process/write patterns, how to get a custom job to appear in Business Manager, or how to author and import a jobs.xml job definition (job/flow/step structure, step type, the required triggers element) so a step type becomes a runnable, schedulable job — even if they just say "I need a script that runs nightly" or "batch process orders".

salesforcecommercecloud Bundle

Implement SLAS authentication patterns in B2C Commerce including passwordless login (email OTP, SMS OTP, passkeys), session bridging between PWA Kit/Storefront Next and SFRA, hybrid authentication (B2C 25.3+), token refresh flows, trusted system on behalf of (TSOB), and JWT validation. Use this skill whenever the user asks about shopper authentication beyond basic login, token exchange flows, passwordless or biometric auth, keeping sessions alive across storefronts, handling 409 Conflict errors on token endpoints, refreshing shopper tokens, or validating JWTs — even if they don't mention SLAS by name.

ticruz38 Bundle

AI-powered email prioritization and triage system. Automatically classifies emails by category and priority, with bulk actions and undo support.

ticruz38 Bundle

Generate content using AI - blog posts, social media captions, email templates

ticruz38 Bundle

Generate email reply suggestions with multiple tone options and context-aware drafting. Built on top of email skill for reading messages and sending replies.

ticruz38 Bundle

Email Summarizer

ticruz38 Bundle

Protect focus time on calendar for deep work

ticruz38 Bundle

Real estate property showing scheduler with calendar coordination, lockbox management, client feedback, and route optimization

wulaosiji Bundle

RSS订阅源处理与管理工具，支持RSS内容解析、订阅管理、内容聚合、关键词筛选和自动化分发（邮件/报告）。 Use when: "解析RSS源", "RSS订阅管理", "内容自动采集", "parse RSS feed", "manage RSS subscriptions", "RSS转邮件", "news feed monitoring", "博客播客追踪". 支持批量解析、关键词过滤和去重，适用于新闻聚合和内容监控。Cross-references: content-extractor, wechat-article-fetcher, twitter-scraper, email-sender, document-hub. Built by UniqueClub 🌐 https://uniqueclub.ai

managedcode Bundle

Maintain or assess Workflow Foundation-based solutions on .NET Framework, especially where long-lived process logic or legacy designer artifacts still matter. USE FOR: WF activities and workflows; designer-backed process logic; long-lived workflow state and persistence; keep, isolate, or replace decisions. DO NOT USE FOR: unrelated stacks; generic tasks that do not need this specific guidance. INVOKES: inspect the repository context, edit targeted files, and run relevant build, test, lint, or validation commands when changes are made.