GitHub
incident-postmortem
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
☆ 27View skill
Databases AI Skills
Discover Databases skills, compare source repositories and read the instructions for each workflow.
Categories: Databases
Databases Clear filters
Browse skills
GitHub
threat-modeling
Perform threat modeling for a system or feature. Use when a senior developer needs security risk assessment.
☆ 27View skill
GitHub
reliability-slo-sla
Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.
☆ 27View skill
GitHub
performance-budgeting
Define performance budgets and guardrails. Use when a senior developer needs performance targets and enforcement.
☆ 27View skill
GitHub
team-onboarding-guide
Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.
☆ 27View skill
GitHub
prompt-optimization
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...
☆ 27View skill
GitHub
domain-modeling
Model domains and bounded contexts for complex systems. Use when a senior developer needs domain-driven design guidance.
☆ 27View skill
GitHub
compliance-readiness
Assess readiness for compliance audits. Use when a senior developer needs a gap analysis for standards.
☆ 27View skill
GitHub
platform-migration-plan
Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.
☆ 27View skill
GitHub
data-governance-check
Review data handling for privacy and retention. Use when a senior developer needs governance validation.
☆ 27View skill
GitHub
integration-test-planner
Plan integration tests across modules or services. Use when a mid-level developer needs to verify system interactions.
☆ 27View skill
GitHub
scalability-assessment
Assess a system for growth bottlenecks. Use when a senior developer needs to evaluate scaling limits.
☆ 27View skill
GitHub
observability-setup
Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.
☆ 27View skill
GitHub
debugging-checklist
Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.
☆ 27View skill
GitHub
feature-flag-playbook
Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.
☆ 27View skill
GitHub
dependency-upgrade-plan
Plan safe dependency upgrades with risk notes. Use when a mid-level developer is tasked with upgrading libraries.
☆ 27View skill
GitHub
unit-test-starter
Generate starter unit tests for a small function or module. Use when a junior developer needs test scaffolding and edge cases.
☆ 27View skill
GitHub
cross-service-debugger
Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.
☆ 27View skill
GitHub
multi-region-strategy
Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.
☆ 27View skill
GitHub
ticket-breakdown
Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.
☆ 27View skill
GitHub
config-file-explainer
Explain a configuration file and its key options. Use when a junior developer is confused by a config file.
☆ 27View skill
GitHub
iac-reviewer
Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.
☆ 27View skill
GitHub
cost-optimization-review
Review system costs and propose reductions. Use when a senior developer needs cost-saving recommendations.
☆ 27View skill
GitHub
data-structure-chooser
Recommend basic data structures for a task. Use when a junior developer needs help choosing lists, maps, or sets.
☆ 27View skill
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.