system-design-draft
Draft a practical system design for a feature. Use when a mid-level developer needs a starting architecture.
Discover Testing & security skills, compare source repositories and read the instructions for each workflow.
Draft a practical system design for a feature. Use when a mid-level developer needs a starting architecture.
Guide quick orientation of an unfamiliar codebase with module mapping, entry points, and local run steps. Use when a junior developer needs to get situated fast.
Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.
Improve CLI help, errors, and output. Use when a mid-level developer needs to make a CLI friendlier.
Generate a small helper script for repetitive tasks. Use when a junior developer needs a quick automation snippet.
Scan code or configuration for common security issues. Use when a mid-level developer needs a quick security pass.
Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.
Optimize GraphQL queries and resolvers for performance. Use when a mid-level developer needs to reduce N+1 or payload size.
Create a staged refactor plan for a module. Use when a mid-level developer needs a safe refactor path.
Diagnose CI failures and stabilize pipelines. Use when a mid-level developer needs to resolve flaky or failing builds.
Recommend caching strategies and invalidation patterns. Use when a mid-level developer needs performance guidance.
Draft an incident postmortem with timeline, RCA, and action items. Use when a senior developer needs a structured post-incident report.
Perform threat modeling for a system or feature. Use when a senior developer needs security risk assessment.
Define or review SLOs and SLAs for a service. Use when a senior developer needs reliability targets.
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.
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.