planifest
- 233 skills
- 0 followers
- 14 hours ago last updated
- ▌ Co Marketing · planifest bundleWhen the user wants to find co-marketing partners, plan joint campaigns, or brainstorm partnership opportunities. Use when the user says 'co-marketing,' 'partner marketing,' 'joint campaign,' 'who should we partner with,' 'integration marketing,' 'cross-promotion,' 'collaborate with another company,' 'partnership ideas,' or 'co-brand.' For customer referral programs, see referral-program. For launch-specific partnerships, see launch-strategy.
- ▌ Interview Coach · planifest bundleFull job search coaching system — JD decoding, resume, storybank, mock interviews, transcript analysis, comp negotiation. 23 commands, persistent state.
- ▌ Cqrs Implementation · planifest bundleImplement Command Query Responsibility Segregation for scalable architectures. Use when separating read and write models, optimizing query performance, or building event-sourced systems.
- ▌ Linux Troubleshooting · planifest bundleLinux system troubleshooting workflow for diagnosing and resolving system issues, performance problems, and service failures.
- ▌ Memory Safety Patterns · planifest bundleCross-language patterns for memory-safe programming including RAII, ownership, smart pointers, and resource management.
- ▌ Microservices Patterns · planifest bundleMaster microservices architecture patterns including service boundaries, inter-service communication, data management, and resilience patterns for building distributed systems.
- ▌ Cloudflare Workers Expert · planifest bundleExpert in Cloudflare Workers and the Edge Computing ecosystem. Covers Wrangler, KV, D1, Durable Objects, and R2 storage.
- ▌ Dbt Transformation Patterns · planifest bundleProduction-ready patterns for dbt (data build tool) including model organization, testing strategies, documentation, and incremental processing.
- ▌ Planifest Ship Agent 2 · planifest bundlePhase 7 only — raises the PR, writes the changelog, handles skips, and archives plan/current/. Invoked by the orchestrator at the end of the feature pipeline.
- ▌ Accessibility Compliance Accessibility Audit · planifest bundleYou are an accessibility expert specializing in WCAG compliance, inclusive design, and assistive technology compatibility. Conduct audits, identify barriers, and provide remediation guidance.
- ▌ Cso · planifest bundleChief Security Officer mode. Infrastructure-first security audit: secrets archaeology, dependency supply chain, CI/CD pipeline security, LLM/AI security, skill supply chain scanning, plus OWASP Top 10, STRIDE threat modeling, and active verification. Two modes: daily (zero-noise, 8/10 confidence gate) and comprehensive (monthly deep scan, 2/10 bar). Trend tracking across audit runs. Use when: "security audit", "threat model", "pentest review", "OWASP", "CSO review". (gstack) Voice triggers (speech-to-text aliases): "see-so", "see so", "security review", "security check", "vulnerability scan", "run security".
- ▌ Soul · planifest bundleEmbody this digital identity. Read SOUL.md first, then STYLE.md, then examples/. Become the person—opinions, voice, worldview.
- ▌ Codex · planifest bundleOpenAI Codex CLI wrapper — three modes. Code review: independent diff review via codex review with pass/fail gate. Challenge: adversarial mode that tries to break your code. Consult: ask codex anything with session continuity for follow-ups. The "200 IQ autistic developer" second opinion. Use when asked to "codex review", "codex challenge", "ask codex", "second opinion", or "consult codex". (gstack) Voice triggers (speech-to-text aliases): "code x", "code ex", "get another opinion".
- ▌ Retro · planifest bundleWeekly engineering retrospective. Analyzes commit history, work patterns, and code quality metrics with persistent history and trend tracking. Team-aware: breaks down per-person contributions with praise and growth areas. Use when asked to "weekly retro", "what did we ship", or "engineering retrospective". Proactively suggest at the end of a work week or sprint. (gstack)
- ▌ Browse · planifest bundleFast headless browser for QA testing and site dogfooding. Navigate any URL, interact with elements, verify page state, diff before/after actions, take annotated screenshots, check responsive layouts, test forms and uploads, handle dialogs, and assert element states. ~100ms per command. Use when you need to test a feature, verify a deployment, dogfood a user flow, or file a bug with evidence. Use when asked to "open in browser", "test the site", "take a screenshot", or "dogfood this". (gstack)
- ▌ Canary · planifest bundlePost-deploy canary monitoring. Watches the live app for console errors, performance regressions, and page failures using the browse daemon. Takes periodic screenshots, compares against pre-deploy baselines, and alerts on anomalies. Use when: "monitor deploy", "canary", "post-deploy check", "watch production", "verify deploy". (gstack)
- ▌ Health · planifest bundleCode quality dashboard. Wraps existing project tools (type checker, linter, test runner, dead code detector, shell linter), computes a weighted composite 0-10 score, and tracks trends over time. Use when: "health check", "code quality", "how healthy is the codebase", "run all checks", "quality score". (gstack)
- ▌ Nelson · planifest bundleOrchestrates multi-agent task execution using a Royal Navy squadron metaphor — from mission planning through parallel work coordination to stand-down. Use when work needs parallel agent orchestration, tight task coordination with quality gates, structured delegation with progress checkpoints, or a documented decision log.
- ▌ Review · planifest bundlePre-landing PR review. Analyzes diff against the base branch for SQL safety, LLM trust boundary violations, conditional side effects, and other structural issues. Use when asked to "review this PR", "code review", "pre-landing review", or "check my diff". Proactively suggest when the user is about to merge or land code changes. (gstack)
- ▌ QA Only · planifest bundleReport-only QA testing. Systematically tests a web application and produces a structured report with health score, screenshots, and repro steps — but never fixes anything. Use when asked to "just report bugs", "qa report only", or "test but don't fix". For the full test-fix-verify loop, use /qa instead. Proactively suggest when the user wants a bug report without any code changes. (gstack) Voice triggers (speech-to-text aliases): "bug report", "just check for bugs".
- ▌ Autoplan · planifest bundleAuto-review pipeline — reads the full CEO, design, eng, and DX review skills from disk and runs them sequentially with auto-decisions using 6 decision principles. Surfaces taste decisions (close approaches, borderline scope, codex disagreements) at a final approval gate. One command, fully reviewed plan out. Use when asked to "auto review", "autoplan", "run all reviews", "review this plan automatically", or "make the decisions for me". Proactively suggest when the user has a plan file and wants to run the full review gauntlet without answering 15-30 intermediate questions. (gstack) Voice triggers (speech-to-text aliases): "auto plan", "automatic review".
- ▌ Benchmark · planifest bundlePerformance regression detection using the browse daemon. Establishes baselines for page load times, Core Web Vitals, and resource sizes. Compares before/after on every PR. Tracks performance trends over time. Use when: "performance", "benchmark", "page speed", "lighthouse", "web vitals", "bundle size", "load time". (gstack) Voice triggers (speech-to-text aliases): "speed test", "check performance".
- ▌ Planifest Migrator · planifestExecutes a pending Planifest framework migration interactively. Reads a migration file, presents findings to the human, applies confirmed changes, and archives the migration on completion. Invoked by the orchestrator when pending migrations are detected.
- ▌
- ▌ Ab Testing · planifest bundleControlled online experiment workflow for product changes with causal inference, randomization integrity checks, and pre-registered decision criteria. Trigger when ship/no-ship decisions require causal evidence under uncertainty and KPI trade-offs must be quantified. Do not use for feature-flag rollout policy without experiment design, deterministic functional verification, or observability-only analysis.
- ▌ API Design · planifest bundleGenerate secure, composable code changes for an existing project from structured JSON input — use with `code2context` to apply AI-suggested file creates and updates from natural language instructions.
- ▌ Playwright · planifest bundlePlaywright browser verification workflow for user-journey evidence with deterministic replay artifacts. Use when web flows require executable browser evidence (trace/screenshot/replay logs) before merge or release; do not use for pure unit/API-only checks.
- ▌ Screenshot · planifest bundleVisual evidence capture workflow for reproducible screenshots in engineering and QA tasks. Use when bug reports, regression checks, or implementation proof require stable screenshot artifacts; do not use for design-source extraction or architecture documentation.
- ▌ Planifest Adr Agent · planifest bundleProduces Architecture Decision Records for each significant decision in the requirements. Invoked by the orchestrator during Phase 2.
- ▌ B2b Saas Pm · planifest bundleGenerate a structured Product Requirements Document (PRD) from a product idea or description — covering overview, objectives, target audience, features, user stories, functional/non-functional requirements, success metrics, and timeline.
- ▌ Consumer Pm · planifest bundleAnalyse and prioritise product feedback by consolidating similar themes, scoring usefulness, and presenting a ranked Markdown table — use when processing user research, app reviews, or support ticket data.
- ▌ Investigate · planifest bundleSystematic debugging with root cause investigation. Four phases: investigate, analyze, hypothesize, implement. Iron Law: no fixes without root cause. Use when asked to "debug this", "fix this bug", "why is this broken", "investigate this error", or "root cause analysis". Proactively invoke this skill (do NOT debug directly) when the user reports errors, 500 errors, stack traces, unexpected behavior, "it was working yesterday", or is troubleshooting why something stopped working. (gstack)
- ▌ Okr Writing · planifest bundleWrite effective Objectives and Key Results that align teams, communicate priorities, and drive measurable outcomes — not vanity metrics or activity tracking
- ▌ Platform Pm · planifest bundlePlatform product management — developer ecosystems, APIs as product, extensibility design, and platform governance; use when building infrastructure that other teams or companies build on top of.
- ▌ Sre Sli Slo · planifest bundleSRE SLI/SLO workflow for reliability target definition, measurable telemetry mapping, and error-budget policy. Use when service reliability objectives must be formalized with escalation actions; do not use for business-feature implementation logic.
- ▌ Testing Bdd · planifest bundleBehavior-driven scenario design for shared business language and executable acceptance evidence. Use when teams must align on Given-When-Then scenarios before implementation sign-off or release; do not use for performance benchmarking or deployment policy design.
- ▌ Testing E2e · planifest bundleEnd-to-end test planning for critical user journeys across integrated systems. Use when release confidence depends on browser/API/dependency behavior as one flow; do not use for isolated unit behavior or pure contract checks.
- ▌ Testing Tdd · planifest bundleRed-green-refactor workflow for test-first implementation feedback loops. Use when behavior and design must evolve safely through small increments backed by failing-then-passing tests; do not use for post-hoc test backfilling only.
- ▌ Planifest Docs Agent · planifest bundleProduces complete per-component documentation, system-wide registry, dependency graph, and iteration log audit trail. Invoked during the Documentation step.
- ▌
- ▌ Planifest Spec Agent · planifest bundleProduces requirements artifacts (execution plan, OpenAPI spec (if applicable), scope, risk register, domain glossary) for a feature. Invoked by the orchestrator during the Requirements step.
- ▌ API Security · planifest bundleGenerate a STRIDE-per-element threat model for a system design — identifying assets, trust boundaries, data flows, and a prioritised threat table with mitigations. Use when threat-modelling any system or API design.
- ▌ Code Quality · planifest bundleExplain code, security tool output, or configuration text — outputs clear EXPLANATION, SECURITY IMPLICATIONS, CONFIGURATION EXPLANATION, or ANSWER sections depending on input type. Use when you need a plain-language breakdown of what code or config does.
- ▌ Okr Planning · planifest bundleWriting and running OKRs — objective quality, key result measurability, grading, and check-in cadence; use when setting or reviewing quarterly goals.
- ▌ Team Scaling · planifest bundleDesign team structures, hiring plans, and organizational processes that scale engineering capability without degrading coordination, quality, or culture
- ▌ Testing Unit · planifest bundleDeterministic unit-test strategy for isolated logic and fast feedback. Use when core logic branches, error paths, and edge conditions need low-latency regression evidence with controlled dependencies; do not use for browser-flow or cross-service compatibility validation.
- ▌
- ▌
- ▌
- ▌ Build Systems · planifest bundleSummarise git changes from the last 7 days into a clean, excited project update — covering key feature changes and upgrades as concise 10-word bullets with a 20-word intro.
- ▌ Code Reviewer · planifest bundlePerform a comprehensive code review of a snippet or diff — assessing correctness, security, performance, readability, and edge cases, with prioritised recommendations and suggested improvements. Use when reviewing PRs or auditing code quality.
- ▌ Design Review · planifest bundleRun structured design reviews that produce actionable findings and clear approval decisions. Use when a design artifact needs formal review for usability, accessibility, consistency, and implementation readiness before handoff or approval; do not use for backend data-model or deployment pipeline decisions.
- ▌ Design Tokens · planifest bundleDesign token architecture workflow for semantic, scalable, implementation-ready token systems. Use when multiple screens or products need consistent color/type/spacing/motion decisions and token definitions before component implementation; do not use for backend data-model or deployment pipeline decisions.
- ▌ Docker Basics · planifest bundleDesign and review container runtime basics for reproducible local/service execution using Docker. Use when container build/run behavior, networking, volumes, and runtime isolation need explicit decisions; do not use for API contract or requirement prioritization tasks.
- ▌ Figma Handoff · planifest bundleDesign-to-engineering handoff workflow for packaging implementation-ready Figma specifications, assets, and acceptance criteria. Trigger when approved Figma designs must be translated into engineering-ready handoff materials (specs, assets, states, acceptance criteria) before implementation starts; do not use for backend data-model or deployment pipeline decisions.
- ▌ Github Fix CI · planifest bundleRespond to GitHub Actions failures with evidence-based triage, root-cause isolation, and minimal-risk fixes. Use when GitHub-hosted checks fail and teams need a repair plan tied to failed jobs; do not use for non-GitHub runtime architecture or data-layer design.
- ▌
- ▌
- ▌ API Versioning · planifest bundleAPI version lifecycle governance for breaking-change classification, deprecation windows, migration planning, and support matrix management across internal and external consumers. Trigger when contract diffs may break consumers (for example required-field removal, semantic change, or channel change), when deprecation/sunset planning is required, or when multiple consumer cohorts must be supported in parallel. Do not use for first-pass endpoint/schema design.
- ▌ C4 Diagramming · planifest bundleTurn any concept, system, or data into a Mermaid diagram with a VISUAL EXPLANATION section — use when you need to visualise architecture, flows, relationships, or any complex idea as a renderable diagram.
- ▌ Cloud Security · planifest bundleProduce a network threat landscape report from open port and service scan data — covering description, risk assessment, recommendations, trends, and one-sentence summary for inclusion in formal security reports.
- ▌ Content Design · planifest bundleRewrite and improve an LLM prompt using proven prompt engineering techniques — covering clarity, persona, delimiters, chain-of-thought, examples, and output format specification.
- ▌ Design Shotgun · planifest bundleDesign shotgun: generate multiple AI design variants, open a comparison board, collect structured feedback, and iterate. Standalone design exploration you can run anytime. Use when: "explore designs", "show me options", "design variants", "visual brainstorm", or "I don't like how this looks". Proactively suggest when the user describes a UI feature but hasn't seen what it could look like. (gstack)
- ▌ Go Style Guide · planifest bundleStyle, review, and refactoring standards for Go codebases. Trigger when `.go`, `go.mod`, `go.sum`, or `go.work` files are created, changed, or reviewed and Go-specific quality rules (error handling, concurrency patterns, interface design, package boundaries) must be enforced. Do not use for generic shell scripts, SQL-only changes, or non-Go runtime style concerns unless Go artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
- ▌ Marketplace Pm · planifest bundleMarketplace product management — liquidity, supply/demand balance, take rate, and network effects; use when building two-sided or multi-sided platforms.
- ▌ Sh Style Guide · planifest bundleStyle, review, and refactoring standards for POSIX `sh` scripting. Trigger when `.sh` files, files with `#!/usr/bin/env sh` or `#!/bin/sh`, or CI workflow blocks with `shell: sh` are created, modified, or reviewed and portability/safety controls for POSIX shell must be enforced. Do not use for Bash-specific, Zsh-specific, or PowerShell-specific style rules. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
- ▌ Planifest Codegen Agent · planifest bundleGenerates the full implementation from the requirements set - application code, tests, infrastructure, configuration. Invoked during Phase 3.
- ▌ Planifest Design Critic · planifestFresh-context REJECT-default critique of P1 spec and P2 ADR artifacts before the human sees them. Spawned by the orchestrator as a subagent; report-only until promoted.
- ▌ Planifest Refresh Setup · planifestRefreshes a Planifest install by detecting the target tool, reconstructing the setup flags currently in effect from installed hook wiring and the flags-used marker file, confirming with the human on the loop, and re-invoking setup.sh/setup.ps1 with those flags. Invoke on request ("refresh the framework setup", "re-run setup with current settings", "refresh setup for {tool}").
- ▌ API Design REST · planifest bundleResource-oriented REST/OpenAPI contract design for URI/method semantics, idempotency, pagination, and HTTP status behavior. Trigger when REST contract diffs are detected in paths, methods, schemas, or status semantics, or when request-response transport choice is still unresolved before implementation. Do not use for GraphQL schema authoring, error-taxonomy-only changes, version lifecycle governance, or consumer-provider contract test implementation.
- ▌ Cloud Architect · planifest bundleAnalyse a Terraform plan and produce a structured Markdown summary — one-sentence overview, top 10 critical changes or concerns, and 5 key takeaways covering security, cost, and compliance.
- ▌ Data Structures · planifest bundleSelect data structures using explicit access patterns, mutation behavior, memory limits, and concurrency constraints. Use when implementation correctness or performance depends on choosing between alternatives (array/map/heap/tree/queue/set) under real workload assumptions; do not use for persistence schema or deployment topology decisions.
- ▌ Design Critique · planifest bundleConduct a detailed architecture design review — evaluating component clarity, integrations, security, scalability, data management, maintainability, and risks. Use when reviewing a system design document or architecture diagram.
- ▌ Land And Deploy · planifest bundleLand and deploy workflow. Merges the PR, waits for CI and deploy, verifies production health via canary checks. Takes over after /ship creates the PR. Use when: "merge", "land", "deploy", "merge and verify", "land it", "ship it to production". (gstack)
- ▌ Localization QA · planifest bundleLocalization QA workflow for language correctness, layout resilience, and locale-specific behavior validation before release. Use when localized UI/content must be verified across target locales; do not use for backend data-model or deployment pipeline decisions.
- ▌ Plan Eng Review · planifest bundleEng manager-mode plan review. Lock in the execution plan — architecture, data flow, diagrams, edge cases, test coverage, performance. Walks through issues interactively with opinionated recommendations. Use when asked to "review the architecture", "engineering review", or "lock in the plan". Proactively suggest when the user has a plan or design doc and is about to start coding — to catch architecture issues before implementation. (gstack) Voice triggers (speech-to-text aliases): "tech review", "technical review", "plan engineering review".
- ▌ Pytest Workflow · planifest bundlePytest 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.
- ▌ SQL Style Guide · planifest bundleStyle, review, and refactoring standards for SQL schema, migration, and query artifacts. Trigger when `.sql` schema/query/migration artifacts are created, changed, or reviewed and SQL-specific quality rules (naming, migration safety, query clarity, and performance intent) must be enforced. Do not use for ORM-only code changes with no SQL artifacts, or for non-SQL data modeling documents. Use together with language-specific style guides only when both SQL and application code are modified.
- ▌ Zsh Style Guide · planifest bundleStyle, 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 Optimise Agent · planifestReviews planifest-framework/skills/ for superfluous content and presents one suggestion at a time for human confirmation. Never modifies files.
- ▌ Planifest Security Agent · planifest bundlePerforms a security review of the implementation, producing a security report with specific findings. Invoked during Phase 5.
- ▌ Planifest Validate Agent · planifest bundleRuns CI checks (lint, typecheck, test, build) and self-corrects up to 5 times. Invoked during Phase 4.
- ▌ Algorithm Design · planifest bundleDesign algorithms by modeling constraints, enumerating candidate strategies, proving correctness, and selecting data structures with explicit tradeoffs. Use when implementation success depends on algorithm choice or decomposition under unclear constraints, from vague outcome requests to concrete directives; do not use for persistence schema or deployment topology decisions.
- ▌ Algorithm Expert · planifest bundleGenerate a glossary of advanced terms from any technical content — each entry includes a 2-sentence definition, an analogy, and a "why it matters" explanation.
- ▌ Architecture Ddd · planifest bundleDomain-driven design workflow for bounded context partitioning, aggregate design, and context mapping in complex domains. Use when domain complexity or organizational scaling requires explicit model boundaries; do not use for small CRUD domains without competing language models.
- ▌ Bash Style Guide · planifest bundleStyle, 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.
- ▌ Benchmark Models · planifest bundleCross-model benchmark for gstack skills. Runs the same prompt through Claude, GPT (via Codex CLI), and Gemini side-by-side — compares latency, tokens, cost, and optionally quality via LLM judge. Answers "which model is actually best for this skill?" with data instead of vibes. Separate from /benchmark, which measures web page performance. Use when: "benchmark models", "compare models", "which model is best for X", "cross-model comparison", "model shootout". (gstack) Voice triggers (speech-to-text aliases): "compare models", "model shootout", "which model is best".
- ▌ DB Normalization · planifest bundleNormalization 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.
- ▌ Debug Root Cause · planifest bundleSystematic debugging workflow for isolating software root causes, implementing proportional fixes, and verifying recovery with reproducible evidence. Use when application/runtime failures, regressions, or flaky behavior are observed and the task requires both diagnosis and remediation. When specialized skills are available in the environment, defer GitHub Actions failure triage to `github-fix-ci`, commit-introduction isolation to `git-bisect-debugging`, profiler-led hotspot analysis to `performance-profiling`, active security incident command to `security-incident-response`, and postmortem-only reporting to `incident-postmortem`. Do not use for broad feature implementation or speculative hardening without evidence.
- ▌ Document Release · planifest bundlePost-ship documentation update. Reads all project docs, cross-references the diff, updates README/ARCHITECTURE/CONTRIBUTING/CLAUDE.md to match what shipped, polishes CHANGELOG voice, cleans up TODOS, and optionally bumps VERSION. Use when asked to "update the docs", "sync documentation", or "post-ship docs". Proactively suggest after a PR is merged or code is shipped. (gstack)
- ▌ Graph Algorithms · planifest bundleGraph 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.
- ▌ Java Style Guide · planifest bundleStyle, review, and refactoring standards for Java codebases with strong typing, explicit failure handling, and maintainable architecture boundaries. Use when `.java`, `pom.xml`, `build.gradle`, or `build.gradle.kts` artifacts are created, changed, or reviewed and Java-specific quality rules must be enforced. Do not use for Kotlin-only, Android-Gradle-only, or non-JVM language style concerns unless Java artifacts are also changed.
- ▌ Jupyter Notebook · planifest bundleNotebook 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.
- ▌ Rust Style Guide · planifest bundleStyle, review, and refactoring standards for Rust codebases. Trigger when `.rs`, `Cargo.toml`, or `Cargo.lock` files are created, changed, or reviewed and Rust-specific quality rules (ownership/borrowing clarity, error handling, trait/API design, crate boundaries) must be enforced. Do not use for C/C++ toolchain conventions, shell-only changes, or non-Rust runtime style concerns unless Rust artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
- ▌ Testing Contract · planifest bundleProvider-consumer compatibility testing for service interface changes. Use when APIs or event schemas evolve and executable contract checks must guard compatibility before release; do not use for UI-only validation or architecture topology decisions.
- ▌ Testing Mutation · planifest bundleMutation-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.
- ▌ Capacity Planning · planifest bundleAnalyse server log files to identify patterns, anomalies, and reliability issues — covering error spikes, recurring failures, performance degradation, and actionable improvement recommendations.
- ▌ Chaos Engineering · planifest bundleExtract structured incident intelligence from cybersecurity breach articles — covering attack type, attacker, target, CVEs, business impact, MITRE ATT&CK mapping, and remediation action plan.
- ▌ DB Index Strategy · planifest bundleIndex 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.
- ▌ DB Logical Design · planifest bundleLogical 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.