Ark DW

Required Startup

Do these before proposing edits:

1. Read CODEX.md, AGENTS.md, and the relevant files under .github/instructions/.
2. Use DEVELOPMENT.md and directoryList.md when the repo workflow or directory ownership is unclear.
3. Write a short spec requirement sheet with:
   • confirmed
   • required
   • assumptions
4. If the task is a bug or regression, locate root cause before changing code.
5. If the task spans multiple modules, shared behavior, or both PC and mobile, write a plan before implementation.

Treat the bundled references as summaries. Repository files are the source of truth when they differ.

Route The Task First

Before editing, classify the task into one of these buckets and then follow references/task-playbooks.md:

1. Page container: component names ending in Page or Mobile
2. Published component: pub-*
3. Internal business component: bu-*
4. Common or shared component: skeleton, tabs, shared style/*
5. Shared config or schema change
6. PC-to-mobile parity or migration work
7. UnoCSS or layout cleanup
8. Locale, icon, or crossbow mapping change

Hard Repository Rules

• Mixin first: index.js keeps lifecycle and mounting. Push business logic into sibling *.mixin.js files by default.
• Config first: default props belong in configRulesProps/. Config model changes also inspect config.json.mjs.
• Publish boundaries:
  • Page and Mobile components must be declared in both miniprogram/app.json and plugin.json.
  • pub-* components must be declared in plugin.json.
  • bu-* components must not be declared in plugin.json.
  • Common components are not published.
• UnoCSS first: prefer utility classes in AXML, keep index.acss import-only when possible, extend uno.config.js before adding component selector CSS.
• Shared style normalization: if inline style strings consume numeric props, normalize bare numbers to px.
• Reuse existing locale, icon, crossbow, mixin, and config patterns. Do not add parallel conventions.
• Shared changes require checking callers, docs, config, and validation scripts, plus the sibling PC or mobile side when the behavior is meant to stay aligned.

Verification Standard

Run the narrowest commands that prove the change. Typical commands:

• pnpm dev:page
• pnpm dev:pageMobile
• pnpm build:page
• pnpm build:pageMobile
• pnpm build:devPageMode:page
• pnpm build:devPageMode:pageMobile
• pnpm --dir packages/page run test:commonPageLayout
• feature-specific scripts under packages/*/scripts

Only report commands actually executed and their real outcomes.

Communication

• Reply in Chinese by default.
• Keep English for identifiers, APIs, code, and framework terms.
• Keep summaries factual and review-friendly.
• Separate verified facts from assumptions.
• When the user asks for compressed output, follow Token Save Reply in references/repo-rules.md.

References

• references/repo-rules.md
• references/repo-workflow.md
• references/task-playbooks.md