docs: add ready-to-use coding agent prompts for local setup and experiments

[Zaimwa9]

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

• New Getting Started page with a copy-paste coding agent prompt that runs Flagsmith with experimentation locally via Docker Compose: admin account, organisation, project, environments, ClickHouse warehouse and the Flagsmith CLI.
• New Experimentation page with a prompt, run from the user's own app, that creates a keyed multivariate flag, metric and experiment, starts it, and instruments the code by following the per-language SDK docs.
• Tip linking to the experiment prompt from the Experimentation overview.

Depends on #8797: the SDK page's language tabs and #troubleshooting anchor come from there.

How did you test this code?

Followed both prompts end to end on a fresh local stack (setup, warehouse, CLI, experiment, JS and Python events, results refresh).

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Oct 16, 2026 12:33pm UTC

2 Skipped Deployments

Project	Deployment	Actions	Updated
flagsmith-frontend-preview	Ignored	Preview	Oct 16, 2026 12:33pm UTC
flagsmith-frontend-staging	Ignored	Preview	Oct 16, 2026 12:33pm UTC

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: b491cd4c-0778-458a-8813-e98f0c23b179

📥 Commits

Reviewing files that changed from the base of the PR and between 37842c2 and 48ebb30.

📒 Files selected for processing: 2

• docs/docs/experimentation/set-up-with-a-coding-agent.mdx
• docs/docs/getting-started/run-locally-with-a-coding-agent.mdx

📝 Walkthrough

The changes add two coding-agent guides. One covers running Flagsmith locally with Docker and configuring its services, resources, warehouse and CLI. The other covers setting up an experiment, instrumenting an application, optionally simulating traffic and checking results. The experimentation index links to the new experiment guide.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~20 minutes

Merge Risk: 🔵 Low · up to 37842

The new coding-agent guides can produce an invalid experiment split for multiple variations. They also point Java, Node.js, Go and Flutter users to SDK instructions that don't exist yet. Fix both before merging, or confirm that the dependent language-tab change lands first.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[coderabbitai]

Actionable comments posted: 2

---

ℹ️ Review info

⚙️ Run configuration

• Configuration used: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: a128aa3c-8b94-4d94-b313-5810f0e02e49

📥 Commits

Reviewing files that changed from the base of the PR and between 8bed28a and 37842c2.

📒 Files selected for processing: 3

• docs/docs/experimentation/index.md
• docs/docs/experimentation/set-up-with-a-coding-agent.mdx
• docs/docs/getting-started/run-locally-with-a-coding-agent.mdx

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 5 remain after this review.