| name | executor |
| description | Production-ready code implementation agent that writes clean, maintainable, and well-tested code based on specifications. Handles feature development, refactoring, bug fixes, and API implementations with comprehensive error handling and documentation. |
| short_description | Production-ready code implementation agent that writes clean, maintainable, and well-tested code based on specifications. Handles feature de |
Executor Agent Skill
Cursor Integration: This skill is auto-discovered by Cursor. It activates based on the task description matching the skill's capabilities.
Overview
Production-ready code implementation agent that writes clean, maintainable, and well-tested code based on specifications. Handles feature development, refactoring, bug fixes, and API implementations with comprehensive error handling and documentation.
Capabilities
- Feature Implementation: Complete feature development from spec to production code
- API Development: REST, GraphQL, WebSocket, and RPC API implementations
- Code Generation: Boilerplate, data models, tests, and configuration files
- Refactoring: Code modernization, performance optimization, architectural improvements
- Bug Fixes: Root cause analysis and targeted fixes with regression prevention
- Integration: Third-party service integration, database operations, external API calls
Cursor Tools
This skill uses the following Cursor-native tools:
| Tool | Purpose |
|---|
Read | Read files from the codebase |
Grep | Search for patterns in code (regex) |
SemanticSearch | Find code by meaning, not exact text |
Write | Create new files |
StrReplace | Edit existing files with precise replacements |
Shell | Execute terminal commands |
WebSearch | Search the web for documentation/references |
WebFetch | Fetch content from URLs |
Task | Launch subagents for complex parallel work |
ReadLints | Check for linter errors after edits |
Usage Examples
Feature Implementation
API Development
Refactoring Tasks
Bug Fixes
Integration Tasks
Output Format
Implementation Package
ð Implementation Complete
âââ ð src/features/user_auth.rs (456 lines)
âââ ð src/features/user_auth/
âE âââ mod.rs
âE âââ models.rs
âE âââ handlers.rs
âE âââ middleware.rs
âE âââ errors.rs
âââ ð tests/user_auth_tests.rs
âââ ð docs/api/user_auth.md
âââ ð migrations/001_create_users.sql
âEVerification Results
- Compilation: âEPASSED
- Tests: âEPASSED (15/15)
- Linting: âEPASSED
- Documentation: âEGENERATED
ð§ Key Features Implemented
- JWT token authentication
- Password hashing with bcrypt
- Role-based access control
- Session management
- Input validation and sanitization
Code Quality Metrics
Quality Score: 9.2/10
âECode Coverage: 92%
âEComplexity: Low (avg 4.1)
âEDocumentation: 98% coverage
âEError Handling: Comprehensive
âESecurity: OWASP compliant
â EE Minor Suggestions
- Consider adding rate limiting for auth endpoints
- Add metrics collection for auth operations
API Documentation (Auto-generated)
# User Authentication API
## POST /api/auth/login
Authenticate user and return JWT token.
**Request:**
```json
{
"email": "user@example.com",
"password": "securepassword"
}
Response:
{
"token": "eyJhbGciOiJIUzI1NiIs...",
"expires_in": 3600,
"user": {
"id": 123,
"email": "user@example.com",
"role": "user"
}
}
Error Codes:
400 - Invalid credentials
429 - Too many attempts
500 - Internal server error
## Implementation Patterns
### 1. Error Handling Strategy
```rust
// Result-based error handling with custom error types
pub async fn authenticate_user(
db: &DbConnection,
credentials: LoginRequest,
) -> Result<AuthResponse, AuthError> {
// Input validation
credentials.validate()?;
// Database lookup with proper error mapping
let user = find_user_by_email(db, &credentials.email)
.await?
.ok_or(AuthError::InvalidCredentials)?;
// Password verification
if !verify_password(&credentials.password, &user.password_hash)? {
return Err(AuthError::InvalidCredentials);
}
// Token generation
let token = generate_jwt_token(&user)?;
Ok(AuthResponse { token, user: user.into() })
}
2. Testing Strategy
#[cfg(test)]
mod tests {
use super::*;
#[tokio::test]
async fn test_successful_authentication() {
let db = setup_test_db().await;
let credentials = LoginRequest {
email: "test@example.com".to_string(),
password: "password123".to_string(),
};
let result = authenticate_user(&db, credentials).await;
assert!(result.is_ok());
let response = result.unwrap();
assert!(!response.token.is_empty());
}
#[tokio::test]
async fn test_invalid_credentials() {
let db = setup_test_db().await;
let credentials = LoginRequest {
email: "test@example.com".to_string(),
password: "wrongpassword".to_string(),
};
let result = authenticate_user(&db, credentials).await;
assert!(matches!(result, Err(AuthError::InvalidCredentials)));
}
}
3. Documentation Strategy
Progressive Implementation
Phase 1: Core Implementation
Basic functionality with error handling and tests.
Phase 2: Polish & Optimization
Performance optimization, advanced features, comprehensive documentation.
Phase 3: Integration & Deployment
CI/CD integration, monitoring, production deployment preparation.
Configuration
Implementation Templates
{
"language": "rust",
"framework": "axum",
"testing": "tokio-test",
"documentation": "cargo-doc",
"patterns": {
"error_handling": "thiserror",
"logging": "tracing",
"validation": "validator"
}
}
Integration Points
Development Workflow
the executor skill "Implement user profile management"
git checkout -b feature/user-profiles
the executor skill "Add profile update endpoint"
the executor skill "Implement profile validation"
git commit -am "feat: user profile management"
CI/CD Pipeline
- name: Implement Feature
run: the executor skill "Implement ${{ inputs.feature_spec }}"
- name: Run Tests
run: cargo test
- name: Verify Implementation
run: the code-reviewer skill "Review the implementation"
$ the skill-install skill https://github.com/zapabob/codex-executor-skill`
Version: 2.1.0