ワンクリックでManusで任意のスキルを実行

teamventure-architecture-migration

Use when refactoring TeamVenture domains/architecture; enforces migration order (Planning→Authorization→Identity→Infrastructure) and preferred steps (split classes before moving packages).

Manusで実行

概要

Use when refactoring TeamVenture domains/architecture; enforces migration order (Planning→Authorization→Identity→Infrastructure) and preferred steps (split classes before moving packages).

インストールコマンド

npx skills add https://github.com/muzhicaomingwang/ai-ideas --skill teamventure-architecture-migration

このコマンドをClaude Codeにコピー＆ペーストしてスキルをインストール

ソース

muzhicaomingwang/ai-ideas

スター3

フォーク2

更新日2026年1月22日 16:04

SKILL.md

readonly

name	teamventure-architecture-migration
description	Use when refactoring TeamVenture domains/architecture; enforces migration order (Planning→Authorization→Identity→Infrastructure) and preferred steps (split classes before moving packages).

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
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 @Transactional to 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

このリポジトリの他の Skills

同じリポジトリ

xhs-noteid

muzhicaomingwang/ai-ideas

Extract Xiaohongshu (小红书) noteId from shared note text or URLs, including xhslink.com short links and xiaohongshu.com/discovery/item/<noteId> links. Use when the user asks for “noteId/笔记ID”, provides a 小红书 share message, or pastes an xhslink short URL that needs redirect expansion.

2026-02-233

podcast-publish-xiaoyuzhou

muzhicaomingwang/ai-ideas

自动发布每日科技早报播客到小宇宙平台。触发场景：用户提到"发布播客"、"小宇宙播客"、"自动发布"、"播客上传"、"RSS发布"。适用于：将生成的播客音频自动发布到RSS.com，并通过RSS订阅同步到小宇宙，同时发送飞书通知。

2026-01-153

feishu-messaging

muzhicaomingwang/ai-ideas

飞书消息发送与文档创建工作流。触发场景：用户提到"发飞书消息"、"飞书文档"、"通知某人"、"发送到飞书"、"飞书通知"。适用于：发送飞书消息、创建飞书文档、操作多维表格、管理知识库。

2026-01-073

miniapp-design

muzhicaomingwang/ai-ideas

小程序页面设计与代码生成工作流。触发场景：用户提到"修改页面"、"更新UI"、"添加组件"、"调整布局"、"生成代码"、"小程序设计"。适用于：TeamVenture 小程序的页面设计迭代、UI 组件开发、样式调整。

2026-01-073

obsidian-organize

muzhicaomingwang/ai-ideas

Obsidian 知识库整理工作流。触发场景：用户提到"整理Obsidian"、"清理文件夹"、"知识库混乱"、"目录太多"、"合并分类"。适用于：个人知识管理、笔记整理、文件夹重组。

2026-01-073

research-by-reddit

muzhicaomingwang/ai-ideas

基于 Reddit API 进行深度调研并生成研究报告。支持搜索、获取帖子、评论分析、情感分析等功能

2026-01-073

ソース

muzhicaomingwang

muzhicaomingwang/ai-ideas

GitHub リポジトリを開く Creator のリポジトリを見る

インストールコマンド

ダウンロード

Manusで実行

役立つ用途SOC

ソフトウェア開発者コンピュータ・数学職15-1252L4

name	teamventure-architecture-migration
description	Use when refactoring TeamVenture domains/architecture; enforces migration order (Planning→Authorization→Identity→Infrastructure) and preferred steps (split classes before moving packages).

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
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 @Transactional to 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