mirror of
https://github.com/XiaoDaiGua-Ray/ray-template.git
synced 2026-11-17 16:13:36 +08:00
Load sign-in assets in the initial graph and defer the workspace, demo features, and mock client until needed. Split feature dependencies and clear stale files from the default production output. Document feature entry points for runtime imports and record the browser and Harness results.
2.3 KiB
2.3 KiB
Ray Template
A Vue 3 + TSX admin template with an admin application, a documentation site, and shared packages.
- To locate an implementation, choose a topic from the task index or
pnpm harness context <scope>. Consult the architecture map for changes that cross module boundaries. - Check
git statusfirst and preserve existing changes. Trace callers and existing data contracts before changing routing, persistence, requests, or shared components. - Prefer feature entry points for runtime imports. Follow the runtime import boundaries when adding exports or changing what loads at startup or on demand.
- For complex tasks, the lead agent may choose to use subagents under the delegation guidelines, when the host supports them and current permissions allow it. Delegation needs no separate approval. The lead agent owns integration and final verification.
- Write agent guidance and internal engineering documentation in English. Preserve the intended languages of product copy and reader-facing documentation.
- Follow the comment style when adding or editing comments. Maintain both Chinese and English product copy. For visible behavior changes, use browser verification only for affected pages, actions, and dimensions.
- For custom CSS, follow the style contract: consume semantic theme tokens and the shell's runtime layout variables so style, color mode, primary color, and layout preferences keep working. Keep provider ownership and scoped overrides explicit.
- Select relevant tests or
pnpm harness verify <scope>using the verification scope. Small changes do not default to full checks or a UI/UX sweep. Use full checks for integration risk, releases, or an explicit request. Pages builds and publishes on main independently of full verification. Within one task, rerun only checks affected by subsequent changes. Report what was and was not verified. - Establish engineering facts from current source, manifests, and the lockfile. Keep sensitive data out of source, prompts, and evidence. Commits, pushes, and deployments require user authorization.