Multica Backend Impl
后端实现:读 JIRA/Confluence/架构设计,TDD 驱动 API 与服务端编码。用于 @BackendDev 契约先行、单元测试、集成验证。
Install
npx skills add it235/multica-best-practices --skill multica-backend-implgit clone --depth 1 https://github.com/it235/multica-best-practices.git /tmp/multica-best-practices
mkdir -p ~/.claude/skills
cp -r /tmp/multica-best-practices/templates/zh_CN/skills/backend/multica-backend-impl ~/.claude/skills/multica-backend-implPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Backend Implementation ## Purpose 在已批准的技术设计与 Issue 范围内,**契约先行 + TDD** 完成后端实现。 > 与 `multica-artifact-backend` 分工:**backend-impl 管怎么读上游、怎么写代码与测试;artifact-backend 管 API 契约文档规范与 Confluence 落地**。 ## Platform 协作 | Platform skill | 本 skill 用途 | | --- | --- | | `multica-platform-jira` | 读 Issue / AC(经 Issue Hub 或 JIRA URL) | | `multica-platform-confluence` | 读 PRD / 架构设计(`fetch_page.py`) | 发布契约走 `multica-artifact-backend` → platform skill;本 skill 不直接写 REST。 ## 开工前:读上游(必做) | 顺序 | 来源 | 方式 | | --- | --- | --- | | 1 | Issue / 验收标准 | `multica-platform-jira` → `get-issue`;含 **`linked_issues`** | | 2 | **关联 JIRA**(Relates/依赖等) | `get_issue.py --with-linked` → 必读关联的 Confluence/Figma(见 `upstream-read.md`) | | 3 | PRD / 需求正文 | JIRA 解析 Confluence → `fetch_page.py` | | 4 | 架构设计 | Leader 派活链接或 JIRA 描述中的设计链接 → `fetch_page.py` | | 5 | 现有代码 | codegraph / 局部阅读,遵循项目约定 | 信息不足 → **BLOCKED**,写入待确认项,不猜接口形状。 ## G2 前:单元测试(硬门禁) **merge 到 deploy branch 之前**,必须在本地(或项目标准 dev 容器)跑通 **全部** 单元测试: ```text 1. 跑项目约定的 unit test 命令(如 mvn test / npm test / pytest tests/unit) 2. 必须 0 failure;既有测试不得因本次改动失败(无退步) 3. 新增/变更 API 须有对应单元测试(Red-Green-Refactor) 4. 失败 → 自行修复后再跑,直至全绿 5. 仅当本地无法跑(缺依赖/缺硬件)→ BLOCKED 列环境缺口,不得 push 后「等 CI 再看」 ``` **禁止**:把单元测试失败留给 Jenkins/CICD 才发现;禁止为通过而删除或 skip 既有测试(除非 Architect/Leader 书面砍 scope)。 CI 是 **二次确认**,不是第一次跑单测的地方。 ## TDD 流程(核心)
Details
- Skill name
multica-backend-impl- Repository
- it235/multica-best-practices
- Path
templates/zh_CN/skills/backend/multica-backend-impl/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Backend Impl skill do?
后端实现:读 JIRA/Confluence/架构设计,TDD 驱动 API 与服务端编码。用于 @BackendDev 契约先行、单元测试、集成验证。
How do I install the Multica Backend Impl skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-backend-impl. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Backend Impl popular?
It lives in it235/multica-best-practices, which has 279 GitHub stars and 33 forks.
Related skills
Multica Artifact Architect
279it235/multica-best-practices
Land technical design artifacts to the code repo or knowledge platform (default Git repo / Confluence). Used by @Architect to upload technical design for downstream implementation and test consumption. Swappable platform.
Multica Artifact Architect
279it235/multica-best-practices
架构师产物薄编排:校验设计草稿规范,落地时只调 multica-platform-confluence + multica-platform-jira。用于 @Architect 发布设计文档。
Multica Artifact Backend
279it235/multica-best-practices
Land API contract artifacts to the API collaboration platform (default Apifox). Used by @BackendDev to upload API contract for downstream frontend / test consumption. Swappable platform.
Multica Manage Skills
279it235/multica-best-practices
Skill library management—batch import/export and bind SKILL.md to the Multica skill library; operates on the templates/<lang>/skills directory. The preferred mount for @Leader.
Multica Backend Impl
279it235/multica-best-practices
Backend implementation skill—API / data model / business logic coding conventions and acceptance checklist; the preferred mount for @BackendDev.
Multica Platform Apifox
279it235/multica-best-practices
Apifox integration—read API contracts/scenarios, and run/supplement test scenarios. Credentials and CLI are only looked up here.
Browse the most popular Claude skills, all software development skills, or write your own with the skills generator.