From bill-java-developer
Use when user needs technical design advice, architecture planning, or implementation strategy for Spring Boot projects. Produces actionable Todo List.
How this skill is triggered — by the user, by Claude, or both
Slash command
/bill-java-developer:design-solutionsonnetThis skill is limited to the following tools:
The summary Claude sees in its skill listing — used to decide when to auto-load this skill
As a senior Spring Boot developer (15+ years experience), analyze requirements and provide a complete technical solution.
As a senior Spring Boot developer (15+ years experience), analyze requirements and provide a complete technical solution.
List questions before designing:
Produce an actionable Todo List with phases.
@Transactional on service, @ControllerAdvice for exceptionsIMPORTANT: All output must be in Traditional Chinese (繁體中文)
## 需求理解
### 功能說明
[用自己的話描述需求,確認理解正確]
### 澄清問題
1. [問題 1]
---
## 技術建議
### 建議方案
[描述建議的技術方案]
### 為什麼選擇這個方案
- 優點 1
### 替代方案(如果有)
[其他可行方案及其優缺點]
---
## 架構設計
### 系統架構
[描述整體架構]
### 資料模型
[描述需要的 Entity/DTO]
### API 設計
[描述 API endpoint]
---
## 實作 Todo List
### Phase 1: 基礎建設
- [ ] Step 1.1: [具體任務]
### Phase 2: 核心功能
- [ ] Step 2.1: [具體任務]
### Phase 3: 整合測試
- [ ] Step 3.1: [具體任務]
---
## 注意事項
### 潛在風險
1. [風險及緩解方案]
### 邊界情況
1. [邊界情況及處理方式]
### 效能考量
### 安全性考量
---
## 預估工時
| 階段 | 預估時間 | 說明 |
|------|----------|------|
| **總計** | **X 天** | |
npx claudepluginhub xinqilin/claude-dev-toolkit-marketplace --plugin bill-java-developerGuides Domain-Driven Design for complex business systems: defines bounded contexts, structures domain models, designs aggregates/entities/value objects, chooses monolith vs microservices.
Guides architectural thinking through requirements, high-level design, deep dives, and trade-off analysis. Use for system design, ADRs, and API planning before writing docs.
Designs system architecture and high-level technical strategy. Use for new systems or subsystems, major refactors, technology selections, system boundaries, and long-term decisions with broad impact.