http-cache skill
Generates a production HTTP caching layer for Swift applications with support for Cache-Control, ETags, and offline fallback.
- GitHub stars
- 882
- Files
- 3
- Last commit
- Nov 9, 2026
- License
- MIT
- Allowed tools
- 7
What does the http-cache skill do?
http-cache generates a production HTTP caching layer for Swift applications with support for Cache-Control, ETags, and offline fallback.
Summary generated from the skill's SKILL.md.
About the http-cache skill
Adding a production HTTP caching layer to Swift applications is what this skill enables for iOS and macOS developers. It automates the creation of networking components that manage Cache-Control directives, ETag conditional requests, and stale-while-revalidate logic. An agent should load this tool when a developer needs to reduce API calls, implement offline fallback, or handle 304 Not Modified responses.
The process begins by scanning the project for existing networking code using Glob and Grep to identify APIClient protocols or URLSession usage. It then generates a suite of Swift files including configuration settings, header parsers, and disk-backed response stores. Depending on user preferences, it can produce a decorator to wrap existing clients or a standalone cache system. The output includes specialized files like CachingAPIClient.swift and NetworkReachability.swift to ensure the new layer integrates correctly with the existing architecture.
What an agent can do with it
- 1Implement offline supportAdd functionality to serve stale cached data when the device has no network connection.
- 2Automate ETag handlingSet up conditional requests using ETags and Last-Modified headers to optimize data fetching.
- 3Configure custom cache storageDefine specific memory and disk limits for the application's caching layer.
Written from the skill's SKILL.md. Every use case is checked against a quote from it.
How to install the http-cache skill
Each command copies the skill folder into the client's skills directory. Restart the client or start a new session to load it.Install the http-cache skill in Claude Code
~/.claude/skills/http-cache/SKILL.md
$ npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache ~/.claude/skills/http-cacheInstall the http-cache skill in Claude Code (project)
.claude/skills/http-cache/SKILL.md
$ npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache .claude/skills/http-cacheInstall the http-cache skill in Codex
~/.agents/skills/http-cache/SKILL.md
$ npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache ~/.agents/skills/http-cacheInstall the http-cache skill in Gemini CLI
~/.gemini/skills/http-cache/SKILL.md
$ npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache ~/.gemini/skills/http-cacheInstall the http-cache skill in Claude.ai
npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache http-cache && zip -r http-cache.zip http-cache # claude.ai → Customize → Skills → + → Create skill → Upload a skill → http-cache.zip
Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A skill needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablershankras/claude-code-apple-skills/skills/generators/http-cache is public and reachablegithub.com/rshankras/claude-code-apple-skills/tree/HEAD/skil ↗Pass
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit 2026-11-09github.com/rshankras/claude-code-apple-skills/commits ↗Pass
- No download-and-run or credential theft in scriptsNo scripts in the skill folderPass
- No hidden instructions in SKILL.mdNo override phrases, safeguard switches, credential requests or hidden charactersgithub.com/rshankras/claude-code-apple-skills/blob/HEAD/skil ↗Pass
- Pre-approved tools are scopedBash lets the agent run any shell command without askinggithub.com/rshankras/claude-code-apple-skills/blob/HEAD/skil ↗Finding
- SKILL.md follows the Agent Skills formatValid name and description; says when to use it; 183 linesgithub.com/rshankras/claude-code-apple-skills/blob/HEAD/skil ↗Pass
SKILL.md
View on GitHubHTTP Cache Generator
Generate a production HTTP caching layer that integrates with your existing networking code. Supports Cache-Control directives, ETag/Last-Modified conditional requests, stale-while-revalidate, and offline fallback.
When This Skill Activates
Use this skill when the user:
- Asks to "add HTTP caching" or "cache API responses"
- Wants "offline support" or "offline fallback"
- Mentions "reduce API calls" or "cache network responses"
- Asks about "ETag" or "conditional requests" or "304 Not Modified"
- Wants "stale-while-revalidate" behavior
Pre-Generation Checks
1. Project Context Detection
- Check Swift version (requires Swift 5.9+)
- Check deployment target (iOS 16+ / macOS 13+)
- Search for existing caching implementations
- Identify source file locations
2. Networking Layer Detection
Search for existing networking code:
Glob: **/*API*.swift, **/*Client*.swift, **/*Network*.swift
Grep: "APIClient" or "URLSession" or "HTTPURLResponse"
If networking-layer generator was used, detect the APIClient protocol and generate a decorator that wraps it.
3. Conflict Detection
Search for existing caching:
Glob: **/*Cache*.swift
Grep: "URLCache" or "ResponseCache" or "CachePolicy"
If found, ask user whether to replace or extend.
Configuration Questions
Ask user via AskUserQuestion:
-
Cache storage sizes?
- Small (10 MB memory / 50 MB disk)
- Medium (25 MB memory / 100 MB disk) — recommended
- Large (50 MB memory / 250 MB disk)
-
Caching strategy?
- Respect server Cache-Control headers (standard)
- Cache-first with background revalidation (stale-while-revalidate)
- Manual per-endpoint policies
-
Offline support?
- Yes — serve stale cache when network unavailable
- No — only cache while online
-
Integration style?
- Decorator wrapping existing APIClient (recommended if networking-layer exists)
- Standalone cache you call directly
Generation Process
Step 1: Read Templates
Read http-cache-patterns.md for architecture guidance.
Read templates.md for production Swift code.
Step 2: Create Core Files
Generate these files:
HTTPCacheConfiguration.swift— Memory/disk sizes, default policyCachePolicy.swift— Per-endpoint enum (default, noCache, forceCache, cacheFirst)CacheControlHeader.swift— Cache-Control header parserConditionalRequestHandler.swift— ETag/Last-Modified/304 handlingHTTPResponseCache.swift— Protocol + disk-backed response store
Step 3: Create Integration Files
Based on configuration:
CachingAPIClient.swift— Decorator wrapping existing APIClient (if decorator style)NetworkReachability.swift— NWPathMonitor wrapper (if offline support selected)
Step 4: Determine File Location
Check project structure:
- If
Sources/Networking/exists →Sources/Networking/Cache/ - If
App/Networking/exists →App/Networking/Cache/ - If
Networking/exists →Networking/Cache/ - Otherwise →
Cache/
Output Format
After generation, provide:
Files Created
Networking/Cache/
├── HTTPCacheConfiguration.swift # Memory/disk sizes, default policy
├── CachePolicy.swift # Per-endpoint caching enum
├── CacheControlHeader.swift # Cache-Control header parser
├── ConditionalRequestHandler.swift # ETag/Last-Modified/304
├── HTTPResponseCache.swift # Protocol + disk implementation
├── CachingAPIClient.swift # Decorator for existing APIClient
└── NetworkReachability.swift # NWPathMonitor (optional)
Integration Steps
Wrap your existing client:
let baseClient = URLSessionAPIClient(configuration: .production)
let cachingClient = CachingAPIClient(
wrapping: baseClient,
cache: DiskHTTPResponseCache(),
configuration: .default
)
// Use cachingClient everywhere you used baseClient
let users = try await cachingClient.request(UsersEndpoint())
Per-endpoint cache policy:
struct UsersEndpoint: APIEndpoint, CacheConfigurable {
var cachePolicy: CachePolicy { .cacheFirst(maxAge: 300) }
}
struct OrdersEndpoint: APIEndpoint, CacheConfigurable {
var cachePolicy: CachePolicy { .noCache }
}
With SwiftUI:
struct UsersView: View {
@Environment(\.apiClient) private var apiClient
var body: some View {
List(users) { user in
Text(user.name)
}
.task {
// Automatically uses cache if available
users = try await apiClient.request(UsersEndpoint())
}
}
}
Testing
@Test
func cachedResponseReturnedOnSecondRequest() async throws {
let mockClient = MockAPIClient()
let cache = InMemoryHTTPResponseCache()
let cachingClient = CachingAPIClient(wrapping: mockClient, cache: cache)
mockClient.mockResponse(for: UsersEndpoint.self, response: [.mock])
// First request hits network
let first = try await cachingClient.request(UsersEndpoint())
#expect(mockClient.requestCount == 1)
// Second request comes from cache
let second = try await cachingClient.request(UsersEndpoint())
#expect(mockClient.requestCount == 1) // No additional network call
#expect(first == second)
}
References
- http-cache-patterns.md — Cache-Control directives, ETag flow, stale-while-revalidate
- templates.md — All production Swift templates
- Related:
generators/networking-layer— Base networking layer this decorates
Files in this skill
3http-cache skill questions
How do I install the http-cache skill in Claude Code?
Run npx degit rshankras/claude-code-apple-skills/skills/generators/http-cache ~/.claude/skills/http-cache. Claude Code loads skills from ~/.claude/skills (all projects) or .claude/skills (one project) and uses a skill when its description matches the task.
Which clients can use the http-cache skill?
Any client that reads the Agent Skills format: Claude Code, Codex, Gemini CLI and claude.ai (upload as a ZIP). Scripts in the skill run only where the client allows code execution.
What features does the HTTP caching layer support?
It supports Cache-Control directives, ETag/Last-Modified conditional requests, stale-while-revalidate, and offline fallback.
How can I integrate the generated cache with my existing API client?
You can wrap your existing client using the CachingAPIClient decorator.