performance-budgeting
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
Découvrez les skills Vie quotidienne, comparez leurs dépôts et consultez leurs instructions.
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.
Improve and rewrite user prompts to reduce ambiguity and improve LLM output quality. Use when a user asks to optimize, refine, clarify, or rewrite a prompt for better results, or when the request is about promp...
Model domains and bounded contexts for complex systems. Use when a senior developer needs domain-driven design guidance.
Assess readiness for compliance audits. Use when a senior developer needs a gap analysis for standards.
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.
Le classement utilise les étoiles du dépôt GitHub indexé. Plusieurs skills peuvent partager ce nombre : ce n’est ni un nombre d’installations ni une note de qualité.