docs: update project rules to include guidelines for component refactoring, bulk verification, UI debugging, and Vuetify documentation consultation

2026-03-27 15:02:29 +08:00
parent 6e38211382
commit 6d20ee3cc1
1 changed files with 5 additions and 0 deletions
@@ -4,6 +4,11 @@
 - Follow the existing code style and patterns.
 - Use pnpm for running project commands.
 - Keep code in TypeScript unless migration is required.
 - When refactoring or creating new components, review `docs/frontend-layering.md` first and follow its layering and responsibility guidelines.
 - For bulk verification failures such as `pnpm run lint`, collect the full output first, then split the work into non-overlapping batches by file or concern and assign those batches to subagents in parallel. Keep the integration and final verification pass in the main agent.
 - For UI debugging that spans implementation, state flow, and live browser behavior, use subagents deliberately: one for component contracts and event flow, one for data sources / routing / integration, and one for live browser verification. Do not edit files until the evidence from those threads converges on a root cause.
 - Treat subagent output as scoped evidence, not as a final answer. Use subagents to narrow the search space, confirm or eliminate hypotheses, and reduce local context load before making edits.
 - When a problem is directly tied to Vuetify component behavior, props, slots, accessibility output, or generated DOM, consult Vuetify MCP and official Vuetify API documentation before changing the implementation. Prefer supported Vuetify props, slots, and documented extension points over custom replacements unless the documented API is insufficient.
 ## Stack
 - Framework: Vue 3 + Vite