First verify the installed version, target platform, and scope of changes, then read the reference according to the task. Do not mix Wot v1/v2; do not arbitrarily upgrade dependencies or add plugins just because you are following the standards.
Framework mechanisms are based on the linked documentation and the installed version; the naming, comment style, and style division of labor selected in this document are project conventions, and existing explicit repository standards take precedence.
Read on demand
| Task | Standards |
|---|---|
| Files, variables, functions, Store, events | Naming |
| Request and response types, API boundaries | Types and interfaces |
| Comments, TSDoc, TODO, compiler directives | Comments |
| UnoCSS, BEM, SCSS, themes | Styles |
| Directories, subpackages, page configuration, layout | Pages and layout |
| Forms, pagination, sessions, caching, acceptance | Quality checks |
Change boundaries
- The standards apply to this change; do not include repository-wide renames or modifications to third-party or automatically generated files.
- When only updating the standards, do not modify application code; this skill does not include project refactoring checklists or business pseudocode.