planifest
- 255 skills
- 0 followers
- last week last updated
- ▌ 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.
- ▌ Design Principles · planifest bundleDefine and align product design principles that teams can apply consistently across UX decisions. Use when product or UX direction is ambiguous and teams need explicit decision guardrails before detailed screens or components are produced; do not use for backend data-model or deployment pipeline decisions.
- ▌ Documentation Rfc · planifest bundleAuthor RFC documents for proposed technical changes with clear problem framing, options, tradeoffs, and decision path. Use when proposal alignment and review sign-off are needed before implementation; do not use for post-decision implementation-only docs.
- ▌ Kubernetes Basics · planifest bundleKubernetes fundamentals workflow for workload deployment, service discovery, and baseline cluster primitives. Use when teams need concrete namespace/workload/service/probe decisions before deployment; do not use for API contract design or requirement prioritization.
- ▌ Nextjs App Router · planifest bundleNext.js App Router implementation workflow for route structure, server/client boundaries, and caching/revalidation behavior. Use when App Router architecture or data/rendering behavior must be implemented or changed; do not use for repository-wide architecture governance or release management policy.
- ▌ Plan Devex Review · planifest bundleInteractive developer experience plan review. Explores developer personas, benchmarks against competitors, designs magical moments, and traces friction points before scoring. Three modes: DX EXPANSION (competitive advantage), DX POLISH (bulletproof every touchpoint), DX TRIAGE (critical gaps only). Use when asked to "DX review", "developer experience audit", "devex review", or "API design review". Proactively suggest when the user has a plan for developer-facing products (APIs, CLIs, SDKs, libraries, platforms, docs). (gstack) Voice triggers (speech-to-text aliases): "dx review", "developer experience review", "devex review", "devex audit", "API design review", "onboarding review".
- ▌ Privacy By Design · planifest bundlePrivacy-by-design workflow for embedding data minimization, lawful basis, retention, and user-rights readiness into product decisions. Use when a feature touches personal data and privacy controls must be defined before implementation; do not use for narrow infrastructure tuning that does not affect personal-data handling.
- ▌ Runbook Authoring · planifest bundleRunbook 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.
- ▌ Typescript Expert · planifest bundleTypeScript and JavaScript expert with deep knowledge of type-level programming, performance optimization, monorepo management, migration strategies, and modern tooling.
- ▌ Use Case Modeling · planifest bundleUse case modeling workflow for clarifying actor interactions, boundary behavior, and exception handling of approved requirements. Use when requirement behavior remains ambiguous and teams need explicit main/alternate/exception flows; do not use for backlog prioritization.
- ▌
- ▌ API Design GRAPHQL · planifest bundleGraphQL schema and resolver contract design for type boundaries, nullability, authz, and query-cost safety. Trigger when SDL, resolver behavior, field contracts, or query safety controls are added/changed, and their contract impact is not yet explicitly specified. Do not use for REST/OpenAPI endpoint design, API version lifecycle governance, or standalone error taxonomy design.
- ▌ API Error Handling · planifest bundleAPI failure-contract design for status mapping, stable error codes, retryability semantics, and traceable error payloads across sync and async transports. Trigger when error behavior, retry semantics, or debuggability fields change in specs or source, or when those rules remain implicit. Do not use for full resource/schema modeling or version-channel policy definition.
- ▌ Csharp Style Guide · planifest bundleStyle, review, and refactoring standards for C#/.NET codebases. Trigger when `.cs`, `.csproj`, `.sln`, `.props`, `.targets`, or `.razor` artifacts are created, modified, or reviewed and C#-specific quality rules (naming, nullability, async patterns, API design consistency) must be enforced. Do not use for Java/Kotlin or JavaScript/TypeScript style concerns unless C# artifacts are also changed. In multi-language pull requests, run together with other applicable `*-style-guide` skills.
- ▌ DB Backup Recovery · planifest bundleDatabase 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.
- ▌ DB Physical Design · planifest bundlePhysical 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.
- ▌ Git Commit Hygiene · planifest bundleEnforce 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.
- ▌ Interaction Design · planifest bundleInteraction design workflow for user flows, state transitions, and feedback behavior across key tasks. Use when user journeys require explicit interaction rules (state changes, validation feedback, error recovery, empty/loading behavior) before UI implementation; do not use for backend data-model or deployment pipeline decisions.
- ▌ Ml Model Selection · planifest bundleML model selection workflow for transparent trade-offs across accuracy, latency, cost, and operability. Use when choosing among multiple model candidates for production use; do not use for generic API-layer or infrastructure-only changes.
- ▌ Ml Problem Framing · planifest bundleML problem framing workflow for objective definition, target variable design, and success criteria. Use when translating business problems into ML tasks and objective/label/metric definitions are still ambiguous; do not use for generic API-layer or infrastructure-only changes.
- ▌ Project Estimation · planifest bundleProject 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.
- ▌ Python Style Guide · planifest bundleStyle, review, and refactoring standards for Python codebases with strong typing, explicit error handling, and maintainable module boundaries. Use when Python artifacts are created, changed, or reviewed and Python-specific quality rules must be enforced.
- ▌ Release Management · planifest bundleRelease 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.
- ▌ User Story Writing · planifest bundleUser story authoring workflow for turning prioritized requirements into implementable, testable delivery slices. Use when approved requirement work must be decomposed for sprint execution; do not use for initial requirement discovery or release-level prioritization.
- ▌ Planifest Reversal Assessor · planifestFresh-context REJECT-default judgement of design-defect reports. Decides whether a P3–P6 blockage justifies a governed reversal of an upstream artifact. Spawned by the orchestrator; never the agent that filed the report.
- ▌ Android Development · planifest bundleCreate production-quality Android applications following Google's official architecture guidance and NowInAndroid best practices. Use when building Android apps with Kotlin, Jetpack Compose, MVVM architecture, Hilt dependency injection, Room database, or multi-module projects. Triggers on requests to create Android projects, screens, ViewModels, repositories, feature modules, or when asked about Android architecture patterns.
- ▌ Code Review General · planifest bundleRun full-scope code review for correctness, maintainability, and regression risk when no single specialty dominates. Use for broad merge-readiness reviews with explicit findings and evidence; if security or performance risk is primary, prioritize `code-review-security` or `code-review-performance` first.
- ▌ Design Consultation · planifest bundleDesign consultation: understands your product, researches the landscape, proposes a complete design system (aesthetic, typography, color, layout, spacing, motion), and generates font+color preview pages. Creates DESIGN.md as your project's design source of truth. For existing sites, use /plan-design-review to infer the system instead. Use when asked to "design system", "brand guidelines", or "create DESIGN.md". Proactively suggest when starting a new project's UI with no existing design system or DESIGN.md. (gstack)
- ▌ Dynamic Programming · planifest bundleDesign dynamic programming solutions by defining state, transitions, base cases, and optimization strategy (memoization/tabulation). Use when optimal substructure and overlapping subproblems make brute-force or greedy approaches insufficient; do not use for persistence schema or deployment topology decisions.
- ▌ Git Branch Strategy · planifest bundleDefine 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.
- ▌ Git Rebase Workflow · planifest bundleLinearize local branch history with safe rebase practices before integration. Use when branch history cleanup is needed and rebase risks (conflicts, dropped commits, rewritten history impact) must be controlled; do not use for CI workflow design or application behavior implementation.
- ▌ Git Release Tagging · planifest bundleCreate 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.
- ▌ Git Revert Recovery · planifest bundleRecover 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.
- ▌ Incident Postmortem · planifest bundleIncident 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.
- ▌ Kubernetes Security · planifest bundleKubernetes security workflow for cluster hardening, workload isolation, and policy enforcement. Use when RBAC, network policy, pod security, secret handling, or admission controls must be defined before production exposure; do not use for API contract design or requirement prioritization.
- ▌ Ml Model Evaluation · planifest bundleML model evaluation workflow for metric design, threshold setting, and failure segmentation. Use when model readiness decisions require explicit accept/reject criteria and segment-level evidence; do not use for generic API-layer or infrastructure-only changes.
- ▌ Mlops Model Serving · planifest bundleMLOps model serving workflow for serving topology, latency SLOs, and safe rollout controls. Use when deploying ML models to production serving paths with explicit reliability and rollback requirements; do not use for model-architecture research decisions.
- ▌ Testing Integration · planifest bundleIntegration-boundary testing for component and service collaboration correctness. Use when modules interact via APIs, queues, databases, or adapters and boundary behavior must be verified; do not use for full UI journey validation or pure unit isolation work.
- ▌ Web Design Engineer · planifest bundleBuild high-quality visual Web artifacts using HTML/CSS/JavaScript/React — web pages, landing pages, dashboards, interactive prototypes, HTML slide decks, animated demos, UI mockups, data visualizations, and more. Use this skill whenever the user's request involves a visual, interactive, or front-end deliverable, including: - Creating web pages, landing pages, dashboards, marketing pages - Building interactive prototypes or UI mockups (with device frames) - Building HTML slide decks / presentations - Creating CSS/JS animations or timeline-driven animated demos - Turning design mockups, screenshots, or PRDs into interactive implementations - Data visualization (Chart.js / D3, etc.) - Design system / UI Kit exploration Even if the user doesn't explicitly say "HTML" or "web page," this skill applies whenever the intent is to produce something visual, interactive, or presentational. Not applicable: pure back-end logic, CLI tools, data-processing scripts, non-visual code tasks, command-line debugging.
- ▌ Accessibility Design · planifest bundleAccessibility-first design workflow for specifying semantics, keyboard/focus behavior, readability, and assistive-technology expectations. Use when UI accessibility behavior must be defined before implementation or design sign-off; do not use for backend data modeling or deployment pipeline decisions.
- ▌ API Contract Testing · planifest bundleConsumer-provider contract testing and release-gate design for compatibility matrices, contract assertions, and CI blocking rules across versions and transports. Trigger when API contract diffs are detected but compatibility evidence is missing or stale (contract test pass, consumer-impact mapping, or compatibility matrix update), or when multiple consumers, versions, or transports must be protected by automated gates. Do not use for first-pass API interface design.
- ▌ Code Review Security · planifest bundleRun security-focused code review when changes cross trust boundaries or may affect authentication, authorization, input validation, secrets handling, or sensitive-data exposure. Use for merge decisions requiring explicit security findings; do not use for non-security-only review scope.
- ▌ Competitive Analysis · planifest bundleAnalyse the societal impact of a technology project — summarising objectives, technologies, outcomes, ethical considerations, sustainability, and an overall rating. Use when evaluating a technology initiative's broader implications.
- ▌ Concurrency Patterns · planifest bundleDesign and review concurrency strategy for shared state, coordination, and contention control. Use when parallel execution or async coordination introduces race/deadlock/liveness risk and explicit pattern selection is required; do not use for persistence schema or deployment topology decisions.
- ▌ Git Bisect Debugging · planifest bundleLocate 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.
- ▌ Git Pr Sync Workflow · planifest bundleKeep 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.
- ▌ Platform Engineering · planifest bundlePlatform engineering covering Internal Developer Platform design, golden paths, self-service capabilities, paved roads, and developer portals; use when designing or evolving the platform a development organisation builds on.
- ▌ Planifest Verify By Execution · planifestVerifies acceptance criteria by actually running the software (browser click-throughs, real API calls, CLI invocations, log/DB checks), never by reading test output alone. Loaded by the P4 validate-agent after CI passes.
- ▌ Architecture Monolith · planifest bundleModular 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.
- ▌ CI CD Pipeline Design · planifest bundleDesign CI/CD pipelines with explicit stage order, quality gates, artifact traceability, and rollback safety. Use when build/test/release flow is being created or changed and teams need deterministic release controls before adoption; do not use for application-domain algorithm or schema design.
- ▌ DB Migration Strategy · planifest bundleSchema 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.
- ▌ DB Query Optimization · planifest bundleQuery 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.
- ▌ DB Transaction Design · planifest bundleTransaction 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.
- ▌ Distributed Consensus · planifest bundleConsensus 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.
- ▌ Feature Flag Strategy · planifest bundleFeature 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.
- ▌ Jest Testing Workflow · planifest bundleJest 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.
- ▌ Ml Data Preprocessing · planifest bundleML data preprocessing workflow for cleaning, normalization, and leakage-safe dataset preparation. Use when training/inference data pipelines need explicit preprocessing decisions; do not use for generic API-layer or infrastructure-only changes.
- ▌ Mlops Pipeline Design · planifest bundleMLOps pipeline design workflow for orchestrating training, validation, packaging, and promotion with explicit gates. Use when ML lifecycle stages must be automated end-to-end with traceable promotion criteria; do not use for model-architecture research decisions.
- ▌ Nextjs Best Practices · planifest bundleNext.js App Router principles. Server Components, data fetching, routing patterns.
- ▌ Observability Logging · planifest bundleObservability 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.
- ▌ Observability Metrics · planifest bundleObservability metrics workflow for metric model design aligned to service health and business impact. Use when teams define or revise service metrics/SLIs for reliable health and capacity decisions; do not use for business-feature implementation logic.
- ▌ Observability Tracing · planifest bundleObservability 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.
- ▌ Performance Profiling · planifest bundlePerformance 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.
- ▌ Stakeholder Interview · planifest bundleInternal stakeholder interview workflow for capturing constraints, decision authority, and policy requirements. Use when delivery is blocked by unresolved business, engineering, legal, security, or operations decisions; do not use for end-user behavior research.
- ▌ Technical Roadmapping · planifest bundleTechnical roadmap workflow for sequencing initiatives, dependencies, and risk-aware milestones. Use when teams must decide what technical work to do first across multiple increments; do not use for low-level code implementation details.
- ▌ Terraform Style Guide · planifest bundleStyle, review, and refactoring standards for Terraform infrastructure-as-code. Trigger when `.tf` or `.tfvars` source/modules/workflow configuration is created, changed, or reviewed and IaC-specific quality rules (module boundaries, variable typing, state safety, plan/apply discipline) must be enforced. Do not use for CloudFormation, Pulumi, or application-runtime coding conventions unless Terraform artifacts are also changed. Combine with language-specific guides only when application code and IaC both change.
- ▌ UX Research Synthesis · planifest bundleUX research synthesis workflow for turning mixed evidence into prioritized design actions. Use when multiple qualitative and quantitative inputs must be consolidated into clear design implications; do not use for backend architecture or deployment planning.
- ▌ DB Conceptual Modeling · planifest bundleConceptual 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.
- ▌ Django App Development · planifest bundleDjango 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.
- ▌ Git Cherry Pick Hotfix · planifest bundleSelect 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.
- ▌ Javascript Style Guide · planifest bundleStyle, review, and refactoring standards for JavaScript codebases with explicit runtime contracts, safe async behavior, and maintainable module boundaries. Use when `.js`, `.jsx`, `.mjs`, or `.cjs` artifacts are created, changed, or reviewed and JS-specific quality rules must be enforced. Do not use for `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json`-owned code. For shared JS/TS config files, run together with `typescript-style-guide` when both JS and TS artifacts change in the same pull request.
- ▌ Ml Experiment Tracking · planifest bundleML experiment tracking workflow for reproducibility, metadata integrity, and run comparison traceability. Use when multiple ML runs must be compared or reproduced reliably; do not use for generic API-layer or infrastructure-only changes.
- ▌ Ml Feature Engineering · planifest bundleML feature engineering workflow for feature definition, lineage, and online-offline parity. Use when model performance depends on explicit feature design and parity controls; do not use for generic API-layer or infrastructure-only changes.
- ▌ Mlops Monitoring Drift · planifest bundleMLOps drift monitoring workflow for detecting data drift, concept drift, and quality degradation with actionable response rules. Use when production ML systems need drift detection thresholds and escalation ownership; do not use for model-architecture research decisions.
- ▌ Observability Alerting · planifest bundleObservability 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.
- ▌ Powershell Style Guide · planifest bundleStyle, 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.
- ▌ React Component Design · planifest bundleReact component design workflow for state ownership, composition boundaries, and predictable rendering behavior. Use when React component behavior or structure must be implemented or revised; do not use for repository-wide architecture governance or release policy decisions.
- ▌ Redis Caching Patterns · planifest bundleRedis 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.
- ▌ Security Authorization · planifest bundleSecurity workflow for authorization boundaries, least-privilege policy, and enforcement design. Use when permission models, access decisions, or privileged action controls are required; do not use for authentication factor selection or non-security quality tuning.