// 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.
| name | documentation-workflow |
| description | 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. |
Документация massCode живёт в VitePress сайте в docs/website/documentation. README — это общий обзор проекта, а не источник детального описания фич.
docs/website/documentation/**docs/website/.vitepress/config.mtsdocs/website/public/**docs/website/documentation/index.mdREADME.mdrg, чтобы найти связанные страницы, скриншоты, shortcuts, labels и существующие формулировки.docs/website/documentation.title и description.<AppVersion text=">=x.y" /> ближе к началу страницы.docs/website/.vitepress/config.mts только если она должна появиться в навигации.docs/website/documentation/index.md только на широкие, cross-cutting фичи.<kbd>...</kbd> и указывай macOS плюс Windows/Linux варианты, если они отличаются.docs/website/public.withBase, например:
<img :src="withBase('/feature.png')">withBase, добавь соответствующий script block:
import { withBase } from 'vitepress'docs/website/documentation.git diff --check.pnpm -C docs/website build.github-workflow.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.
Use when changing massCode API routes, DTOs, IPC handlers, Electron bridges, or any renderer-to-main communication and storage-access boundaries.
Use when changing massCode localization, adding user-facing strings, creating locale keys, or wiring text through the project's translation system.