Claude Code

Add EnterestOS response tracking using Claude Code.

2 minPrerequisites: Project created in EnterestOS

Problem: You are using Claude Code to build or modify a project and want to add response tracking without manually writing SDK integration code.

Solution: Give Claude Code a specific, scoped prompt — it integrates EnterestOS into your form submit handler without touching anything else.

Steps

  1. 01.Create a project in EnterestOS and copy your project key
  2. 02.Open your project with Claude Code
  3. 03.Paste the prompt below into the Claude Code session
  4. 04.Review the proposed changes
  5. 05.Submit a test form
  6. 06.Confirm the submission appears in Inbox under Reply

Prompt to Use

Update the contact form submit handler to track responses with EnterestOS.

Requirements:
- Preserve existing UI
- Preserve existing validation
- Preserve existing backend logic
- Install @enterestos/sdk
- Use project key: pk_live_xxx
- Track submission type: contact_request
- Call trackResponse() after successful submit
- Wrap tracking in try-catch — do not block submission on failure

Return modified files and testing instructions.

Be specific with Claude Code

Vague prompts produce incorrect results. Always specify: which form to update, the exact project key, the submission type, and that existing logic must be preserved.

Verification

  1. 01.Submit test data through the form
  2. 02.Go to /app/inbox
  3. 03.Confirm submission appears with status Reply

Result: You now have EnterestOS integrated via Claude Code — your form tracks every submission without changing your existing code.

Common Questions

How do I connect a form to EnterestOS using Claude Code?

Give Claude Code a prompt naming the form file, your project key, the submission type, and the instruction to preserve all existing logic. It installs the SDK and adds trackResponse() to the submit handler.

Why do I need to be specific when prompting Claude Code for EnterestOS integration?

Vague prompts produce incorrect results. Claude Code needs to know exactly which form to update, which project key to use, which submission type to set, and that all existing logic must stay unchanged. The more specific the prompt, the cleaner the output.