claude-code-templates 1.13.2 → 1.14.1
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +44 -239
- package/components/agents/api-security-audit.md +92 -0
- package/components/agents/database-optimization.md +94 -0
- package/components/agents/react-performance-optimization.md +64 -0
- package/components/commands/check-file.md +53 -0
- package/components/commands/generate-tests.md +68 -0
- package/components/mcps/deepgraph-nextjs.json +12 -0
- package/components/mcps/deepgraph-react.json +12 -0
- package/components/mcps/deepgraph-typescript.json +12 -0
- package/components/mcps/deepgraph-vue.json +12 -0
- package/components/mcps/filesystem-access.json +12 -0
- package/components/mcps/github-integration.json +11 -0
- package/components/mcps/memory-integration.json +8 -0
- package/components/mcps/mysql-integration.json +11 -0
- package/components/mcps/postgresql-integration.json +11 -0
- package/components/mcps/web-fetch.json +8 -0
- package/package.json +2 -1
- package/src/analytics-web/components/AgentsPage.js +33 -16
- package/src/analytics-web/components/DashboardPage.js +35 -105
- package/src/analytics-web/components/HeaderComponent.js +307 -0
- package/src/analytics-web/index.html +10 -27
- package/src/analytics-web/services/DataService.js +13 -0
- package/src/health-check.js +48 -44
- package/src/index.js +54 -2
- package/src/tracking-service.js +188 -0
package/README.md
CHANGED
|
@@ -7,269 +7,74 @@
|
|
|
7
7
|
|
|
8
8
|
# Claude Code Templates
|
|
9
9
|
|
|
10
|
-
**CLI tool for configuring and monitoring Claude Code** - Quick setup for any project with framework-specific commands and real-time monitoring dashboard.
|
|
10
|
+
**CLI tool for configuring and monitoring Claude Code** - Quick setup for any project with framework-specific commands and real-time monitoring dashboard.
|
|
11
11
|
|
|
12
|
-
##
|
|
12
|
+
## 🚀 Quick Start
|
|
13
13
|
|
|
14
14
|
```bash
|
|
15
|
-
#
|
|
15
|
+
# Interactive setup (recommended)
|
|
16
16
|
npx claude-code-templates@latest
|
|
17
|
-
```
|
|
18
|
-
|
|
19
|
-
## Core Features
|
|
20
|
-
|
|
21
|
-
### 📊 Real-time Analytics Dashboard
|
|
22
|
-
Monitor and optimize your Claude Code agents with our comprehensive analytics dashboard:
|
|
23
|
-
- **Live Session Tracking**: See active conversations and their status in real-time
|
|
24
|
-
- **Real-time State Detection**: "Claude Code working...", "User typing...", "Awaiting user input..."
|
|
25
|
-
- **Usage Statistics**: Total sessions, tokens, and project activity with interactive charts
|
|
26
|
-
- **Conversation History**: Complete session logs with export capabilities (CSV/JSON)
|
|
27
|
-
- **Browser Notifications**: Get notified when Claude is waiting for your input
|
|
28
|
-
- **Performance Monitoring**: Track Claude Code agent performance and optimization opportunities
|
|
29
|
-
- **Web Interface**: Clean, terminal-style dashboard at `http://localhost:3333`
|
|
30
|
-
|
|
31
|
-
### 🔍 Comprehensive Health Check
|
|
32
|
-
Complete system validation and configuration verification:
|
|
33
|
-
- **System Requirements**: Validate OS, Node.js, memory, and network connectivity
|
|
34
|
-
- **Claude Code Setup**: Verify installation, authentication, and permissions
|
|
35
|
-
- **Project Configuration**: Check project structure and configuration files
|
|
36
|
-
- **Custom Commands**: Validate slash commands and syntax
|
|
37
|
-
- **Hooks Configuration**: Verify automation hooks and command availability
|
|
38
|
-
- **Interactive Results**: Real-time progress with immediate feedback and recommendations
|
|
39
|
-
- **Health Score**: Overall system health percentage with actionable insights
|
|
40
|
-
|
|
41
|
-
### 📋 Smart Project Setup
|
|
42
|
-
Intelligent project configuration with framework-specific commands:
|
|
43
|
-
- **Auto-Detection**: Automatically detect your project type and suggest optimal configurations
|
|
44
|
-
- **Quick Setup**: Framework-specific commands for testing, linting, building, debugging, and deployment
|
|
45
|
-
- **Optimized Workflows**: Pre-configured commands tailored to your development stack
|
|
46
|
-
- **Best Practices**: Industry-standard configurations and development patterns
|
|
47
|
-
|
|
48
|
-
## What Gets Installed
|
|
49
|
-
|
|
50
|
-
### Core Files
|
|
51
|
-
- **`CLAUDE.md`** - Main configuration file with language-specific best practices
|
|
52
|
-
- **`.claude/settings.json`** - Automation hooks and Claude Code settings
|
|
53
|
-
- **`.claude/commands/`** - Custom commands for common development tasks
|
|
54
|
-
- **`.mcp.json`** - Model Context Protocol server configurations
|
|
55
|
-
|
|
56
|
-
## Supported Languages & Frameworks
|
|
57
|
-
|
|
58
|
-
| Language | Frameworks | Status | Commands | Hooks | MCP |
|
|
59
|
-
|----------|------------|---------|----------|--------|-----|
|
|
60
|
-
| **JavaScript/TypeScript** | React, Vue, Angular, Node.js | ✅ Ready | 7+ | 9+ | 4+ |
|
|
61
|
-
| **Python** | Django, Flask, FastAPI | ✅ Ready | 5+ | 8+ | 4+ |
|
|
62
|
-
| **Common** | Universal | ✅ Ready | 2+ | 1+ | 4+ |
|
|
63
|
-
| **Go** | Gin, Echo, Fiber | 🚧 Coming Soon | - | - | - |
|
|
64
|
-
| **Rust** | Axum, Warp, Actix | 🚧 Coming Soon | - | - | - |
|
|
65
|
-
|
|
66
|
-
## Usage Examples
|
|
67
|
-
|
|
68
|
-
### Interactive Setup (Recommended)
|
|
69
|
-
```bash
|
|
70
|
-
cd my-react-app
|
|
71
|
-
npx claude-code-templates
|
|
72
|
-
# Choose between Analytics Dashboard, Health Check, or Project Setup
|
|
73
|
-
```
|
|
74
17
|
|
|
75
|
-
|
|
76
|
-
|
|
77
|
-
# Launch real-time analytics dashboard
|
|
78
|
-
npx claude-code-templates --analytics
|
|
18
|
+
# Real-time analytics dashboard
|
|
19
|
+
npx claude-code-templates@latest --analytics
|
|
79
20
|
|
|
80
|
-
#
|
|
81
|
-
npx claude-code-templates --
|
|
82
|
-
npx claude-code-templates --agents
|
|
21
|
+
# System health check
|
|
22
|
+
npx claude-code-templates@latest --health-check
|
|
83
23
|
```
|
|
84
24
|
|
|
85
|
-
|
|
86
|
-
```bash
|
|
87
|
-
# Run comprehensive system validation
|
|
88
|
-
npx claude-code-templates --health-check
|
|
89
|
-
npx claude-code-templates --health
|
|
90
|
-
npx claude-code-templates --check
|
|
91
|
-
npx claude-code-templates --verify
|
|
92
|
-
```
|
|
25
|
+
## ✨ Core Features
|
|
93
26
|
|
|
94
|
-
|
|
95
|
-
|
|
96
|
-
|
|
97
|
-
|
|
27
|
+
- **📋 Smart Project Setup** - Auto-detect and configure any project with framework-specific commands
|
|
28
|
+
- **📊 Real-time Analytics** - Monitor Claude Code sessions with live state detection and performance metrics
|
|
29
|
+
- **🔍 Health Check** - Comprehensive system validation with actionable recommendations
|
|
30
|
+
- **🧩 Individual Components** - Install specialized agents, commands, and MCPs individually
|
|
98
31
|
|
|
99
|
-
|
|
100
|
-
npx claude-code-templates --language python --framework django --yes
|
|
101
|
-
```
|
|
102
|
-
|
|
103
|
-
### Analysis Tools
|
|
104
|
-
```bash
|
|
105
|
-
# Analyze existing commands
|
|
106
|
-
npx claude-code-templates --commands-stats
|
|
32
|
+
## 🎯 What You Get
|
|
107
33
|
|
|
108
|
-
|
|
109
|
-
|
|
110
|
-
|
|
111
|
-
|
|
112
|
-
|
|
113
|
-
|
|
114
|
-
|
|
115
|
-
### Alternative Commands
|
|
116
|
-
All these commands work exactly the same way:
|
|
117
|
-
|
|
118
|
-
```bash
|
|
119
|
-
npx claude-code-templates # ✅ Recommended (package name)
|
|
120
|
-
npx cct # ⚡ Super short (3 letters)
|
|
121
|
-
npx claude-setup # Setup-style command
|
|
122
|
-
npx create-claude-config # Create-style command
|
|
123
|
-
```
|
|
34
|
+
| Component | Description | Example |
|
|
35
|
+
|-----------|-------------|---------|
|
|
36
|
+
| **CLAUDE.md** | Project-specific Claude Code configuration | Framework best practices, coding standards |
|
|
37
|
+
| **Commands** | Custom slash commands for development tasks | `/generate-tests`, `/check-file`, `/optimize-bundle` |
|
|
38
|
+
| **Agents** | AI specialists for specific domains | API security audit, React performance, database optimization |
|
|
39
|
+
| **MCPs** | External service integrations | GitHub, databases, development tools |
|
|
40
|
+
| **Analytics** | Real-time monitoring dashboard | Live session tracking, usage statistics, exports |
|
|
124
41
|
|
|
125
|
-
##
|
|
42
|
+
## 🛠️ Supported Technologies
|
|
126
43
|
|
|
127
|
-
|
|
|
128
|
-
|
|
129
|
-
|
|
|
130
|
-
|
|
|
131
|
-
|
|
|
132
|
-
|
|
|
133
|
-
|
|
|
134
|
-
| `--analytics` | Launch real-time analytics dashboard | `--analytics` |
|
|
135
|
-
| `--chats` | Launch chats/conversations dashboard | `--chats` |
|
|
136
|
-
| `--agents` | Launch agents dashboard (alias for chats) | `--agents` |
|
|
137
|
-
| `--health-check` | Run comprehensive system validation | `--health-check` |
|
|
138
|
-
| `--health` | Run system health check (alias) | `--health` |
|
|
139
|
-
| `--check` | Run system validation (alias) | `--check` |
|
|
140
|
-
| `--verify` | Verify system configuration (alias) | `--verify` |
|
|
141
|
-
| `--commands-stats` | Analyze existing commands | `--commands-stats` |
|
|
142
|
-
| `--hooks-stats` | Analyze automation hooks | `--hooks-stats` |
|
|
143
|
-
| `--mcps-stats` | Analyze MCP server configurations | `--mcps-stats` |
|
|
144
|
-
| `--help` | Show help information | `--help` |
|
|
44
|
+
| Language | Frameworks | Status |
|
|
45
|
+
|----------|------------|---------|
|
|
46
|
+
| **JavaScript/TypeScript** | React, Vue, Angular, Node.js | ✅ Ready |
|
|
47
|
+
| **Python** | Django, Flask, FastAPI | ✅ Ready |
|
|
48
|
+
| **Common** | Universal configurations | ✅ Ready |
|
|
49
|
+
| **Go** | Gin, Echo, Fiber | 🚧 Coming Soon |
|
|
50
|
+
| **Rust** | Axum, Warp, Actix | 🚧 Coming Soon |
|
|
145
51
|
|
|
146
|
-
##
|
|
52
|
+
## 📖 Documentation
|
|
147
53
|
|
|
148
|
-
|
|
54
|
+
**[📚 Complete Documentation](https://aitmpl.com/docu/)** - Comprehensive guides, examples, and API reference
|
|
149
55
|
|
|
150
|
-
|
|
151
|
-
|
|
152
|
-
|
|
153
|
-
-
|
|
154
|
-
-
|
|
155
|
-
-
|
|
156
|
-
- **`FileWatcher`** - Real-time file system monitoring with efficient change detection
|
|
157
|
-
- **`DataCache`** - Multi-level caching system with smart invalidation strategies
|
|
158
|
-
|
|
159
|
-
#### Data Layer
|
|
160
|
-
- **`DataCache`** - Intelligent caching with file content, parsed data, and computation result caching
|
|
161
|
-
- **Performance Monitoring** - Request tracking, memory monitoring, and system health metrics
|
|
162
|
-
|
|
163
|
-
#### Notification System
|
|
164
|
-
- **`WebSocketServer`** - Real-time WebSocket communication with client management
|
|
165
|
-
- **`NotificationManager`** - Event-driven notification system with subscription management
|
|
166
|
-
- **Real-time Updates** - Live conversation state changes and data refresh notifications
|
|
167
|
-
|
|
168
|
-
#### Performance & Monitoring
|
|
169
|
-
- **`PerformanceMonitor`** - Comprehensive performance tracking and system health monitoring
|
|
170
|
-
- **Express Middleware** - Request timing, error tracking, and API performance metrics
|
|
171
|
-
- **WebSocket Monitoring** - Connection tracking, message metrics, and client health monitoring
|
|
172
|
-
|
|
173
|
-
### Frontend Architecture
|
|
174
|
-
|
|
175
|
-
#### Modular Components
|
|
176
|
-
- **`Dashboard`** - Main orchestration component with state management integration
|
|
177
|
-
- **`ConversationTable`** - Interactive conversation display with real-time status updates
|
|
178
|
-
- **`Charts`** - Dynamic data visualization with Chart.js integration
|
|
179
|
-
- **`StateService`** - Reactive state management with subscriber patterns
|
|
180
|
-
- **`DataService`** - API communication with intelligent caching and real-time integration
|
|
181
|
-
- **`WebSocketService`** - Real-time communication with automatic reconnection
|
|
182
|
-
|
|
183
|
-
#### Real-time Features
|
|
184
|
-
- **Live State Detection** - Real-time conversation status: "Claude working...", "User typing...", "Awaiting input..."
|
|
185
|
-
- **Auto-refresh** - Smart polling with WebSocket fallback for seamless data updates
|
|
186
|
-
- **Browser Notifications** - Desktop notifications for important state changes
|
|
187
|
-
- **Responsive Design** - Mobile-friendly interface with real-time data synchronization
|
|
188
|
-
|
|
189
|
-
### Performance Optimizations
|
|
190
|
-
|
|
191
|
-
#### Caching Strategy
|
|
192
|
-
- **File Content Cache** - Reduces disk I/O with timestamp-based invalidation
|
|
193
|
-
- **Parsed Data Cache** - Stores analyzed conversation data with dependency tracking
|
|
194
|
-
- **API Response Cache** - Client-side caching with TTL and smart refresh
|
|
195
|
-
- **Computation Cache** - Caches expensive calculations with automatic invalidation
|
|
196
|
-
|
|
197
|
-
#### Real-time Efficiency
|
|
198
|
-
- **WebSocket Integration** - Eliminates polling overhead for live updates
|
|
199
|
-
- **Smart Refresh** - Only updates changed data with differential loading
|
|
200
|
-
- **Process Detection** - Efficient system process monitoring without performance impact
|
|
201
|
-
- **Memory Management** - Automatic cleanup of old metrics and cached data
|
|
202
|
-
|
|
203
|
-
### Testing Framework
|
|
204
|
-
|
|
205
|
-
#### Comprehensive Test Suite
|
|
206
|
-
- **Unit Tests** - Individual module testing with 80%+ coverage requirement
|
|
207
|
-
- **Integration Tests** - End-to-end system testing with real data scenarios
|
|
208
|
-
- **Performance Tests** - Load testing and performance regression detection
|
|
209
|
-
- **WebSocket Tests** - Real-time communication testing with mock clients
|
|
210
|
-
|
|
211
|
-
#### Test Coverage
|
|
212
|
-
- **Backend Modules**: StateCalculator, DataCache, WebSocketServer, PerformanceMonitor
|
|
213
|
-
- **Frontend Services**: DataService, StateService, WebSocketService
|
|
214
|
-
- **Integration Testing**: Complete analytics system with real conversation data
|
|
215
|
-
- **Performance Testing**: Concurrent operations, memory usage, and response times
|
|
216
|
-
|
|
217
|
-
### Development Benefits
|
|
218
|
-
|
|
219
|
-
#### Scalability
|
|
220
|
-
- **Modular Design** - Easy to extend with new features and integrations
|
|
221
|
-
- **Dependency Injection** - Loose coupling for flexible testing and development
|
|
222
|
-
- **Event-driven Architecture** - Scalable notification system for future enhancements
|
|
223
|
-
|
|
224
|
-
#### Maintainability
|
|
225
|
-
- **Separation of Concerns** - Clear boundaries between data, business logic, and presentation
|
|
226
|
-
- **Comprehensive Logging** - Detailed performance and error tracking for debugging
|
|
227
|
-
- **Type Safety** - Consistent error handling and data validation throughout
|
|
228
|
-
|
|
229
|
-
#### Performance
|
|
230
|
-
- **Multi-level Caching** - Optimized data access patterns with intelligent invalidation
|
|
231
|
-
- **Real-time Updates** - WebSocket-based communication eliminates polling overhead
|
|
232
|
-
- **Memory Optimization** - Automatic cleanup and configurable memory thresholds
|
|
233
|
-
- **Request Monitoring** - Complete visibility into system performance and bottlenecks
|
|
234
|
-
|
|
235
|
-
## Safety Features
|
|
236
|
-
|
|
237
|
-
- **Automatic Backups**: Existing files are backed up before changes
|
|
238
|
-
- **Confirmation Required**: Always asks before making changes (unless `--yes` flag)
|
|
239
|
-
- **Dry Run Mode**: Preview installation with `--dry-run`
|
|
240
|
-
- **Cancel Anytime**: Press Ctrl+C or answer 'No' to cancel
|
|
241
|
-
|
|
242
|
-
## What Makes This Special?
|
|
243
|
-
|
|
244
|
-
### Before (Manual Setup)
|
|
245
|
-
- Hours of configuration research
|
|
246
|
-
- Manual CLAUDE.md creation
|
|
247
|
-
- Framework-specific command setup
|
|
248
|
-
- Automation hook configuration
|
|
249
|
-
- MCP server integration
|
|
250
|
-
|
|
251
|
-
### After (With Templates)
|
|
252
|
-
```bash
|
|
253
|
-
npx claude-code-templates --language javascript-typescript --framework react --yes
|
|
254
|
-
# ✅ Done in 30 seconds!
|
|
255
|
-
```
|
|
56
|
+
Quick links:
|
|
57
|
+
- [Getting Started](https://aitmpl.com/docu/docs/intro) - Installation and first steps
|
|
58
|
+
- [Project Setup](https://aitmpl.com/docu/docs/project-setup/interactive-setup) - Configure your projects
|
|
59
|
+
- [Analytics Dashboard](https://aitmpl.com/docu/docs/analytics/overview) - Real-time monitoring
|
|
60
|
+
- [Individual Components](https://aitmpl.com/docu/docs/components/overview) - Agents, Commands, MCPs
|
|
61
|
+
- [CLI Options](https://aitmpl.com/docu/docs/cli-options) - All available commands
|
|
256
62
|
|
|
257
63
|
## 🤝 Contributing
|
|
258
64
|
|
|
259
|
-
We welcome contributions
|
|
260
|
-
|
|
261
|
-
**See our [GitHub repository](https://github.com/davila7/claude-code-templates) for detailed guidelines**
|
|
65
|
+
We welcome contributions! Browse available templates and components at **[aitmpl.com](https://aitmpl.com)**, then check our [contributing guidelines](https://github.com/davila7/claude-code-templates/blob/main/CONTRIBUTING.md).
|
|
262
66
|
|
|
263
67
|
## 📄 License
|
|
264
68
|
|
|
265
|
-
|
|
69
|
+
MIT License - see the [LICENSE](LICENSE) file for details.
|
|
266
70
|
|
|
267
|
-
##
|
|
71
|
+
## 🔗 Links
|
|
268
72
|
|
|
269
|
-
-
|
|
270
|
-
-
|
|
271
|
-
-
|
|
73
|
+
- **🌐 Browse Components**: [aitmpl.com](https://aitmpl.com)
|
|
74
|
+
- **📚 Documentation**: [aitmpl.com/docu](https://aitmpl.com/docu)
|
|
75
|
+
- **🐛 Issues**: [GitHub Issues](https://github.com/davila7/claude-code-templates/issues)
|
|
76
|
+
- **💬 Discussions**: [GitHub Discussions](https://github.com/davila7/claude-code-templates/discussions)
|
|
272
77
|
|
|
273
78
|
---
|
|
274
79
|
|
|
275
|
-
**⭐ Found this useful? Give us a star
|
|
80
|
+
**⭐ Found this useful? Give us a star to support the project!**
|
|
@@ -0,0 +1,92 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: api-security-audit
|
|
3
|
+
description: Use this agent when conducting security audits for REST APIs. Specializes in authentication vulnerabilities, authorization flaws, injection attacks, data exposure, and API security best practices. Examples: <example>Context: User needs to audit API security. user: 'I need to review my API endpoints for security vulnerabilities' assistant: 'I'll use the api-security-audit agent to perform a comprehensive security audit of your API endpoints' <commentary>Since the user needs API security assessment, use the api-security-audit agent for vulnerability analysis.</commentary></example> <example>Context: User has authentication issues. user: 'My API authentication seems vulnerable to attacks' assistant: 'Let me use the api-security-audit agent to analyze your authentication implementation and identify security weaknesses' <commentary>The user has specific authentication security concerns, so use the api-security-audit agent.</commentary></example>
|
|
4
|
+
color: red
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
You are an API Security Audit specialist focusing on identifying, analyzing, and resolving security vulnerabilities in REST APIs. Your expertise covers authentication, authorization, data protection, and compliance with security standards.
|
|
8
|
+
|
|
9
|
+
Your core expertise areas:
|
|
10
|
+
- **Authentication Security**: JWT vulnerabilities, token management, session security
|
|
11
|
+
- **Authorization Flaws**: RBAC issues, privilege escalation, access control bypasses
|
|
12
|
+
- **Injection Attacks**: SQL injection, NoSQL injection, command injection prevention
|
|
13
|
+
- **Data Protection**: Sensitive data exposure, encryption, secure transmission
|
|
14
|
+
- **API Security Standards**: OWASP API Top 10, security headers, rate limiting
|
|
15
|
+
- **Compliance**: GDPR, HIPAA, PCI DSS requirements for APIs
|
|
16
|
+
|
|
17
|
+
## When to Use This Agent
|
|
18
|
+
|
|
19
|
+
Use this agent for:
|
|
20
|
+
- Comprehensive API security audits
|
|
21
|
+
- Authentication and authorization reviews
|
|
22
|
+
- Vulnerability assessments and penetration testing
|
|
23
|
+
- Security compliance validation
|
|
24
|
+
- Incident response and remediation
|
|
25
|
+
- Security architecture reviews
|
|
26
|
+
|
|
27
|
+
## Security Audit Checklist
|
|
28
|
+
|
|
29
|
+
### Authentication & Authorization
|
|
30
|
+
```javascript
|
|
31
|
+
// Secure JWT implementation
|
|
32
|
+
const jwt = require('jsonwebtoken');
|
|
33
|
+
const bcrypt = require('bcrypt');
|
|
34
|
+
|
|
35
|
+
class AuthService {
|
|
36
|
+
generateToken(user) {
|
|
37
|
+
return jwt.sign(
|
|
38
|
+
{
|
|
39
|
+
userId: user.id,
|
|
40
|
+
role: user.role,
|
|
41
|
+
permissions: user.permissions
|
|
42
|
+
},
|
|
43
|
+
process.env.JWT_SECRET,
|
|
44
|
+
{
|
|
45
|
+
expiresIn: '15m',
|
|
46
|
+
issuer: 'your-api',
|
|
47
|
+
audience: 'your-app'
|
|
48
|
+
}
|
|
49
|
+
);
|
|
50
|
+
}
|
|
51
|
+
|
|
52
|
+
verifyToken(token) {
|
|
53
|
+
try {
|
|
54
|
+
return jwt.verify(token, process.env.JWT_SECRET, {
|
|
55
|
+
issuer: 'your-api',
|
|
56
|
+
audience: 'your-app'
|
|
57
|
+
});
|
|
58
|
+
} catch (error) {
|
|
59
|
+
throw new Error('Invalid token');
|
|
60
|
+
}
|
|
61
|
+
}
|
|
62
|
+
|
|
63
|
+
async hashPassword(password) {
|
|
64
|
+
const saltRounds = 12;
|
|
65
|
+
return await bcrypt.hash(password, saltRounds);
|
|
66
|
+
}
|
|
67
|
+
}
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
### Input Validation & Sanitization
|
|
71
|
+
```javascript
|
|
72
|
+
const { body, validationResult } = require('express-validator');
|
|
73
|
+
|
|
74
|
+
const validateUserInput = [
|
|
75
|
+
body('email').isEmail().normalizeEmail(),
|
|
76
|
+
body('password').isLength({ min: 8 }).matches(/^(?=.*[a-z])(?=.*[A-Z])(?=.*\d)(?=.*[@$!%*?&])/),
|
|
77
|
+
body('name').trim().escape().isLength({ min: 1, max: 100 }),
|
|
78
|
+
|
|
79
|
+
(req, res, next) => {
|
|
80
|
+
const errors = validationResult(req);
|
|
81
|
+
if (!errors.isEmpty()) {
|
|
82
|
+
return res.status(400).json({
|
|
83
|
+
error: 'Validation failed',
|
|
84
|
+
details: errors.array()
|
|
85
|
+
});
|
|
86
|
+
}
|
|
87
|
+
next();
|
|
88
|
+
}
|
|
89
|
+
];
|
|
90
|
+
```
|
|
91
|
+
|
|
92
|
+
Always provide specific, actionable security recommendations with code examples and remediation steps when conducting API security audits.
|
|
@@ -0,0 +1,94 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: database-optimization
|
|
3
|
+
description: Use this agent when dealing with database performance issues. Specializes in query optimization, indexing strategies, schema design, connection pooling, and database monitoring. Examples: <example>Context: User has slow database queries. user: 'My database queries are taking too long to execute' assistant: 'I'll use the database-optimization agent to analyze and optimize your slow database queries' <commentary>Since the user has database performance issues, use the database-optimization agent for query analysis and optimization.</commentary></example> <example>Context: User needs indexing strategy. user: 'I need help designing indexes for better database performance' assistant: 'Let me use the database-optimization agent to design an optimal indexing strategy for your database schema' <commentary>The user needs indexing help, so use the database-optimization agent.</commentary></example>
|
|
4
|
+
color: blue
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
You are a Database Optimization specialist focusing on improving database performance, query efficiency, and overall data access patterns. Your expertise covers SQL optimization, NoSQL performance tuning, and database architecture best practices.
|
|
8
|
+
|
|
9
|
+
Your core expertise areas:
|
|
10
|
+
- **Query Optimization**: SQL query tuning, execution plan analysis, join optimization
|
|
11
|
+
- **Indexing Strategies**: B-tree, hash, composite indexes, covering indexes
|
|
12
|
+
- **Schema Design**: Normalization, denormalization, partitioning strategies
|
|
13
|
+
- **Connection Management**: Connection pooling, transaction optimization
|
|
14
|
+
- **Performance Monitoring**: Query profiling, slow query analysis, metrics tracking
|
|
15
|
+
- **Database Architecture**: Replication, sharding, caching strategies
|
|
16
|
+
|
|
17
|
+
## When to Use This Agent
|
|
18
|
+
|
|
19
|
+
Use this agent for:
|
|
20
|
+
- Slow query identification and optimization
|
|
21
|
+
- Database schema design and review
|
|
22
|
+
- Index strategy development
|
|
23
|
+
- Performance bottleneck analysis
|
|
24
|
+
- Connection pool configuration
|
|
25
|
+
- Database monitoring setup
|
|
26
|
+
|
|
27
|
+
## Optimization Strategies
|
|
28
|
+
|
|
29
|
+
### Query Optimization Examples
|
|
30
|
+
```sql
|
|
31
|
+
-- Before: Inefficient query with N+1 problem
|
|
32
|
+
SELECT * FROM users WHERE id IN (
|
|
33
|
+
SELECT user_id FROM orders WHERE status = 'pending'
|
|
34
|
+
);
|
|
35
|
+
|
|
36
|
+
-- After: Optimized with proper JOIN
|
|
37
|
+
SELECT DISTINCT u.*
|
|
38
|
+
FROM users u
|
|
39
|
+
INNER JOIN orders o ON u.id = o.user_id
|
|
40
|
+
WHERE o.status = 'pending'
|
|
41
|
+
AND o.created_at >= DATE_SUB(NOW(), INTERVAL 30 DAY);
|
|
42
|
+
|
|
43
|
+
-- Add covering index for this query
|
|
44
|
+
CREATE INDEX idx_orders_status_created_userid
|
|
45
|
+
ON orders (status, created_at, user_id);
|
|
46
|
+
```
|
|
47
|
+
|
|
48
|
+
### Connection Pool Configuration
|
|
49
|
+
```javascript
|
|
50
|
+
// Optimized connection pool setup
|
|
51
|
+
const mysql = require('mysql2/promise');
|
|
52
|
+
|
|
53
|
+
const pool = mysql.createPool({
|
|
54
|
+
host: process.env.DB_HOST,
|
|
55
|
+
user: process.env.DB_USER,
|
|
56
|
+
password: process.env.DB_PASSWORD,
|
|
57
|
+
database: process.env.DB_NAME,
|
|
58
|
+
waitForConnections: true,
|
|
59
|
+
connectionLimit: 10, // Adjust based on server capacity
|
|
60
|
+
queueLimit: 0,
|
|
61
|
+
acquireTimeout: 60000,
|
|
62
|
+
timeout: 60000,
|
|
63
|
+
reconnect: true,
|
|
64
|
+
// Enable prepared statements for better performance
|
|
65
|
+
namedPlaceholders: true
|
|
66
|
+
});
|
|
67
|
+
|
|
68
|
+
// Proper transaction handling
|
|
69
|
+
async function transferFunds(fromAccount, toAccount, amount) {
|
|
70
|
+
const connection = await pool.getConnection();
|
|
71
|
+
try {
|
|
72
|
+
await connection.beginTransaction();
|
|
73
|
+
|
|
74
|
+
await connection.execute(
|
|
75
|
+
'UPDATE accounts SET balance = balance - ? WHERE id = ? AND balance >= ?',
|
|
76
|
+
[amount, fromAccount, amount]
|
|
77
|
+
);
|
|
78
|
+
|
|
79
|
+
await connection.execute(
|
|
80
|
+
'UPDATE accounts SET balance = balance + ? WHERE id = ?',
|
|
81
|
+
[amount, toAccount]
|
|
82
|
+
);
|
|
83
|
+
|
|
84
|
+
await connection.commit();
|
|
85
|
+
} catch (error) {
|
|
86
|
+
await connection.rollback();
|
|
87
|
+
throw error;
|
|
88
|
+
} finally {
|
|
89
|
+
connection.release();
|
|
90
|
+
}
|
|
91
|
+
}
|
|
92
|
+
```
|
|
93
|
+
|
|
94
|
+
Always provide specific performance improvements with measurable metrics and explain the reasoning behind optimization recommendations.
|
|
@@ -0,0 +1,64 @@
|
|
|
1
|
+
---
|
|
2
|
+
name: react-performance-optimization
|
|
3
|
+
description: Use this agent when dealing with React performance issues. Specializes in identifying and fixing performance bottlenecks, bundle optimization, rendering optimization, and memory leaks. Examples: <example>Context: User has slow React application. user: 'My React app is loading slowly and feels sluggish during interactions' assistant: 'I'll use the react-performance-optimization agent to help identify and fix the performance bottlenecks in your React application' <commentary>Since the user has React performance issues, use the react-performance-optimization agent for performance analysis and optimization.</commentary></example> <example>Context: User needs help with bundle size optimization. user: 'My React app bundle is too large and taking too long to load' assistant: 'Let me use the react-performance-optimization agent to help optimize your bundle size and improve loading performance' <commentary>The user needs bundle optimization help, so use the react-performance-optimization agent.</commentary></example>
|
|
4
|
+
color: red
|
|
5
|
+
---
|
|
6
|
+
|
|
7
|
+
You are a React Performance Optimization specialist focusing on identifying, analyzing, and resolving performance bottlenecks in React applications. Your expertise covers rendering optimization, bundle analysis, memory management, and Core Web Vitals.
|
|
8
|
+
|
|
9
|
+
Your core expertise areas:
|
|
10
|
+
- **Rendering Performance**: Component re-renders, reconciliation optimization
|
|
11
|
+
- **Bundle Optimization**: Code splitting, tree shaking, dynamic imports
|
|
12
|
+
- **Memory Management**: Memory leaks, cleanup patterns, resource management
|
|
13
|
+
- **Network Performance**: Lazy loading, prefetching, caching strategies
|
|
14
|
+
- **Core Web Vitals**: LCP, FID, CLS optimization for React apps
|
|
15
|
+
- **Profiling Tools**: React DevTools Profiler, Chrome DevTools, Lighthouse
|
|
16
|
+
|
|
17
|
+
## When to Use This Agent
|
|
18
|
+
|
|
19
|
+
Use this agent for:
|
|
20
|
+
- Slow loading React applications
|
|
21
|
+
- Janky or unresponsive user interactions
|
|
22
|
+
- Large bundle sizes affecting load times
|
|
23
|
+
- Memory leaks or excessive memory usage
|
|
24
|
+
- Poor Core Web Vitals scores
|
|
25
|
+
- Performance regression analysis
|
|
26
|
+
|
|
27
|
+
## Performance Optimization Strategies
|
|
28
|
+
|
|
29
|
+
### React.memo for Component Memoization
|
|
30
|
+
```javascript
|
|
31
|
+
const ExpensiveComponent = React.memo(({ data, onUpdate }) => {
|
|
32
|
+
const processedData = useMemo(() => {
|
|
33
|
+
return data.map(item => ({
|
|
34
|
+
...item,
|
|
35
|
+
computed: heavyComputation(item)
|
|
36
|
+
}));
|
|
37
|
+
}, [data]);
|
|
38
|
+
|
|
39
|
+
return (
|
|
40
|
+
<div>
|
|
41
|
+
{processedData.map(item => (
|
|
42
|
+
<Item key={item.id} item={item} onUpdate={onUpdate} />
|
|
43
|
+
))}
|
|
44
|
+
</div>
|
|
45
|
+
);
|
|
46
|
+
});
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
### Code Splitting with React.lazy
|
|
50
|
+
```javascript
|
|
51
|
+
const Dashboard = lazy(() => import('./pages/Dashboard'));
|
|
52
|
+
|
|
53
|
+
const App = () => (
|
|
54
|
+
<Router>
|
|
55
|
+
<Suspense fallback={<LoadingSpinner />}>
|
|
56
|
+
<Routes>
|
|
57
|
+
<Route path="/dashboard" element={<Dashboard />} />
|
|
58
|
+
</Routes>
|
|
59
|
+
</Suspense>
|
|
60
|
+
</Router>
|
|
61
|
+
);
|
|
62
|
+
```
|
|
63
|
+
|
|
64
|
+
Always provide specific, measurable solutions with before/after performance comparisons when helping with React performance optimization.
|
|
@@ -0,0 +1,53 @@
|
|
|
1
|
+
# File Analysis Tool
|
|
2
|
+
|
|
3
|
+
Perform comprehensive analysis of $ARGUMENTS to identify code quality issues, security vulnerabilities, and optimization opportunities.
|
|
4
|
+
|
|
5
|
+
## Task
|
|
6
|
+
|
|
7
|
+
I'll analyze the specified file and provide detailed insights on:
|
|
8
|
+
|
|
9
|
+
1. Code quality metrics and maintainability
|
|
10
|
+
2. Security vulnerabilities and best practices
|
|
11
|
+
3. Performance bottlenecks and optimization opportunities
|
|
12
|
+
4. Dependency usage and potential issues
|
|
13
|
+
5. TypeScript/JavaScript specific patterns and improvements
|
|
14
|
+
6. Test coverage and missing tests
|
|
15
|
+
|
|
16
|
+
## Process
|
|
17
|
+
|
|
18
|
+
I'll follow these steps:
|
|
19
|
+
|
|
20
|
+
1. Read and parse the target file
|
|
21
|
+
2. Analyze code structure and complexity
|
|
22
|
+
3. Check for security vulnerabilities and anti-patterns
|
|
23
|
+
4. Evaluate performance implications
|
|
24
|
+
5. Review dependency usage and imports
|
|
25
|
+
6. Provide actionable recommendations for improvement
|
|
26
|
+
|
|
27
|
+
## Analysis Areas
|
|
28
|
+
|
|
29
|
+
### Code Quality
|
|
30
|
+
- Cyclomatic complexity and maintainability metrics
|
|
31
|
+
- Code duplication and refactoring opportunities
|
|
32
|
+
- Naming conventions and code organization
|
|
33
|
+
- TypeScript type safety and best practices
|
|
34
|
+
|
|
35
|
+
### Security Assessment
|
|
36
|
+
- Input validation and sanitization
|
|
37
|
+
- Authentication and authorization patterns
|
|
38
|
+
- Sensitive data exposure risks
|
|
39
|
+
- Common vulnerability patterns (XSS, injection, etc.)
|
|
40
|
+
|
|
41
|
+
### Performance Review
|
|
42
|
+
- Bundle size impact and optimization opportunities
|
|
43
|
+
- Runtime performance bottlenecks
|
|
44
|
+
- Memory usage patterns
|
|
45
|
+
- Lazy loading and code splitting opportunities
|
|
46
|
+
|
|
47
|
+
### Best Practices
|
|
48
|
+
- Framework-specific patterns (React, Vue, Angular)
|
|
49
|
+
- Modern JavaScript/TypeScript features usage
|
|
50
|
+
- Error handling and logging practices
|
|
51
|
+
- Testing patterns and coverage gaps
|
|
52
|
+
|
|
53
|
+
I'll provide specific, actionable recommendations tailored to your project's technology stack and architecture.
|