planifest
- 255 skills
- 0 followers
- last week last updated
- ▌ Security Secure Coding · planifest bundleSecurity workflow for secure-by-default coding decisions and vulnerability prevention in implementation changes. Use when application code paths process untrusted input, sensitive data, or privileged operations; do not use for policy-only governance without code impact.
- ▌ Testing Property Based · planifest bundleProperty-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.
- ▌ Typescript Style Guide · planifest bundleStyle, review, and refactoring standards for TypeScript codebases. Trigger when `.ts`, `.tsx`, `.d.ts`, or `tsconfig*.json` files are created, changed, or reviewed and TS-specific quality rules (type safety, narrowing, async/error handling, module boundaries) must be enforced. Do not use for JavaScript-only modules that are outside TypeScript type-check scope. In mixed JS/TS repositories, this skill owns `tsconfig`-scoped modules. For shared JS/TS configuration files (for example `package.json`, shared lint/test config), run together with `javascript-style-guide` when both JS and TS artifacts change in the same pull request.
- ▌ Web Video Presentation · planifest bundle把一篇文章或口播稿,做成"看起来像视频"的点击驱动 16:9 网页演示,可选合成口播音频。流程:原始文章 → **一次产出**口播稿 + outline 开发计划 → 用户**一次对齐** 5 件事(稿子 / outline / 主题 / 素材 / 开发模式)→ 网页开发(逐章 / 顺序 / 并行)→ 可选音频合成(默认 MiniMax CLI mmx-cli)。**outline 只规划节奏与信息密度,不规划动画** —— 动画由章节开发时按 PRINCIPLES + ANTI-AI 法则即时设计。每次点击推进口播稿的一个节拍,每一步独占整屏,进度条平时隐藏只在悬浮时出现。适用场景:用网页做视频(动态 PPT 但不像 PPT)、把口播稿 / 文章变成可交互的解说、为 B 站 / YouTube / 视频号录屏教程、做有电影感的产品 / talk demo。本 Skill 沉淀的是设计方法论 + 协作流程 —— 不绑定任何特定样式 / 字体 / 颜色 —— 因此能复用到任意主题与美学。
- ▌ Architecture Principles · planifest bundleDefine architecture principles and review guardrails before choosing monolith, microservices, serverless, or event-driven options. Use when teams need explicit decision criteria; do not use to record final decisions.
- ▌ Architecture Serverless · planifest bundleServerless architecture workflow for event-driven and bursty workloads using managed compute and platform services. Use when elasticity and reduced platform operations justify managed-service constraints; do not use when workload shape requires long-lived stateful control loops.
- ▌ Code Review Performance · planifest bundleRun performance-focused code review when changes may affect latency, throughput, or CPU/memory/I/O efficiency on critical paths. Use for merge decisions requiring explicit performance-risk findings; do not use for broad non-performance review scope.
- ▌ Cost Optimization Cloud · planifest bundleOptimize cloud spend with explicit tradeoffs across cost, performance, and reliability. Use when spend or forecast misses budget targets and teams need concrete optimization actions without violating SLOs or compliance constraints; do not use for purely functional product behavior design.
- ▌ DB Replication Sharding · planifest bundleReplication 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.
- ▌ Docker Compose Patterns · planifest bundleDesign multi-service local orchestration with Docker Compose, including dependency wiring, startup order, health checks, and shared network/storage boundaries. Use when local integration environments need deterministic service composition; do not use for production orchestration policy design.
- ▌ Express API Development · planifest bundleExpress API development workflow for production-ready Node.js services. Use when Express-specific API code (routing, middleware chain, validation, error handling, auth integration, request lifecycle behavior) must be implemented or revised; do not use for repository-wide architecture governance or release management policy.
- ▌ Github Address Comments · planifest bundleResolve GitHub PR review comments with structured triage, focused code changes, and reviewer-verifiable responses. Use when review threads need implementation follow-up and traceable closure; do not use for non-GitHub runtime architecture or data-layer design.
- ▌ Open Source Contributor · planifest bundleContributes effectively to open source projects — use when making first contributions, navigating unfamiliar codebases, writing PRs that will be accepted, or triaging issues.
- ▌ Requirement Elicitation · planifest bundleRequirement 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.
- ▌ Requirements Definition · planifest bundleCanonical 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.
- ▌ Security Authentication · planifest bundleSecurity workflow for authentication architecture, credential lifecycle, and session/token assurance. Use when login, identity proofing, MFA, or session security decisions are required; do not use for authorization policy design or non-security quality tuning.
- ▌ Sqlalchemy Orm Patterns · planifest bundleSQLAlchemy ORM workflow for model mapping, session/transaction boundaries, and query loading strategy. Use when SQLAlchemy ORM behavior must be implemented or revised with explicit persistence decisions; do not use for repository-wide architecture governance or release policy decisions.
- ▌
- ▌ Architecture C4 Modeling · planifest bundleC4 architecture modeling workflow for context, container, and component views that make boundaries and responsibilities explicit. Use when teams need a shared structural model before major implementation or refactoring; do not use as a substitute for decision records.
- ▌ Chaos Engineering Basics · planifest bundleDesign and execute controlled chaos experiments to validate resilience assumptions with explicit steady-state metrics, blast-radius limits, and abort rules. Use when reliability claims need evidence before wider rollout; do not use for active incident command or postmortem-only reporting.
- ▌ Ml Training Optimization · planifest bundleML training optimization workflow for convergence stability, efficiency, and cost control. Use when training runs are slow, unstable, or over budget and optimization decisions are required; do not use for generic API-layer or infrastructure-only changes.
- ▌ Performance Load Testing · planifest bundlePerformance 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.
- ▌ 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.