Agent skill
teamventure-architecture-migration
Use when refactoring TeamVenture domains/architecture; enforces migration order (Planning→Authorization→Identity→Infrastructure) and preferred steps (split classes before moving packages).
Install this agent skill to your Project
npx add-skill https://github.com/majiayu000/claude-skill-registry/tree/main/skills/data/teamventure-architecture-migration
SKILL.md
TeamVenture Architecture Migration (Order + Guardrails)
Migration order (domain/context)
- Planning (core): Plans + review collaboration (memberships, itinerary revisions, itinerary suggestions)
- Authorization (supporting): Policy/permission checks (no ownership of business fact tables)
- Identity (supporting): Auth/login/session/user profile
- Infrastructure (supporting): Read/write routing, cache/MQ wiring, monitoring hardening
Refactor order inside a domain
- Split classes first (semantic/CQRS refactor), keep packages stable
- Example:
*Service→*QueryService+*CommandService
- Example:
- Move packages second (mechanical refactor)
- Move in small batches; keep public API/HTTP routes stable
CQRS + read/write split rule
- Query methods must be annotated with
@Transactional(readOnly = true)to route to slave - Command methods must use default or explicit
@Transactionalto route to master - Permission checks that must be immediately consistent should read from master (or cache with strict invalidation)
Execution checklist (per step)
- Make change in smallest viable slice
- Run Java tests (
mvn test) and fix regressions introduced by the slice - Avoid broad renames and unrelated refactors
Recommended Agent Skills
Expand your agent's capabilities with these related and highly-rated skills.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
agent-ops-spec
Manage specification documents in .agent/specs/. Use when user provides requirements, acceptance criteria, or feature descriptions that need to be tracked and validated against implementation.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-testing
Test strategy, execution, and coverage analysis. Use when designing tests, running test suites, or analyzing test results beyond baseline checks.
agent-ops-state
Maintain .agent state files. Use at session start, after meaningful steps, and before concluding: read/update constitution/memory/focus/issues/baseline consistently.
Didn't find tool you were looking for?