‹ 首页

api-response-optimization

@aj-geddes · 收录于 5 天前 · 上游提交 4 个月前

Optimize API response times through caching, compression, and efficient payloads. Improve backend performance and reduce network traffic.

适合你,如果后端 API 响应慢、需要减少网络流量

/ 通过 npx 安装 校验哈希
npx oh-my-skill add aj-geddes/useful-ai-prompts/api-response-optimization
/ 通过 bash 安装
curl -fsSL https://oh-my-skill.com/install.sh | bash -s -- aj-geddes/useful-ai-prompts/api-response-optimization
/ 已经装过?验证本机副本,不用重装
npx oh-my-skill verify aj-geddes/useful-ai-prompts/api-response-optimization
安装目标可用 --agent / --scope 或 --to 明确指定;省略时只会在唯一已存在的 agent 目录上自动选择,零命中或多命中会停止并提示。content_hash 缺失或不一致均拒装。
300GitHub stars
~399最小装载
~1.3K含声明引用
~1.4K文本包总量
索引托管

怎么用

商店整理自技能原文 · 版本 3f5182c · 表述以原文为准
它做什么

当您请求优化API响应时,Claude会通过缓存、压缩和精简数据负载来减少传输量,从而提升后端性能和降低网络流量。

什么时候触发

当您提到API响应慢、服务器CPU或内存占用高、返回数据过大、性能下降或扩展瓶颈时触发。

装好后可以这样说
Claude会分析并给出缓存、压缩等建议。
Claude会指导精简字段和压缩方法。
Claude会检查并推荐优化策略。
技能原文 SKILL.md作者撰写 · MIT · 3f5182c

API Response Optimization

Table of Contents
  • [Overview](#overview)
  • [When to Use](#when-to-use)
  • [Quick Start](#quick-start)
  • [Reference Guides](#reference-guides)
  • [Best Practices](#best-practices)
Overview

Fast API responses improve overall application performance and user experience. Optimization focuses on payload size, caching, and query efficiency.

When to Use
  • Slow API response times
  • High server CPU/memory usage
  • Large response payloads
  • Performance degradation
  • Scaling bottlenecks
Quick Start

Minimal working example:

// Inefficient response (unnecessary data)
GET /api/users/123
{
  "id": 123,
  "name": "John",
  "email": "john@example.com",
  "password_hash": "...", // ❌ Should never send
  "ssn": "123-45-6789", // ❌ Sensitive data
  "internal_id": "xyz",
  "created_at": "2024-01-01T00:00:00Z",
  "updated_at": "2024-01-02T00:00:00Z",
  "meta_data": {...}, // ❌ Unused fields
  "address": {
    "street": "123 Main",
    "city": "City",
    "state": "ST",
    "zip": "12345",
    "geo": {...} // ❌ Not needed
  }
}

// Optimized response (only needed fields)
GET /api/users/123
{
  "id": 123,
// ... (see reference guides for full implementation)
Reference Guides

Detailed implementations in the references/ directory:

| Guide | Contents | |---|---| | [Response Payload Optimization](references/response-payload-optimization.md) | Response Payload Optimization | | [Caching Strategies](references/caching-strategies.md) | Caching Strategies | | [Compression & Performance](references/compression-performance.md) | Compression & Performance | | [Optimization Checklist](references/optimization-checklist.md) | Optimization Checklist |

Best Practices
✅ DO
  • Follow established patterns and conventions
  • Write clean, maintainable code
  • Add appropriate documentation
  • Test thoroughly before deploying
❌ DON'T
  • Skip testing or validation
  • Ignore error handling
  • Hard-code configuration values
按 MIT 许可原样转载,未经改动 · 在 GitHub 查看 →

评论

登录即可评论;带「已验证安装」的,是发布者名下有本店的安装或持有记录。