Look up a prompt, check where a file goes, remember which Crown skill to call, or see what changed.
Crown AI Handbook
A searchable operating guide for Crown AI: get set up, find the right department guidance, see what changed, and send new ideas back into the system.
Estimating remembered2 context updatesLast used: Proposal Review
Pick Up Where You Need Help
Returning visits should not reteach setup. They should make the current AI-ready ways of working easy to find, use, or improve.
Return path: updates, department context, request loop, then reference only when needed.
My department
Context packs, task starters, related skills, and recent changes for the remembered department.
Open departmentSomething changedOnly meaningful global or department updates surface here. Setup documentation stays quiet.
View updatesI have an ideaRequests become future context packs, task starters, skills, or reference fixes.
Send requestChoose your entry point
First visit gets the Udemy-style entry cards. Returning visits collapse this and put search, department context, updates, and requests first.
This is intentionally not the final visual treatment. It is a working map for persistence, memory, and routing.
Start Here
Connect Microsoft 365, install Crown plugin, trust Crown AI, and run setup.
Your Department
Find use cases, prompts, quick starts, and department-specific updates.
Office / Warehouse / Workshop
Understand where rules, work, and Cowork each belong.
Crown Plugin
Six skills, when they fire, and when not to use them.
Ask a question, flag confusing instructions, or suggest a new AI assist without starting a hallway thread.
Ideas route to the topic they affect: department, plugin, folder system, or roadmap.
Start Here
First-run setup should feel like a guided walkthrough. Returning users get compact recovery notes if something is disconnected.
Reference: Boords-style clickable points.
Connect Microsoft 365
Open Settings, connect Microsoft 365, then make sure Crown AI is reachable through the connector. Do not use the local attach button for this problem.
First visitMac recovery
Use Claude Well
The trust rules stay findable, but returning users should not have to scroll through philosophy every time.
Returning state should favor summaries, copy prompts, and expandable details.
Habits that stay visible
Give contextJob, customer, source, and intended output.
Check factsClaude drafts and reasons. It is not the source of record.
Keep source attachedIf a source is disconnected, reconnect it instead of working around it.
Copy-ready prompt area
Real prompts from the existing page and quick-start guides become searchable, copyable blocks.
Turn these notes into a clean SOP draft...
Review this proposal for missing scope...
Sort these files into Reference or Active Work...
Your Department
The remembered department becomes the useful return path: model-readable context first, task starters second, skills and updates nearby.
This is not a prompt library. It is a catalog of current AI-ready ways the department works.
Return card pattern
Context modelReusable rules and sources the model reads across Claude.
Task starterA lightweight way to begin work using the right context, not the whole operating system.
Publishing pathNew ideas become context updates, task starters, skills, or reference fixes.
Department updateContext PackSkill coverage
Office / Warehouse / Workshop
This section teaches the file system through a visual model, then turns into a lookup table for where work goes.
First visit: concept and step-through. Returning visit: destination rules first.
Lookup rules
OfficeStandards. Fixed company rules and examples.
WarehouseWorkspaces. Active Work, Reference, and Completed.
WorkshopCowork. Where the work happens, not where the permanent copy lives.
Visual explainer lives here
Use the approved Office/Workshop/Warehouse image or rebuild it as an interactive step-through once the layout is ready.
Crown Plugin
Each skill gets a compact card: what triggers it, what it creates or moves, and when not to use it.
Returning users likely land here from search.
Ask / Request
This is the pull side of the living handbook: questions, confusion, skill ideas, and job-specific AI opportunities become future updates.
First version can be mailto only. No backend, no database, just a prefilled triage note.
Updates & Publishing Path
New things enter the handbook as typed updates, then show up where they are useful: global strip, department card, skill reference, or system reference.
The update path keeps the return screen current without turning it into a daily dashboard.
System Reference
Setup, folder structure, trust rules, and plugin documentation stay searchable and available, but they do not lead the returning experience.
Reference lives below the working loop unless search brings someone directly here.