Do not run git commands. You may READ files outside of this directory, but DO NOT WRITE (DO NOT ADD, DO NOT MODIFY, DO NOT DELETE) outside of the directory you are in.

If the way you are set up is not allowing you to keep working without coming back to me for small approvals, search the web to find out how I can set you up to let you keep working without you asking me for approvals.

To prevent collision of port usage, use port 8181 if you are Claude, 8282 if you are Gemini, 8383 if you are OpenAI. Remember not to use localhost, because dev server is on a computer and the test device is a separate phone.

Append the name of your app with who you are. For example, "Castle Claude", "Castle Gemini", "Castle OpenAI". With app ids like "com.castle.claude", "com.castle.gemini", "com.castle.openai".

When I ask you to write a report as an MD file for me to read, you must place that in the tools/tickets folder in the OVERALL project (/tools/tickets), not inside Castle. Make sure title of file is in the format of YOURNAME-YYMMDDHHMM-Title (e.g. CLAUDE-202601081216-UsabilityProblems.md).

While developing, keep testing your code using an iPhone simulator that you are given. It is "iPhone-Claude" or "iPhone-Gemini" or "iPhone-GPT" depending on who you are. Make sure to check screens and input the way user would input. When done, test on Android emulator as well. At the end, test on the physical devices (using release build that does not require dev server): an Android device over adb and an iPhone device connected wirelessly. Do not touch simulators that are not yours. Always specify port and simulator so that you do not clash with other agents.

EXTENSIVELY test the app before coming back to me for a review. DO NOT COME BACK TO ME until the app is working PERFECTLY. Work doggedly. Do not give up. Search the web as needed.

To use Expo MCP, start your dev server with MCP CLI: EXPO_UNSTABLE_MCP_SERVER=1 npx expo start.

Use safe area insets for screens (esp tab bar).

Use expo-sqlite.