If you keep running into a problem that a guide or a breakdown would solve, tell me. Requests help decide what I explain next, and the answers join the library for everyone.
What it is
The request system is Slack-first. Crafter, Founder, and Mentorship members use #crew-ama to ask for new guides, workflow breakdowns, resource ideas, product critiques, or deeper explanations around AI-assisted solo dev work.
The channel keeps requests close to the real workshop: learning to build your own products, agent specialists, and studio systems. If a question needs more context, I can open a Slack thread with you, ask follow-ups, and turn the answer into a resource or Crew AMA segment for everyone.
How to submit
- Go to Slack and post in #crew-ama.
- Lead with the problem, not only the feature request.
- Add enough context for a useful answer: screenshots, code snippets, links, recordings, or a short explanation of what is blocking you. Remove passwords, keys, personal information, and customer data first.
- If it needs back-and-forth, I can keep the conversation in a Slack thread so the context stays attached.
What happens next
- Quick questions can get answered directly in Slack.
- Useful repeat blockers can become resources, templates, or workflow notes.
- Deeper questions can become part of a Crew AMA video or practical breakdown.
- Finished drops can be shared in Slack and added to the resource library.
Which channel fits
- A resource you wish existed, or a question that needs a deeper explanation: #crew-ama, as described above.
- An account, billing, or access problem: #help-desk, so it is handled as support rather than a request.
- Honest notes on your app from other members: #feedback, or bring it to Workshop Hour in #the-bench.
- Private review of your studio’s work: that belongs to Crafter Mentorship, in its private channel.