Contact
Have ideas, spot an issue, or want to collaborate? Reach out using the channels below. We respond to constructive feedback and correction requests, and we welcome examples that show how you adapted prompts to your voice or audience. If you’re reporting an error, include a short description, the page and section, and any public thread we should reference. For collaboration, describe the outcome you want (co‑authored post, resource update, shared prompt set) and timelines. The goal is to help you ship a credible recap, improve the guidance, and keep content reliable for the wider community. To speed triage, use clear subject lines (Bug, Clarification, Example Share) and include links rather than attachments. We prefer public, reproducible references and summaries that a newcomer could understand. Corrections are logged with effective dates and notes; if a section is unsafe or unclear, we revise or deprecate it. We do not offer paid support and we do not collect personal analytics; responses happen as time allows, typically within 24–48 business hours.
For feedback, suggestions, or corrections related to the guide. If you noticed outdated instructions, missing context, or examples that need clarification, email us with links or screenshots. We prefer actionable messages: describe the problem, share a reference thread if applicable, and suggest how the section could be improved. We read every note and prioritize changes that improve safety, clarity, or usability for creators and teams using Grok on X. Use concise subject lines (e.g., “Correction: Step 3 prompt constraint”) and include one paragraph that states the issue, one that cites evidence, and one that proposes a fix. If privacy is a concern, redact names and remove private analytics. We may publish anonymized changelogs or examples to help others learn; if you prefer not to be cited, say so in the email. We cannot guarantee individual coaching, but we aim to ship improvements that benefit everyone.
Social
Follow or mention us on X if you share something built with this guide. We like short, practical recaps and posts that credit collaborators and reference public threads. If you publish a recap using our prompts, tag your highlights (best thread, most discussed theme, one collaborator to thank) and add an accessible text summary. Mention us if you want feedback or if a section helped you ship faster—we often collect examples to improve guidance. To make replies more useful, include context: what prompt you used, what you edited, and what you would change next time. We avoid DMs for support and prefer public threads so others can learn; if a conversation requires privacy, keep it brief and remove any sensitive details. Accessibility matters—add alt text to images and avoid tiny text. If your post inspires a documentation update, we’ll credit the example and link back.