Productivity

iamwaqargulzar Bundle

Use when the user asks to "plan how our narrative lands on every surface", "write per-surface message-match specs", or "brief each creative builder from the canon"; maps the narrative-registry canon onto every flagship surface (homepage, pricing, store listing, sales deck, social bio, docs, email) as a per-surface message-match spec — what claim, pillar, proof, and objection reframe each surface must carry — and cuts a handoff brief to each discipline's creative builder (content-writer, ad-creative-builder, email-creative-builder, social-creative-builder, message-house-builder), so the same story lands consistently everywhere. Not for writing the finished surface copy — use each discipline creative builder; not for the tier-scoped launch asset manifest — use launch-asset-packager; not for scoring cross-surface consistency — use narrative-quality-auditor; not for claim adjudication — use offer-claims-registry. 叙事落地/逐面消息一致/创意交接简报/画布传导

iamwaqargulzar Bundle

Use when the user asks to "build a preference center", "set up a frequency opt-down ladder", "give people a step-down instead of unsubscribe", or "design a topic/cadence preference page"; produces a preference-center field spec, a frequency/topic opt-down ladder (down-tier paths that substitute for a hard unsubscribe), a preference-to-suppression mapping, and a SEND N-dimension sub-item note on preference-center / frequency options offered. Not for the lifecycle flow map or cadence governance — use email-sequence-designer; not for the consent/suppression record itself — use consent-registry; not for computing EQS or ruling the N1 unsubscribe veto — use email-quality-auditor. 邮件偏好中心/降频阶梯设计/退订替代降档

joogy06 Bundle

Use when the user has an idea, feature, design, or change that needs exploration before implementation — architecture decisions, new features, system design, refactoring plans, or any creative/building task that benefits from structured design thinking before code.

joogy06 Skill

Use when assigned as implementation team manager or coordinator. Provides methodology for task decomposition, dependency management, specialist assignment, and team coordination.

joogy06 Skill

Use when the goal is getting your work or yourself in front of the people who decide — pre-wiring a decision before the meeting that formally makes it, getting a proposal, demo or deck through the door, building visibility in Microsoft Teams and internal channels under hybrid proximity bias, working a business or industry social event and following it up, using external platforms to reach people inside your target organisations, and asking for something in a form that is easy to say yes to. Includes where legitimate influence ends and manipulation begins.

ericrisco Bundle

Use when wiring server code to send transactional or bulk email via Resend, SendGrid, or Postmark: a provider-agnostic sendEmail() seam, idempotent retries, 100-cap batches with partial failures, transactional-vs-broadcast streams, bounce webhooks feeding a suppression list. NOT SPF/DKIM/DMARC inbox reputation (that is `email-deliverability`).

planifest Bundle

Pytest verification workflow for Python changes with deterministic fixtures, explicit case strategy, and CI-ready evidence. Use when Python modules need executable pytest evidence before merge; do not use for browser-level E2E or non-Python test tooling decisions.

planifest Bundle

Style, review, and refactoring standards for Zsh scripting. Trigger when `.zsh`, `.zshrc`, `.zprofile`, `.zshenv`, `.zlogin`, `.zlogout` files, files with `#!/usr/bin/env zsh` or `#!/bin/zsh`, or CI workflow blocks with `shell: zsh` are created, modified, or reviewed and Zsh-specific quality controls must be enforced. Do not use for POSIX `sh`, Bash-specific, or PowerShell-specific style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

planifest Bundle

Style, review, and refactoring standards for Bash shell scripting. Trigger when `.sh` files, files with `#!/usr/bin/env bash` or `#!/bin/bash`, or CI workflow blocks with `shell: bash` are created, modified, or reviewed and Bash-specific quality controls (quoting safety, error handling, portability, readability) must be enforced. Do not use for generic POSIX `sh`, PowerShell, or language-specific application style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.

planifest Bundle

Normalization workflow for reducing update anomalies while balancing query practicality and domain invariants. Use when schema redundancy and inconsistency risk need deliberate trade-off decisions; do not use for physical indexing-only tasks.

planifest Bundle

Graph algorithm workflow for modeling entities/relations and selecting traversal, path, ordering, or flow strategies. Use when correctness or performance depends on graph representation and algorithm choice; do not use for schema-only modeling or deployment topology planning.

planifest Bundle

Notebook delivery workflow for software teams requiring reproducible execution, clear narrative, and shareable evidence. Use when analysis, experiment, or verification results must be delivered as executable notebook artifacts; do not use for product requirement prioritization or architecture topology selection.

planifest Bundle

Mutation-testing workflow for exposing weak assertions and missing behavioral checks. Use when tests pass but confidence is low and objective robustness evidence is needed; do not use before baseline tests exist.

