codex-skills-library

Manage Buffer content via the GraphQL API. Use when creating, scheduling, editing, or deleting posts, saving ideas, reading scheduled queues, or pulling post analytics. Not for general API debugging.

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 prompt optimization or prompt rewriting.

Edits, rewrites, or improves text for clarity, tone, grammar, or style.

Validate API changes against an expected contract. Use when a mid-level developer needs to detect breaking changes.

Define consistent API error codes and responses. Use when a mid-level developer needs error standardization.

Build a basic HTTP request (curl or fetch) for an API. Use when a junior developer needs a quick request example.

Optimize GraphQL queries and resolvers for performance. Use when a mid-level developer needs to reduce N+1 or payload size.

Review a system architecture for scalability, reliability, and maintainability. Use when a senior developer needs to critique a design.

Model domains and bounded contexts for complex systems. Use when a senior developer needs domain-driven design guidance.

Recommend caching strategies and invalidation patterns. Use when a mid-level developer needs performance guidance.

Plan feature flag rollout and cleanup. Use when a mid-level developer needs controlled release guidance.

Design safe queue consumers and retries. Use when a mid-level developer needs reliable background processing.

Draft a practical system design for a feature. Use when a mid-level developer needs a starting architecture.

Review data handling for privacy and retention. Use when a senior developer needs governance validation.

Review database migrations for safety and rollback. Use when a mid-level developer needs validation of schema changes.

Draft a basic SQL query from a simple requirement. Use when a junior developer needs help forming SELECT queries.

Write concise docstrings for functions. Use when a junior developer needs help describing inputs, outputs, and errors.

Improve a README for clarity and completeness. Use when a junior developer needs guidance on documenting setup and usage.

Draft release notes from changes and PRs. Use when a mid-level developer needs a structured changelog.

Create an onboarding guide for new engineers. Use when a senior developer needs structured onboarding materials.

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.

Explain a configuration file and its key options. Use when a junior developer is confused by a config file.

Recommend basic data structures for a task. Use when a junior developer needs help choosing lists, maps, or sets.

Provide a systematic debugging checklist. Use when a junior developer is stuck and needs a structured approach.

Guide installation of project dependencies and toolchains. Use when a junior developer is stuck setting up the environment.

Explain compiler/runtime errors in plain language. Use when a junior developer needs help understanding an error message.

Provide safe git commands for common tasks. Use when a junior developer needs help with branching, commits, or resolving simple conflicts.

Explain lint errors and propose fixes. Use when a junior developer needs help resolving common lint or format warnings.

Summarize noisy logs into likely causes and next steps. Use when a junior developer needs help interpreting logs.

Generate a small helper script for repetitive tasks. Use when a junior developer needs a quick automation snippet.

Break a task or ticket into small steps. Use when a junior developer needs guidance on how to start.

Run a basic accessibility checklist for UI changes. Use when a junior developer needs quick a11y guidance.

Improve CLI help, errors, and output. Use when a mid-level developer needs to make a CLI friendlier.

Explain CSS layout issues and propose fixes. Use when a junior developer is struggling with alignment or spacing.

Diagnose CI failures and stabilize pipelines. Use when a mid-level developer needs to resolve flaky or failing builds.

Coordinate debugging across multiple services. Use when a senior developer needs to trace a distributed issue.

Review infrastructure-as-code changes for safety and correctness. Use when a mid-level developer needs a second look on IaC.

Design a multi-region architecture strategy. Use when a senior developer needs geo-redundant planning.

Set up metrics, logs, and traces for a service. Use when a mid-level developer needs basic observability coverage.

Create a plan to migrate platforms or runtimes. Use when a senior developer needs a phased migration approach.