platform-migration-plan
Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.
Browse published AI skills maintained by proflead. Compare skill descriptions and follow each source repository for setup instructions.
Indexed skills
62Repository stars across indexed skills
1,674Repository forks
310Average repository stars per indexed skill
27Repository stars may repeat across skills from the same repository.
Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.
Review data handling for privacy and retention. Use when a senior developer needs governance validation.
Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.
Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.
Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.
Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.
Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.
Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
Explain a configuration file and its key options. Use when a junior developer is confused by a config file.
Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.
Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.
Recommend basic data structures for a task. Use when a junior developer needs help choosing lists, maps, or sets.
Design safe queue consumers and retries. Use when a mid-level developer needs reliable background processing.
Evaluate third-party vendors for engineering fit. Use when a senior developer needs a structured vendor assessment.
Improve a README for clarity and completeness. Use when a junior developer needs guidance on documenting setup and usage.
Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.
Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.
Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.
Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.
Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.
The default order uses GitHub repository stars from our indexed data. Stars belong to the source repository and may be shared by multiple skills. They indicate repository interest, not skill installs or an independent quality score.