mokhouse-operations

Automating MOK HOUSE operations loads centralized company context—structure, divisions, pricing, client patterns—into Claude conversations. This enables automatic activation across music projects, invoicing, and procurement workflows, ensuring consistent handling of ESM submissions, project briefs, and client relationships without manual setup each session.

Yes. The Skill provides operational templates for project briefs and invoices that activate automatically within MOK HOUSE discussions. Templates apply across music studio contexts and client workflows, reducing manual template lookup and ensuring consistent formatting and pricing logic.

The Skill integrates with Graphiti to capture and persist operational patterns and company knowledge across sessions. It maintains compatibility with existing Claude commands and memory storage, enabling learned context to activate automatically in future MOK HOUSE discussions without re-entry.

Activated context includes company structure, division responsibilities, client relationship data, pricing rules, and Indigenous procurement requirements. This knowledge applies across music projects, studio operations, ESM/Panda Candy submission workflows, and invoicing, enabling contextually accurate responses without manual briefing.

Yes. The Skill supports Indigenous procurement contexts within MOK HOUSE operations. Context activation includes procurement requirements and vendor patterns, enabling automatic application across business operations and client workflows that involve Indigenous community engagement.

No. The Skill enables automatic activation across sessions through cross-session memory persistence. Context loads automatically when MOK HOUSE discussions begin, eliminating manual reloading and ensuring operational consistency from conversation start.