SEO & GEOSophia
Give Sophia the target pages, audience, priority markets, CMS context, and visibility goal. She can turn audits and content gaps into an ongoing roadmap.
Guides & tutorials
Step-by-step workflows for turning a request into a reviewable output, then saving the context that makes the next step easier.
FormatWorkflow guides
CoversBuild, docs, agents
Use whenYou want a repeatable path
Walkthroughs
Pick a workflow and follow the pins
Each guide ends with a useful artifact, not just a better understanding of the product. Choose a workflow, then click each numbered step to see where it happens on the surface.
Chat - Cody
What audience and pages should this site cover?
Homeowners. Home, services, booking.
Describe audience, pages, style...Reliable repairs, booked in minutes.
Layoutdone
Copydone
Responsivedone
Launchreview
Compass
Knowledge workflows should preserve decisions
Compass is most useful when pages capture why something matters, what was decided, and what should happen next. Use it to turn scattered notes into a navigable product map.
Teammates
Specialist workflows need boundaries
Teammates are strongest when they know their target, permissions, success criteria, and escalation path. This is especially important for security, SEO, support, legal, and delivery operations.
SEO & GEO
SecurityJessica
Define the target, scope, credentials, production-safety boundaries, and reporting format before a scan or pentest-style workflow begins.
SupportMason
Connect product knowledge, common user questions, escalation policy, and preferred tone so support content and triage stay consistent.
FAQ
Common questions
Are these tutorials only for websites?
No. Websites are a common starting point, but the same workflow pattern applies to apps, presentations, documentation, support flows, audits, and internal tools.
What makes a thinQit tutorial different from a prompt library?
A tutorial shows the whole loop: context, action, review, iteration, and where the result should live afterward. The prompt is only one part of the workflow.
Can I mix Codex, Compass, and Teammates in one workflow?
Yes. Many real workflows move through more than one product area. The important part is to keep the handoff clear: what changed, what context matters, and who owns the next action.
What should I do after a tutorial produces an artifact?
Review the artifact, note what changed, save important decisions in Compass, and hand off any specialist follow-up to the right teammate. The result should become reusable context, not a one-off chat output.