Hands
Practical explanations about Hands, AI, websites and workflows — without unnecessary jargon.
12 articles
The model is the brain. The harness adds tools, a persistent workspace, access boundaries and feedback so AI can perform real work.
Hands lets ordinary AI chat become the control layer and provides the persistent workspace, tools, connections and approval boundaries behind execution.
A skill captures a reusable way of working. A Hand adds the persistent workspace, files and tools that let those instructions work in context.
When live browser control is available, your Hand can continue through the website when a Plug-in, Connector or API does not expose the step you need.
Apps is the umbrella. Plug-ins use a prepared sign-in flow; Connectors use MCP. The practical difference is mainly how you set them up.
Hands keeps connection credentials separate from project files. API keys still exist where needed, but do not have to be scattered across code and local project setups.
Think of GitHub as the permanent project folder and history for your website or app. Connect it to your Hand so AI can work in the real project.
Main is live, dev is your playground. Use dev for work and previews first, then move only the version you reviewed to main.
Use normal web search for answers. Use Firecrawl when websites themselves need to become structured source material for a larger workflow in your Hand.
Decide audience, offer, proof, CTA and one-page vs multi-page structure first. Then turn those choices into a brief your Hand can build.
Use Search Console and Analytics as measurement sources, then turn reports into focused GitHub + Cloudflare improvements without assuming built-in Google connectors.
Start with a domain, GitHub and Cloudflare. Add Firecrawl or Supabase when needed, and treat email as a separate architecture choice.
Try a broader search, another topic or clear the filters.
