r/CraftDocs

No way to learn it just by noodling around. WT general F??? What is it with geeks? Seems programming chops and thinking chops are mutually exclusive. I went to an Apple World Wide Developer's Conference back in the early 1990s. One of the top apple engineers bragged that Apple's new programming IDE was "So easy my grandmother could use it!" A person in the audience yelled out "I'll hire her right now!" If you get the joke you are probably not a geek. If you don't get the joke you are probably trying to sell an application that nobody can use. An application like Craft. If you are wondering why my tone is so critical, its because I am so hoping that someone will build an all in one document envinronment that integrates content with calendar and tasks and team and resources in such a way as to allow one to create in any format they can imagine and then easily pivot that content (and creation) into any other format or presentation or navigation format they need at any given future moment. I want a computing environment that works with me not against me, that is fluid in possibilities yet solid in expected behavior. I want a computational environment that learns from my work, that doesn't go to sleep when I walk away, that goes into overdrive when I am not getting in its way, that is constantly looking over my shoulder, constantly trying to understand my content, and the scope and direction of my efforts, and then building out multiple most probable trajectories so that when I come back I am not staring at empty new documents but reviewing and selecting the best futures as built out by my computer as deeply intuitive and eager collaborator. A user should be able to start anywhere they want to start… a drawing, a graph, a diagram, a flowchart, a mind map, an outline, a text block, a table, an annotated freehand sketch, an interactive dynamic space, a set of constraints or inputs, a goal statement, a simple "I wish…" directive, a linear slide deck, a set of note cards on a cork board… or an admixture of any of the above. All of my work should be viewable from any other perspective or orientation or format. I should never have to save anything out to a document, everything I do should always be added to a history timeline that I should be able to navigate and branch out of at any time. Attributes like subject, object, intent, semantic proximity, semantic complexity, semantic relational popularity, should all be instantly obvious and presented in a fluid easily understandable interface that is intuitively navigable. Creation of content, and edits to and comments upon content should be just as easy to apply while navigating through my work. Collections should be just that, artificial boarders placed around arbitrary regions of my work to simplify and highlight and draw attention to, but not to separate from the larger general context of my life's oeuvre. And collections must be just another form of content to be recorded and cataloged as resource for all of the other creation and prediction work that is the collaboration of myself and the computer as extension of myself. I keep hoping. I keep hoping. Craft is not it at all.

I use both ChatGPT and Claude, and I want to keep my context and instructions in Craft so they are “portable” between AI providers.

I connect to Craft through MCP and work directly in ChatGPT or Claude. I tried the Craft AI agent, but it was not very useful for me. I am tired of repeating the same instructions about how I want things done.

Does anyone use Craft to store reusable AI skills, preferences, or project context? How do you organize them, and how do you get your AI tools to read and follow them?

I would like to hear what works for you, especially if you use more than one AI provider.

I really love Goodnotes handwriting and photo features and would love to find a way to integrate it with Craft. Anyone do this already?

The Craft connector is useful because Claude can read and write directly in a space, but the same convenience can blur the boundary between working notes and material a person has already reviewed. A prompt mistake should not be able to rewrite an accepted decision, client record, or source note just because all of them are visible in the same context.

One structure would keep an assistant-writable inbox and working area separate from reviewed documents. Claude could read the reviewed area, create proposed updates in the working area, and link each proposal to the exact document it would supersede. A person would promote the change after review. That only works if Craft or the connector can enforce narrower permissions than full read/write access to the space; naming conventions alone are not a real control.

How are people handling this with Craft's current permission model and MCP connector? Can access be scoped to selected folders or documents, or do you use a separate space, a read-only integration, exports, or another approval step to protect reviewed content?

I love Craft, but my main interaction is with ChatGPT on my Mac, not within Craft itself. Now with the introduction of Dots, these always-on agents are very powerful. When will Craft get its own plug-in in the ChatGPT Store?