القائمة
Use when changing massCode API routes, DTOs, IPC handlers, Electron bridges, or any renderer-to-main communication and storage-access boundaries.
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Use when adding or updating massCode documentation, documenting a new feature, changing docs website pages, adding docs assets, updating the VitePress sidebar, or adding README feature mentions.
Use when generating massCode release notes for a GitHub release. Writes the notes to a gitignored file `docs/releases/<tag>.md` for the user to paste into the GitHub release. Use when summarizing merged PRs of a version into a consistent release notes structure.
Use when working in massCode and you need repo-wide architecture rules, naming conventions, decomposition boundaries, or guidance on which massCode skill to load next.
Use when working with massCode issues, branches, commits, pull requests, or merge preparation in GitHub.
Use when defining or reviewing massCode renderer types that come from generated API clients or DTOs, especially when deciding whether to reuse existing API shapes, derive narrower local types, or introduce a UI-only model.
Use when following massCode repo workflow rules, especially for scoped lint and test commands, or when changes require required follow-up commands like code generation or locale sync.
| name | electron-api-and-ipc |
| description | Use when changing massCode API routes, DTOs, IPC handlers, Electron bridges, or any renderer-to-main communication and storage-access boundaries. |
Все backend-возможности massCode живут в main process. Renderer получает доступ к данным и системным операциям только через Elysia API или IPC channels.
import { api } from '~/renderer/services/api'.ipc.invoke('channel:action', payload).src/renderer/electron.ts.При добавлении нового endpoint:
src/main/api/dto/;src/main/api/routes/;pnpm api:generate, чтобы обновить клиент.Не оставляй API-клиент рассинхронизированным с route/DTO изменениями.
ipc.invoke(...).fs:*system:*db:* — legacy или migration flows, не основной путь для новой функциональностиmain-menu:*prettier:*spaces:*theme:*pnpm api:generate.db:* flows там, где задача должна идти через текущую API/IPC модель приложения.