Multica Artifact Architect
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.
Install
npx skills add it235/multica-best-practices --skill multica-artifact-architectgit 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/en_US/skills/architect/multica-artifact-architect ~/.claude/skills/multica-artifact-architectPersonal skills live in ~/.claude/skills. Use .claude/skills in a project folder to share a skill with your team.
From the SKILL.md
# Artifact · Technical Design Sync ## Purpose Land technical design docs to the team's unified technical-doc location and let downstream retrieve them via a stable reference. > This skill decouples "platform integration" from "role prompt": the role prompt only says "produce technical design", not which platform. Changing companies means editing only this skill, not the @Architect prompt. ## Default platform: Git repo / Confluence (choose one per team convention) - Output: technical design (current arch, proposed change, affected components, steps, verification plan, risks). - Upload A (Git repo): place under the repo's agreed doc dir (e.g. `docs/design/<issue-id>.md`), reviewed together with the code PR — traceable. - Upload B (Confluence): create / update a technical design page, return the link. - Retrieve: downstream @FrontendDev / @BackendDev / @Tester read via the **file path or page link**. ## Content spec (platform-independent part) Per `multica-technical-design` skill: current architecture, minimal viable change, affected components, implementation steps, verification plan, risks. Keep stable headings and ids. ## Usage (role side writes only this line) > @Architect: "Produce technical design, land it via `multica-artifact-architect` skill to the team's agreed location (Git / KB), and return the reference." ## Swap platform (no role-prompt change)
Details
- Skill name
multica-artifact-architect- Repository
- it235/multica-best-practices
- Path
templates/en_US/skills/architect/multica-artifact-architect/SKILL.md- License
- MIT
- Repo updated
- 4 November 2026
FAQ
What does the Multica Artifact Architect skill do?
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.
How do I install the Multica Artifact Architect skill?
skills CLI (Claude Code, Cursor, Codex and more): npx skills add it235/multica-best-practices --skill multica-artifact-architect. Skills go in ~/.claude/skills (personal) or .claude/skills (project), and Claude loads them automatically when a task matches the description.
Is Multica Artifact Architect 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
架构师产物薄编排:校验设计草稿规范,落地时只调 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 Artifact Backend
279it235/multica-best-practices
后端产物薄编排:API 契约文档规范,落地调 multica-platform-confluence + multica-platform-jira。用于 @BackendDev 发布契约供前端/测试消费。
Multica Review Test
279it235/multica-best-practices
Test-artifact dedicated review framework. Called by TestReviewer to professionally analyze Tester's cases/report/coverage doc (coverage depth/acceptance mapping/coverage reasonableness/conclusion truth/contract consistency), output PASS/FAIL + fix list, report to Leader.
Tech Trend Watch
423mizchi/skills
Long-term technology stack review using State of JS, State of CSS, and Thoughtworks Technology Radar — satisfaction×usage matrix, ADOPT/TRIAL/ASSESS/HOLD mapping, P0–P3 migration priority. Use for annual stack audits, planning major migrations (jest→vitest, webpack→Vite, etc.), or on-demand replacement decisions. Not for general architecture design.
Multica Review Test
279it235/multica-best-practices
测试产物专属评审框架:T1 用例 Block/Revise/Pass、T2 覆盖率评估复核、T3 报告 PASS/FAIL/BLOCKED 三阶段评审,输出结论与修改清单汇报 Leader,供 TestReviewer 挂载。
Browse the most popular Claude skills, all testing & qa skills, or write your own with the skills generator.