planifest
- 233 skills
- 0 followers
- 15 hours ago last updated
- ▌ Responsive Layout Design · planifest bundleResponsive layout design workflow for defining adaptive structure and component behavior across viewport ranges. Use when UI layouts must remain usable and readable across device contexts; do not use for backend data modeling or deployment pipeline decisions.
- ▌ Security Threat Modeling · planifest bundleSecurity workflow for threat modeling using assets, trust boundaries, attacker capabilities, and abuse paths. Use when systems or major features need explicit security design validation before implementation or major release; do not use for active incident containment.
- ▌ Architecture Event Driven · planifest bundleEvent-driven architecture workflow for asynchronous integration, decoupled workflows, and failure-tolerant event propagation. Use when temporal decoupling and independent evolution are required; do not use when strict synchronous consistency is mandatory across all steps.
- ▌ Design System Foundations · planifest bundleDefine scalable design-system foundations with clear ownership and adoption boundaries. Use when multiple teams need shared component standards, foundational patterns, and ownership rules to deliver consistent UI across products; do not use for backend data-model or deployment pipeline decisions.
- ▌ Dockerfile Best Practices · planifest bundleDesign Dockerfiles for secure, deterministic, and efficient image builds with minimal attack surface and reproducible dependencies. Use when image build behavior, layer strategy, and runtime hardening need explicit decisions; do not use for non-container runtime code style concerns.
- ▌ Git History Investigation · planifest bundleReconstruct 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.
- ▌ Github Release Management · planifest bundlePackage and publish GitHub Releases with exact version/tag mapping, accurate release notes, and artifact integrity controls. Use when release publication on GitHub must be prepared or updated; do not use for non-GitHub runtime architecture or data-layer design.
- ▌ Acceptance Criteria Design · planifest bundleDesign executable acceptance criteria for approved requirements by converting goals/specs into binary pass/fail checks with observable outcomes. Use when implementation handoff, QA validation, or release decisions need testable criteria for stable `REQ-*`/`NFR-*` baselines; do not use for requirement discovery, prioritization, or sprint slicing.
- ▌ Architecture Microservices · planifest bundleMicroservices 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.
- ▌ Deployment Strategy Canary · planifest bundleDesign canary rollout strategy with progressive traffic steps, guardrail metrics, and automated stop/rollback decisions. Use when releases need incremental risk containment and evidence-based promotion gates; do not use for full-environment cutover planning where blue-green is required.
- ▌ Distributed Systems Basics · planifest bundleDistributed-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.
- ▌ Documentation Architecture · planifest bundleAuthor architecture documentation that explains boundaries, dependencies, and operational constraints for engineering decision-making. Use when architecture docs are primary deliverables or must be updated after structural changes; do not use for implementing production feature logic.
- ▌ Kubernetes Workload Design · planifest bundleKubernetes workload design workflow for resource sizing, autoscaling behavior, and safe rollout strategy. Use when workload specs need concrete sizing and resilience decisions to meet reliability/performance targets; do not use for API contract design or requirement prioritization.
- ▌ Requirement Prioritization · planifest bundleRequirement prioritization workflow for dependency-aware ranking and release cut-line decisions. Use when finalized requirement baselines need ordering under value, risk, and capacity constraints; do not use for requirement discovery.
- ▌ Risk Requirements Analysis · planifest bundleRequirement 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.
- ▌ Security Incident Response · planifest bundleSecurity incident workflow for triage, containment, eradication, and recovery evidence handling. Use when suspected or confirmed security incidents require coordinated response actions; do not use for proactive threat modeling or routine vulnerability backlog grooming.
- ▌ Documentation API Reference · planifest bundleAuthor API reference documentation that is accurate, complete, and implementation-aligned for client developers. Use when API docs are primary deliverables or must be updated for contract changes; do not use for implementing new product behavior.
- ▌ Fastapi Service Development · planifest bundleFastAPI 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.
- ▌ Non Functional Requirements · planifest bundleQuality attribute specification workflow after functional requirements are defined. Use when approved functional requirements need measurable performance/reliability/security/operability/compliance targets before implementation planning; do not use for initial requirement elicitation or sprint task breakdown.
- ▌ Schema Evolution Governance · planifest bundleSchema 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.
- ▌ Security Secrets Management · planifest bundleSecurity workflow for secret inventory, storage, distribution, rotation, and auditability controls. Use when API keys, credentials, certificates, or signing secrets lifecycle decisions are required; do not use for generic config management that excludes sensitive material.
- ▌ Testing Regression Strategy · planifest bundleRisk-based regression suite curation for release gating under time and budget limits. Use when teams must decide what runs always versus conditionally by impact and risk; do not use for implementing a single test type in isolation.
- ▌ Github Codeowners Management · planifest bundleGovern CODEOWNERS rules so review routing reflects real ownership and risk boundaries on GitHub. Use when repository ownership mapping or mandatory reviewer rules must be defined, updated, or audited; do not use for non-GitHub runtime architecture or data-layer design.
- ▌ Algorithm Complexity Analysis · planifest bundleAnalyze candidate algorithms for time/space complexity, scalability limits, and resource-budget fit (CPU, memory, I/O, concurrency). Use when feasibility depends on input growth or latency/memory constraints and quantitative bounds are required before implementation; do not use for persistence schema or deployment topology decisions.
- ▌ Architecture Decision Records · planifest bundleArchitecture 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.
- ▌ Git Merge Conflict Resolution · planifest bundleResolve Git merge/rebase conflicts with explicit intent tracking and post-resolution verification. Use when conflicts occur and intent-preserving resolution is required before integration; do not use for CI workflow design or application behavior implementation.
- ▌ Performance Capacity Planning · planifest bundlePerformance capacity planning workflow for forecasting demand, defining headroom policy, and preventing saturation-related SLO breaches. Use when traffic growth or workload forecasts require explicit capacity and threshold decisions; do not use for non-performance functional acceptance decisions.
- ▌ Architecture Tradeoff Analysis · planifest bundleArchitecture 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.
- ▌ Deployment Strategy Blue Green · planifest bundleDesign blue-green deployment strategy with explicit cutover checks, rollback triggers, and state/data compatibility safeguards. Use when release risk requires fast rollback and environment-level switch control; do not use for canary-percentage experimentation policy design.
- ▌ Github Actions Workflow Design · planifest bundleDesign and maintain GitHub Actions workflows with explicit trigger scope, security boundaries, and reliable job orchestration. Use when GitHub automation (build/test/release jobs, triggers, permissions, caching, concurrency, environments) must be created or revised; do not use for non-GitHub runtime architecture or data-layer design.
- ▌ Architecture Clean Architecture · planifest bundleClean 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.
- ▌ Design QA Implementation Parity · planifest bundleVerify implementation parity against approved design specs with severity-based decisions and fix guidance. Use when implemented UI must be compared against approved specs before release or sign-off; do not use for backend data-model or deployment pipeline decisions.
- ▌ Security Vulnerability Management · planifest bundleSecurity workflow for vulnerability intake, triage, remediation planning, and fix verification. Use when vulnerabilities from scans, reports, or incidents must be prioritized and driven to closure; do not use for incident command during ongoing active compromise.