後端工程
後端工程
設計後端服務、資料存取及可靠的交易與事件流程。
magnus919 · 社群來源 · 程式設計與開發
來源狀態
可用來源
原始名稱: backend-engineering
原始作者: magnus919
這是第三方 Community Skill；2lus 收錄不代表已完整安全審計或保證安全。
資源類型
Skill
與類似 Skill 有什麼不同？
- API 設計
後端工程處理服務實作與交易邊界；API 設計處理公開契約與相容性。
來源描述的能力
這些是來源描述的可能操作，不代表 2lus 已授予權限或已測試。
尚未列出能力，請審查原始來源。
這個 Skill 是什麼？
將 API 契約落實為可維護的服務邏輯。
可以做什麼？何時適合使用？
- 拆分 controller 與服務責任
- 處理跨表交易及事件發布
- 讓新舊系統逐步並行遷移
如何使用
- 提供契約、資料模型與故障情境
- 定義授權、驗證與交易邊界
- 規劃資料存取、事件/outbox 與測試證據
使用前你需要準備
- 既有 endpoint 與資料模型
- 部署及相容限制
你可以替換：
請提供版本、來源資料、目標與限制。
環境與相依需求
- 既有 endpoint 與資料模型
- 部署及相容限制
使用範例與 Prompt
以下是 2lus 撰寫的示範需求；請替換為你有權處理的檔案與專案，不代表已執行或保證結果。
入門
為新增訂單 API 劃分 controller、service 與 repository 責任。
實務
設計扣庫存與建立訂單的交易邊界及失敗恢復。
進階
規劃舊系統遷移到事件流程的 outbox、冪等消費與回滾步驟。
實用提醒
- 把不可分割的業務變更放進同一交易；跨系統事件需重試與冪等。
限制與注意事項
- 架構建議不能取代執行環境中的負載與故障測試。
安全注意事項
- 在服務端檢查身分與資源所有權，避免信任 client userId。
使用與設定
此條目不提供已確認的通用安裝指令；請依官方文件與 Agent 版本操作。
支援平台
未確認特定 Agent 相容性
來源與授權
來源查核日期（非安全認證）: 2026-10-01
MIT
原始來源 ↗ 官方文件 ↗相關 Skills
使用第三方 Skill 前，請先檢查來源、權限與執行內容。安裝指令只供查看與複製，不會由 2lus 執行。
2lus AI Skills Library 提供 Skill 的整理與使用導覽。第三方 Skill 的內容、授權與可用性以原始來源為準。使用或安裝前，請自行確認其權限與執行內容。
Backend Engineering
Design backend services, data access, and reliable transaction and event flows.
magnus919 · Community source · Programming & Development
Source status
Active source
Original name: backend-engineering
Original author: magnus919
This is a third-party community skill. Inclusion by 2lus is not a complete security audit or safety guarantee.
Resource type
Skill
How is this different from similar skills?
- API Design
Backend Engineering handles service implementation and transaction boundaries; API Design handles public contracts and compatibility.
Documented capabilities
These are operations described upstream, not permissions granted or tested by 2lus.
Capabilities not declared here; review the original source.
What is this skill?
Implement an API contract as maintainable service behavior.
Use cases and when to use it
- Separate controller and service responsibilities
- Handle cross-table transactions and event publication
- Migrate old and new services side by side
How to use it
- Provide contracts, models, and failure cases
- Define authorization, validation, and transaction boundaries
- Plan data access, event/outbox flow, and test evidence
What you need
- Existing endpoints and data models
- Deployment and compatibility constraints
You can replace:
Provide versions, source material, goals, and constraints.
Environment and dependencies
- Existing endpoints and data models
- Deployment and compatibility constraints
Usage and prompt examples
These example requests were written by 2lus. Substitute files and projects you may use; examples are not executed results or guarantees.
Beginner
Separate controller, service, and repository responsibilities for a new order API.
Practical
Design transaction boundaries and recovery for inventory deduction and order creation.
Advanced
Plan outbox publication, idempotent consumption, and rollback for migration to events.
Tips
- Keep indivisible business changes in one transaction; retry and deduplicate cross-system events.
Limitations
- Architecture advice cannot replace load and failure testing in the target environment.
Security notes
- Check identity and resource ownership server-side; do not trust client-supplied user IDs.
Usage and setup
No verified universal installation command is provided for this entry. Follow the official documentation for your agent version.
Supported agents
Specific agent compatibility unknown
Sources and license
Source check date (not a safety certification): 2026-10-01
MIT
Original source ↗ Documentation ↗Related skills
Before using a third-party skill, review its source, permissions and executable content. Commands are for viewing and copying only; 2lus does not execute them.
2lus AI Skills Library provides curated educational guides. Third-party content, licenses and availability are governed by their original sources. Review permissions and executable content before use or installation.