implementing-code
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
- Implement feature or fix
- Run local tests (unit/integration)
- Run linter/formatter
- If failure, fix and repeat
Reference Implementation
SOLID Compliant Class (Java + Spring Boot)
More from nguyenhuuca/assessment
compliance
Ensure regulatory compliance. Use when implementing GDPR, HIPAA, PCI-DSS, or SOC2 requirements. Covers compliance frameworks and controls.
19requirements-analysis
Analyze and refine product requirements. Use when clarifying scope, identifying gaps, or validating requirements. Covers requirement types and analysis techniques.
16identity-access
Implement identity and access management. Use when designing authentication, authorization, or user management. Covers OAuth2, OIDC, and RBAC.
13security-review
Conduct security code reviews. Use when reviewing code for vulnerabilities, assessing security posture, or auditing applications. Covers security review checklist.
13execution-roadmaps
Create execution roadmaps for projects. Use when planning multi-phase projects or feature rollouts. Covers phased delivery and milestone planning.
12cloud-native-patterns
Apply cloud-native architecture patterns. Use when designing for scalability, resilience, or cloud deployment. Covers microservices, containers, and distributed systems.
12