Skip to content
Back to skills

Implementing Code

ASecurity

Write clean, efficient, maintainable code. Use when implementing features, writing functions, or creating new modules. Covers SOLID principles, error handling, and code organization.

  • 34 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 22, 2026
toolsgojavabashspringawstestingsecurityperformance

Security analysis

A100/100

Scanned September 22, 2026

npx -y skills add nguyenhuuca/assessment --skill implementing-code --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Implementing Code?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Implementing Code
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/nguyenhuuca-implementing-code/badge)](https://www.skillsdirectory.com/skills/nguyenhuuca-implementing-code)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: implementing-code
description: Write clean, efficient, maintainable code. Use when implementing features, writing functions, or creating new modules. Covers SOLID principles, error handling, and code organization.
allowed-tools: Read, Write, Edit, Bash, Glob, Grep
---

# Implementing Code

## Workflows

- [ ] **Security Check**: Injection flaws, auth issues, sensitive data exposure
- [ ] **Performance Check**: N+1 queries, memory leaks, inefficient algorithms
- [ ] **Readability Check**: SOLID principles, naming conventions, comments
- [ ] **Testing Check**: Edge cases, error paths, happy paths

## Feedback Loops

1. Implement feature or fix
2. Run local tests (unit/integration)
3. Run linter/formatter
4. If failure, fix and repeat

## Reference Implementation

### SOLID Compliant Class (Java + Spring Boot)

```java
// Abstraction (Interface Segregation)
public interface Logger {
    void log(String message);
}

public interface UserRepository extends JpaRepository<User, Long> {
    boolean existsByEmail(String email);
}

// Domain Entity
@Entity
@Data
@Builder
@NoArgsConstructor
@AllArgsConstructor
public class User {
    @Id
    @GeneratedValue(strategy = GenerationType.IDENTITY)
    private Long id;

    @Email(message = "Invalid email format")
    @NotBlank(message = "Email is required")
    private String email;

    @Builder.Default
    private Instant createdAt = Instant.now();
}

// Implementation (Single Responsibility)
@Service
@Transactional
public class UserService {
    private final UserRepository userRepository;
    private final Logger logger;

    public UserService(UserRepository userRepository, Logger logger) {
        this.userRepository = userRepository;
        this.logger = logger;
    }

    public User registerUser(String email) {
        // Validation
        if (!email.contains("@")) {
            throw new IllegalArgumentException("Invalid email format");
        }

        if (userRepository.existsByEmail(email)) {
            throw new DuplicateEmailException("Email already exists");
        }

        // Business logic
        User user = User.builder()
            .email(email)
            .build();

        User saved = userRepository.save(user);
        logger.log("User registered: " + saved.getId());

        return saved;
    }
}
```

## Code Review Checklist

- [ ] No hardcoded secrets or credentials
- [ ] Input validation on all external data
- [ ] Proper error handling with meaningful messages
- [ ] No N+1 query patterns
- [ ] Functions follow single responsibility principle
- [ ] Dependencies injected, not instantiated inline
- [ ] Tests cover happy path and edge cases

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…