planifest Bundle

Index strategy workflow for balancing read latency, write amplification, and plan stability on critical query paths. Use when query performance depends on index design trade-offs; do not use for high-level conceptual modeling.

planifest Bundle

Logical database design workflow for table structure, key strategy, constraints, and relational consistency. Use when durable schema semantics must be defined before physical tuning; do not use for query-only optimization tasks.

planifest Bundle

Runbook authoring workflow for clear, executable operational procedures for on-call responders. Use when incident response, rollback, failover, or maintenance steps must be documented before production use; do not use for production feature logic design.

planifest Bundle

Database backup and recovery workflow for defining RPO/RTO-aligned retention, restore strategy, and disaster readiness. Use when data durability and recovery guarantees are in scope; do not use for query-only tuning tasks.

planifest Bundle

Physical database design workflow for storage layout, partitioning, engine settings, and hardware-aware performance behavior. Use when sustained workload efficiency depends on physical data organization; do not use for conceptual modeling tasks.

planifest Bundle

Enforce atomic commits, clear commit messages, and auditable change intent before push or review. Use when commit granularity, message clarity, and traceability must be improved; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Project estimation workflow for dependency-aware breakdowns and uncertainty-calibrated effort ranges. Use when initiatives need planning-grade estimates with explicit assumptions and confidence ranges; do not use for low-level implementation design details.

planifest Bundle

Release management workflow for go/no-go governance, readiness evidence, and rollback preparedness. Use when release decisions require explicit criteria and cross-team sign-off; do not use for application-domain algorithm or schema decisions.

planifest Bundle

Define branch topology, lifecycle rules, and merge policy that match team delivery and release risk. Use when branch protection, release/hotfix flow, and merge discipline must be explicit to prevent unsafe history changes; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Create immutable release tags and traceable release notes from Git history. Use when release cuts require consistent tag naming, immutability guarantees, and bounded changelog traceability; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Recover safely from problematic merges or commits using explicit revert strategy and validation. Use when a bad commit/merge has landed and rollback intent plus blast radius must be controlled; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Incident postmortem workflow for evidence-backed root cause analysis and systemic prevention actions. Use after incident stabilization when teams need timeline, root-cause chain, contributing factors, and owned prevention actions; do not use for active incident command and real-time mitigation.

planifest Bundle

Locate regression-introducing commits using git bisect with deterministic classification. Use when a reproducible regression exists but the introducing commit is unknown; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Keep pull request branches synchronized with target branch updates using a safe, policy-aligned strategy. Use when a PR branch diverges from base and merge-vs-rebase plus conflict handling must be chosen safely; do not use for CI workflow design or application behavior implementation.

planifest Bundle

Modular monolith architecture workflow for strong domain boundaries, transactional consistency, and operational simplicity in a single deployable. Use when teams need fast delivery and coherent data consistency with controlled complexity; do not use when independent runtime scaling boundaries are mandatory.

planifest Bundle

Schema migration strategy workflow for sequencing changes, compatibility windows, and rollback-safe rollout in live systems. Use when schema evolution impacts running services; do not use for static greenfield schemas without deployment constraints.

planifest Bundle

Query optimization workflow for reducing latency and resource cost through plan-aware rewrites and access-path improvements. Use when hot-path query behavior is the bottleneck; do not use for conceptual schema redesign without workload evidence.

planifest Bundle

Transaction design workflow for boundary definition, isolation-level choice, and contention control under real workload behavior. Use when correctness depends on concurrent read/write semantics; do not use for schema-only tasks that do not affect transaction behavior.

planifest Bundle

Consensus workflow for quorum, leader election, commit semantics, and membership change safety. Use when replicated-state correctness requires coordinated agreement across nodes under faults; do not use for non-replicated single-node workflows.

planifest Bundle

Feature flag lifecycle governance workflow for safe rollout, blast-radius control, and cleanup discipline. Use when feature rollout needs runtime controls (targeting, staged exposure, kill-switch policy, ownership, and retirement lifecycle) and those rules are not yet explicit; do not use for statistical experiment design and analysis.

planifest Bundle

Jest verification workflow for JavaScript/TypeScript codebases with deterministic tests, explicit mock boundaries, and actionable CI evidence. Use when JS/TS changes need executable Jest evidence before merge; do not use for browser-level E2E or language-agnostic policy design.

planifest Bundle

Observability logging workflow for structured schema, correlation, and incident triage utility. Use when services need logging standards or revisions for diagnosable incidents; do not use for business-feature implementation logic.

planifest Bundle

Observability tracing workflow for distributed trace coverage and critical-path diagnosis. Use when cross-service request paths need instrumentation or analysis to localize latency/error bottlenecks; do not use for business-feature implementation logic.