Why Use This
This skill provides specialized capabilities for jeremylongshore's codebase.
Use Cases
- Developing new features in the jeremylongshore repository
- Refactoring existing code to follow jeremylongshore standards
- Understanding and working with jeremylongshore's codebase structure
Install Guide
2 steps - 1
- 2
Install inside Ananke
Click Install Skill, paste the link below, then press Install.
https://github.com/jeremylongshore/claude-code-plugins-plus-skills/tree/main/plugins/saas-packs/clerk-pack/skills/clerk-performance-tuning
Skill Snapshot
Auto scan of skill assets. Informational only.
Valid SKILL.md
Checks against SKILL.md specification
Source & Community
Updated At Mar 11, 2026, 05:33 AM
Skill Stats
SKILL.md 62 Lines
Total Files 2
Total Size 2.1 KB
License MIT
---
name: clerk-performance-tuning
description: |
Optimize Clerk authentication performance.
Use when improving auth response times, reducing latency,
or optimizing Clerk SDK usage.
Trigger with phrases like "clerk performance", "clerk optimization",
"clerk slow", "clerk latency", "optimize clerk".
allowed-tools: Read, Write, Edit, Grep
version: 1.0.0
license: MIT
author: Jeremy Longshore <jeremy@intentsolutions.io>
compatible-with: claude-code, codex, openclaw
---
# Clerk Performance Tuning
## Overview
Optimize Clerk authentication for best performance and user experience.
## Prerequisites
- Clerk integration working
- Performance monitoring in place
- Understanding of application architecture
## Instructions
1. Step 1: Optimize Middleware
2. Step 2: Implement User Data Caching
3. Step 3: Optimize Token Handling
4. Step 4: Lazy Load Auth Components
5. Step 5: Optimize Server Components
6. Step 6: Edge Runtime Optimization
For full implementation details and code examples, load:
`Read(${CLAUDE_SKILL_DIR}/references/implementation-guide.md)`
## Output
- Optimized middleware configuration
- Multi-level caching strategy
- Token management optimization
- Lazy loading for auth components
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| Slow page loads | Blocking auth calls | Use Suspense boundaries |
| High latency | No caching | Implement token/user cache |
| Bundle size | All components loaded | Lazy load auth components |
| Cold starts | Node runtime | Use Edge runtime |
## Resources
- [Next.js Performance](https://nextjs.org/docs/app/building-your-application/optimizing)
- [Clerk Performance Tips](https://clerk.com/docs/quickstarts/nextjs)
- [Edge Runtime](https://nextjs.org/docs/app/api-reference/edge)
## Next Steps
Proceed to `clerk-cost-tuning` for cost optimization strategies.
## Examples
**Basic usage**: Apply clerk performance tuning to a standard project setup with default configuration options.
**Advanced scenario**: Customize clerk performance tuning for production environments with multiple constraints and team-specific requirements.