Replace bracketed placeholders before running these prompts.
Daily Feature Prompt
You are working on StratoFusion. Add [feature/change].
Follow AGENTS.md, public/docs/developer/AI_OPERATING_PROTOCOL.md, and the relevant public/docs files. Keep the design provider-agnostic, respect `(provider, account, resource)`, use rclone/Fly.io for transfers, keep UI render-only, add targeted tests/docs, use PowerShell and PNPM, and do not use WSL.
Architecture Planning
You are working on StratoFusion. Read AGENTS.md, README.md, and the relevant public/docs files before proposing changes.
Plan [feature/change]. Use public/docs/developer/AI_OPERATING_PROTOCOL.md for intake and implementation patterns. Keep the design provider-agnostic, interface-first, and compatible with the `(provider, account, resource)` boundary. Identify affected ports, services, adapters, canonical models, rclone/Fly behavior, OAuth/auth, quotas/subscription tiers, tests, and docs. Do not write code yet. Use PowerShell by default, PNPM only, and do not use WSL.
Requirements Discovery
You are working on StratoFusion. Ask me for the missing requirements for [feature/change].
Focus on source/destination direction, destructive behavior, provider/account/resource boundaries, OAuth scopes and token refresh, provider quotas, transfer quotas, subscription/trial effects, rclone/Fly safety, conflict resolution, expected docs, and the right feedback loop. Ask concise questions before implementation.
Interface-First Implementation
You are working on StratoFusion. Implement [feature/change] interface-first.
Read existing ports, services, adapters, and canonical models before editing. Keep UI render-only. Hide provider quirks behind adapters or services. Avoid `any`, keep files under 500 LOC, use PNPM, use PowerShell by default, and do not use WSL. Add or update targeted tests and docs.
TDD Implementation
You are working on StratoFusion. Use TDD for [feature/change].
First identify the smallest failing unit, integration, component, or E2E test that proves the behavior. Cover edge cases for auth failures, timeouts, retries, quota enforcement, and provider differences where relevant. Implement the minimum change behind stable interfaces, then rerun the targeted checks. Use PNPM only and no WSL.
Provider Adapter Work
You are working on StratoFusion provider adapter code for [provider/change].
Normalize provider outputs into canonical models such as `FileItem`, `FolderItem`, and `PathRef`. Do not leak provider IDs, path quirks, duplicate-name behavior, rate-limit shape, or raw API responses into UI. Respect `(provider, account, resource)`. Add deterministic tests with provider APIs mocked behind interfaces.
Rclone Safety Review
You are working on StratoFusion rclone/Fly.io transfer logic.
Review [diff/path] for data-safety risks. State the source, destination, direction, command intent, destructive flags, dry-run behavior, conflict policy, secret scrubbing, timeout/stall watchdog behavior, cancellation semantics, quota preflight, and operation/job reconciliation risks. Flag any ambiguity before changes are made.
Test Planning
You are working on StratoFusion. Create a test plan for [feature/change].
Choose the correct feedback loops: TypeScript, unit, integration, component, Playwright/E2E, or manual verification. Include auth failure, token refresh, provider quota, transfer quota, timeout, retry, cancellation, conflict resolution, and multi-account cases where relevant. Keep tests deterministic by mocking external systems behind interfaces.
Documentation Update
You are working on StratoFusion docs for [feature/change].
Update only the canonical docs that map to the behavior: architecture in public/docs/ARCHITECTURE.md, API in public/docs/API_REFERENCE.md, deployment/env in public/docs/DEPLOYMENT.md, billing/trial in public/docs/SUBSCRIPTION_MANAGEMENT.md, rclone/Fly in public/docs/RCLONE_SERVICE.md, and testing in public/docs/TESTING.md. Do not invent architecture or secrets. Keep the wording concise and consistent with existing docs.
Final PR/Diff Review
You are reviewing a StratoFusion diff before PR.
Lead with findings. Check for provider logic leaking into UI, duplicated provider behavior, shallow helper sprawl, weak interfaces, unsafe rclone assumptions, unclear source/destination direction, auth failure gaps, timeout/retry gaps, quota/tier enforcement gaps, missing tests, missing docs, Windows/WSL violations, files over 500 LOC, `any`, secret/logging risks, and destructive operation safety. Include file/line references and recommended fixes.