Put Meta's Muse to work on the coordination around your Adobe files

Module 1Does Muse Fit Your Creative Work?4 lessons

1. 1What Muse Is: An Agent With Its Own Computer

   • Describe how an agent that carries out tasks differs from a chat assistant that answers questions
   • Name the Muse features this course uses: Chats, side chats, Artifacts, Goals, scheduled tasks, Connectors and Memory
   • Separate Muse from Meta AI, from the Muse Spark model and from unrelated products called Muse
2. 2Access, Plans and Limits as of October 2026

   • Check whether you are eligible to use Muse by age and country
   • Compare the Free, Power and Maximum plans using Meta's official figures
   • Spot third-party pricing and token claims that conflict with Meta's official pages
3. 3No Adobe Connector: Muse Works Around Your Files

   • Check Meta's official connector lists and confirm none includes an Adobe app
   • Sort your weekly tasks into ones Muse can coordinate and ones that stay in your hands
   • Explain to a colleague why this course won't promise Adobe automation
4. 4What Muse's Incidents Teach a Creative Studio

   • Link each recorded incident to the setting or habit that guards against it
   • Decide whether Muse fits your business, given your NDAs, releases and licences
   • Explain why the Activity log is more reliable than the agent's own explanation of what it did

Module 2Safe-Start Setup4 lessons

1. 5Create a Separate Account and Turn Off Training

   • Create a Muse account kept separate from your existing Meta profiles
   • Turn off Help improve our AI models and confirm it is off
   • Choose a neutral agent name and avoid client details during onboarding
2. 6Permissions: Always Ask, and Answer With Allow Once

   • Set Connectors and Web access defaults to Always ask
   • Choose Allow once or Deny on an approval card after reading See task details
   • Explain why Always allow and Allow for this task are too broad while you learn
3. 7Memory, Soul and a Side Chat for Each Client

   • Write a memory entry stating your role, working hours and creative boundaries
   • Edit Memory.md and Soul.md under Identity
   • Set up a side chat for each project using a client code instead of a name
4. 8Your First Read-Only Task and the Activity Log

   • Run a read-only task using a dummy brief
   • Find each action and permission in the Activity log
   • Check that nothing was created, moved or sent

Module 3Connect Only What Each Workflow Needs4 lessons

1. 9Least Access: One Connector at a Time, Read Only

   • Connect a service through Settings > Connectors and set it to retrieval only where offered
   • Confirm in Settings > Connectors that no Adobe connector is listed
   • Ask Muse what a connector can do and what it will ask before doing
   • Disconnect a service and ask Muse to forget what it read
2. 10What Stays Out, and How to Explain It to a Client

   • List the asset types and data you will keep out of Muse
   • Write a two-paragraph note telling a client how you use an AI agent and what you never give it
   • Strip client names and confidential details from a brief before pasting it
3. 11Cloud Folders and Email: Dropbox, Box, Gmail and Calendar

   • Connect Dropbox or Box and Gmail with read-only access, and Google Calendar too if you need it
   • Point Muse at one test project folder by name
   • Run a read-only check that lists recently modified files without moving or sharing anything
4. 12Muse for Mac: One Project Folder, Copies Only

   • Set local app access to Off or Read only
   • Decide whether to grant Full Disk Access, knowing it covers the whole Mac
   • Write a folder-limited instruction that makes Muse show its plan and wait for approval

Module 4Write Your Method So an Agent Can Follow It2 lessons

1. 13From Habits in Your Head to a Written Method

   • Explain the difference between a Photoshop action that replays clicks and an agent that follows a method
   • Write down the steps of one recurring coordination job
   • Mark which steps you hand to Muse and which you keep
2. 14Inputs, Steps, Stop Points and [CHECK] Marks

   • Write an instruction block with inputs, steps, output format and stop points
   • Add a [CHECK] rule so unverified items are marked rather than guessed
   • Test the block on a dummy job and revise it

Module 5Workflow: Brief to Deliverables Checklist and Spec Matrix3 lessons

1. 15Separate Required From Optional in a Brief

   • Write a prompt that sorts brief elements into required, optional and unclear
   • Spot items the brief leaves unclear, including whether generated elements are allowed
   • Correct Muse's sorting where your judgment differs
2. 16Build the Deliverables Checklist and Spec Matrix

   • Write a prompt that produces a spec matrix with one row per deliverable
   • Check the matrix's dimensions, colour spaces and naming against the brief
   • Keep the matrix private and versioned
3. 17Shot List and Questions for the Client

   • Generate a shot list grouped by setup with time estimates
   • Turn every [CHECK] into a clear client question
   • Approve and send the questions from your own email

Module 6Workflow: Asset Intake and Reference Log3 lessons

1. 18Asset IDs, Sources and Permission Status

   • Write a prompt that builds an asset log with ID, source, permission status and version
   • Use fixed permission values so nothing unknown passes as approved
   • Check a sample of log entries against the actual files
2. 19Missing Inputs: Pause After One Follow-Up

   • Write a rule that pauses any request whose input is missing
   • Approve a single draft follow-up and send it yourself
   • Track paused items until the input arrives or you decide
3. 20Duplicates and Replaced References, Flagged Not Resolved

   • Write a rule that flags duplicates and replacements without deleting or overwriting
   • Decide which version is current and record why
   • Spot reference drift before more work depends on it

Module 7Workflow: Client Feedback Into Edit Packets3 lessons

1. 21Gather Feedback From Email and Cloud Folders

   • Write a read-only prompt that collects feedback since a given date
   • Check that each change is tied to a specific file and version
   • Spot conflicting or vague feedback and flag it for the client
2. 22Edit Packets: Source Version, Changes and Details to Preserve

   • Produce an edit packet naming the source version, the areas to change and the details to preserve
   • Reject a packet whose source file is missing or can't be reviewed
   • Stop a correction cycle that keeps failing
3. 23Draft Replies You Approve and Send Yourself

   • Generate a draft reply confirming the changes and delivery date
   • Check the draft against the edit packets for overpromising
   • Send it yourself and log what was confirmed

Module 8Workflow: Pre-Delivery Check and Your Visual Review2 lessons

1. 24Schedule the Pre-Delivery Check and Read One Exception List

   • Schedule a read-only pre-delivery check with a day, time and time zone
   • Confirm the task under Upcoming and set its approvals
   • Act on each exception: fix it, ask the client or hold the file
2. 25Your Visual Review at 100 to 200 Percent

   • Have Muse draft a visual review checklist from your notes
   • Inspect each file at 100–200 percent for shadows, reflections, edges, perspective and label text
   • Approve, return or hold each file and record your decision

Module 9Weekly Review and Keeping Your Method Current2 lessons

1. 26The Weekly Review: Activity Log, Upcoming, Allowed Websites, Memory

   • Review the Activity log for unapproved or unexpected actions
   • Remove stale scheduled tasks, allowed websites and memory entries
   • Recheck connectors and permission defaults
2. 27Export, Disconnect, Forget and Reset, and Revise Your Method

   • Download your Muse data before any reset
   • Close a project by disconnecting, forgetting and deleting its side chat
   • Revise your method document after each job