Imported from Tsukugi/Rapunzel (AGENTS.md). Install upstream with npx skills add Tsukugi/Rapunzel. Copyright stays with the author.

Rapunzel agent guidance

Project

Rapunzel is a React Native 0.72 app for reading and downloading books and manga from Lilith repositories. It uses React Navigation, React Native Paper, Taihou for state and effects, MMKV for persistence, and a custom image cache.

Repository map

• src/ contains the app, API loader, cache, store, lifecycle, views, and shared tools.
• __tests__/ contains Jest tests for app behavior and utilities.
• scripts/ contains release tooling and its tests.
• android/ and ios/ contain native project files.
• docs/ contains behavior notes, troubleshooting details, the deployed smoke-test guide, and the cross-project test matrix.
• backlog.md contains open work.
• backlog-resolved.md contains completed backlog items and their verification history.

Commands

• Install dependencies: npm i
• Start Metro: npm run start
• Run the app: npm run android or npm run ios
• Run tests: npm test
• Run lint: npm run lint
• Run the TypeScript checker: npx tsc --noEmit

Working rules

• Read the relevant implementation and tests before editing.
• For a bug, reproduce it with a focused test before changing code.
• For an improvement, inspect the current implementation first, then add or update tests when behavior changes.
• Do not make blind fixes or recovery/best-effort fixes. Identify the cause and fix that cause.
• Keep changes small and consistent with the existing React Native architecture.
• Do not add secrets, credentials, generated build output, or local machine state.
• Preserve user changes already present in the worktree.
• Keep backlog.md and backlog-resolved.md current for every task. Add newly discovered or requested work to backlog.md, and move completed items to backlog-resolved.md with the resolution and verification details.
• Before handing off work, review both backlog files and document any backlog change made by the task. Do not mark an item resolved without recording how it was verified.

Verification

Before handing off a code change, run the most relevant focused tests, then npm test, npm run lint, and npx tsc --noEmit when the local toolchain supports them. Review the final diff and report any check that could not run.

Release verification

• MUST test the update before publishing it or reaching out to the user about a new release.
• Build and test the exact APK, OTA bundles, manifest, and release assets that will be published.
• For an Android update, install the older build, apply the update, and confirm the app starts and the changed behavior works.
• Verify the public manifest returns HTTP 200, has the expected version and URLs, and that every published asset is downloadable with the expected hash.
• If the update cannot be tested, stop and report the release as blocked. Do not publish it or describe it as ready.

Commits

If a commit is requested, use a clear title and a summary of at least 50 words that explains what changed and why. Do not put file paths in the commit message.