Productivity

planifest Bundle

Performance profiling workflow for CPU/memory/I/O hotspot localization and optimization prioritization. Use when regressions or inefficiencies require profiler-based evidence for optimization decisions; do not use for non-performance functional acceptance decisions.

planifest Bundle

Conceptual data modeling workflow for domain entities, relationships, and lifecycle boundaries. Use when teams must align on domain meaning before logical/physical schema decisions; do not use for index-only or migration-only tasks.

planifest Bundle

Django application development workflow for production-grade app changes. Use when Django-specific code (models, views, serializers/forms, routing, settings, middleware, auth flows) must be implemented or revised with framework runtime behavior in scope; do not use for repository-wide architecture governance or release management policy.

planifest Bundle

Select and apply minimal hotfix commits across branches via cherry-pick with dependency risk control. Use when urgent fixes must be propagated without pulling unrelated changes; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Observability alerting workflow for signal quality, routing policy, and actionable thresholds. Use when alert rules need design or tuning to detect incidents with clear ownership and noise control; do not use for business-feature implementation logic.

planifest Bundle

Style, review, and refactoring standards for PowerShell scripting. Trigger when `.ps1`, `.psm1`, `.psd1` files, or CI workflow blocks with `shell: pwsh` or `shell: powershell` are created, modified, or reviewed and PowerShell-specific quality controls (error handling, parameter validation, readability, operational safety) must be enforced. Do not use for Bash, generic POSIX `sh`, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

planifest Bundle

Redis caching workflow for latency improvement with explicit key strategy, TTL/invalidation policy, and correctness bounds. Use when Redis-backed caching decisions are required for application performance; do not use for repository-wide architecture governance or release management policy.

planifest Bundle

Property-based testing workflow for invariant validation over broad input spaces. Use when correctness depends on rules that must hold across many generated inputs; do not use for narrow deterministic examples only.

planifest Bundle

Replication and sharding workflow for scaling read/write throughput while managing consistency, failover, and data distribution risk. Use when single-node limits are reached or resilience requires topology changes; do not use for local query tuning only.

planifest Bundle

Requirement elicitation workflow for collecting, reconciling, and structuring evidence before requirement baseline writing. Use when requirement inputs are incomplete and teams need high-confidence evidence gathering; do not use for final canonical requirement synthesis.

planifest Bundle

Canonical requirement baseline workflow after evidence collection. Use when elicitation evidence is ready and must be synthesized into a traceable, testable requirement baseline; do not use for prioritization or implementation slicing.

planifest Bundle

Performance load testing workflow for realistic workload simulation, bottleneck detection, and saturation behavior analysis. Use when systems need throughput/latency validation before rollout; do not use for non-performance functional acceptance decisions.

planifest Bundle

Reconstruct change history using log/show/diff/blame evidence to explain when and why behavior changed. Use when teams need evidence-based history analysis for regressions or ownership questions; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Microservices architecture workflow for service boundary design, independent deployability, and distributed operational safety. Use when domain and team structure justify independent service evolution; do not use as a default scaling strategy for all systems.

planifest Bundle

Distributed-systems workflow for failure-mode analysis, consistency choices, and reliability primitive selection across networked components. Use when correctness depends on partitions, retries, timeouts, ordering, or partial failures; do not use for single-process implementation details only.

planifest Bundle

Requirement risk analysis workflow for failure scenarios, scoring, and mitigation before implementation commitment. Use when approved requirements need explicit risk assessment; do not use for initial requirement elicitation or sprint task breakdown.

planifest Bundle

FastAPI service development workflow for production-grade Python APIs. Use when FastAPI service behavior (path operations, dependency injection, request/response models, validation, async execution, OpenAPI exposure) must be implemented or revised; do not use for repository-wide architecture governance or release management policy.

planifest Bundle

Schema evolution governance workflow for safe migration sequencing, compatibility control, and rollback readiness across dependent systems. Use when shared schemas change and end-to-end compatibility governance is required; do not use for isolated query micro-optimizations.

planifest Bundle

Architecture Decision Record workflow for capturing technical decisions, alternatives, trade-offs, and revision triggers over time. Use when decisions materially affect system behavior, cost, or team workflow; do not use for trivial implementation choices.

planifest Bundle

Architecture trade-off analysis workflow for comparing options with explicit criteria, weighting, and sensitivity under uncertainty. Use when multiple viable architecture choices exist and rationale must be defensible; do not use after architecture direction is already fixed.

planifest Bundle

Clean Architecture workflow for enforcing dependency direction, stable domain boundaries, and use-case-centered application design. Use when teams must separate business rules from frameworks and delivery mechanisms; do not use for isolated module cleanup without boundary implications.

richfrem Bundle

Execute the implementation planning workflow using the plan template

allinherog-star Bundle

会议待办整理助手适合运营、产品、销售、software在用户提出“会议后该做什么”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成待办拆解、决策摘要、风险和跟进清单。

allinherog-star Bundle

销售增长助手适合销售、市场营销、运营、产品在用户提出“客户为什么不推进”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

allinherog-star Bundle

资料整理助手适合运营、产品、technical、销售在用户提出“这份材料重点是什么”这类问题，需要快速拆解目标、判断重点并形成可执行结果时使用，帮助基于输入材料生成摘要、诊断结论、行动建议和可复用交付物。

pooriaarab Skill

Use when the user wants to organize Google Calendar — pruning unused calendars, fixing color-coding, declining stale recurring events, archiving past events, aligning with the organizer taxonomy. Triggers: 'clean up my Google Calendar', 'too many calendars', 'fix calendar color chaos'.

pooriaarab Skill

Use when the user wants to organize, triage, or clean up Gmail, or reach inbox zero. Triggers: 'organize my gmail', 'inbox zero', 'unsubscribe from newsletters', 'clean up email', 'my inbox is a mess'.

pooriaarab Skill

Use when the user wants to organize Google Tasks — pruning completed items, consolidating task lists, surfacing stale recurring tasks, aligning with the organizer taxonomy. Triggers: 'organize Google Tasks', 'my Google Tasks is a mess'.

pooriaarab Skill

Turn a thin or messy issue-tracker ticket into a complete, implementation-ready spec an engineer can execute without a follow-up meeting — grounding every claim in real code, right-sizing the detail, and writing test cases. Triggers include "spec this", "flesh out <ticket>", "make this ready for an engineer".

samarv Skill

A strategic framework for identifying and launching new product lines by mapping the user's end-to-end journey. Use this when your core product is mature, when users are "hacking" your current tool for unintended use cases, or when you need to expand your TAM without bloating your primary interface.

samarv Skill

A framework for recovering from professional setbacks, "punches," or negative feedback. Use this when you feel defensive after a meeting, when a leader disagrees with your approach, or when you fear you've created a negative impression of your competence.

iamwaqargulzar Bundle

Design lifecycle email programs and sequences with segmentation, deliverability, personalization, testing and measurement.

iamwaqargulzar Bundle

Plan and execute organic social strategy, calendar, creative, community engagement, social selling and measurement.

iamwaqargulzar Bundle

Compatibility skill for paid ads. Use when a user or upstream workflow invokes this name; route the task to `ads` while preserving the requested scope and source-specific intent.

iamwaqargulzar Bundle

Write B2B cold outreach and follow-up sequences grounded in relevance, evidence, concise value, compliant sending practices and clear calls to action.

iamwaqargulzar Bundle

Compatibility skill for geo schema. Use when a user or upstream workflow invokes this name; route the task to `schema` while preserving the requested scope and source-specific intent.