이현우
Community@LeeHyunWoo02
Convention skills defining DDD hexagonal architecture, JPA persistence, Redis caching, and Spring Batch seed data rules for the smash(ProvinceHow) backend.
Agent Skills by 이현우
Showing 6 vetted skills indexed across 1 GitHub repositories.
architecture-conventions
Defines DDD hexagonal architecture rules for the ProvinceHow Spring Boot backend.
redis-conventions
Defines Redis caching conventions for DDD hexagonal Spring Boot architecture with ports and adapters.
persistence-conventions
Defines JPA persistence conventions for a DDD hexagonal Spring Boot backend.
global-conventions
Defines naming, exception, DTO, and logging conventions for a DDD hexagonal Spring Boot codebase.
seed-data
Prepare, validate, and reload seed CSV files for Spring Batch database initialization jobs.
backend-conventions
Defines DDD hexagonal architecture workflows and layered JUnit5 testing conventions for Spring Boot backends.
Frequently Asked Questions About 이현우
FAQPage SchemaWhat tasks can I perform using LeeHyunWoo02's skills?▼
You can place new classes in the correct hexagonal layer, design ports and adapters, separate domain models from JPA entities, define Redis key naming and TTL rules, write DomainException/ErrorCode-based exceptions, and prepare or re-load seed CSV data through Spring Batch Seed Jobs.
Who are these skills designed for?▼
Backend engineers working on the smash(ProvinceHow) service who follow DDD hexagonal architecture. They suit developers adding features, APIs, repositories, caches, or seed batches who must comply with the project's layered conventions and ubiquitous language.
How do the skills work together in practice?▼
architecture-conventions governs layer placement and context boundaries; backend-conventions covers use cases, domain models, and JUnit5/Mockito tests; persistence-conventions handles JPA mapping and transactions; redis-conventions covers cache ports; global-conventions defines naming, DTOs, and exceptions.
What are the prerequisites for applying these skills?▼
Familiarity with Spring Boot, Spring Batch, JPA, and Redis is assumed, since the rules reference RepositoryAdapter/JpaMapper patterns, RedisTemplate, dual-DataSource @Transactional boundaries, and BatchGuard/SEED_VERSION re-execution control within the smash(ProvinceHow) codebase.
How is seed data verified and reloaded?▼
Seed CSVs under data/ are loaded by 8 @Order-sequenced Spring Batch Seed Jobs respecting FK dependencies. BatchGuard and SEED_VERSION prevent unwanted re-runs, and scripts/verify-seed.sh produces a report whose failure types map to documented remediation steps.