Your team's Claude system — built around how you actually work. Install once, and every conversation starts with full context.
"Hi Susan — thanks for the meeting today. It was great discussing the project direction. As discussed, we'll be adjusting the scope to reflect the changes your team raised. I'll send over an updated timeline by end of week. Please don't hesitate to reach out if you have any questions in the meantime."
"Hey Susan — good call today. Two things needed from you:
1. Confirm you're okay pulling the reporting dashboard out of phase one and moving it to phase two.
2. Let Jack know we're holding on the onboarding flow rework until his team signs off on the ops feedback. We won't start until he gives the green light.
Timeline stays the same for everything else. I'll have an updated scope doc over by Wednesday."
Same prompt: "write a follow-up to Susan from today's call." The difference is everything Foundation configures — context files that know your business, your voice, and this specific client.
The plugin connects to your team's shared Drive folder where company context lives. Each teammate runs onboarding once. After that, every skill knows who they are, how they write, and how the company works.
In Cowork, open Customize → Plugins. Paste jmason33333-ux/nobo-foundation-plugin into the search bar. Click Install. All 17 skills load automatically.
/onboard.Type the slash command in any Claude conversation. A 10-minute guided dialog creates your personal profile:
No forms to fill out. It's a conversation, not a questionnaire.
Create a new project in Claude. Type /new-project and answer a few questions about the client or engagement. All context files are written automatically — every specialist now knows the landscape.
Ask naturally, or invoke a skill by its slash handle. Claude picks the right specialist, reads your context, and produces output in your voice.
When you run /onboard and /new-project, the plugin creates context files every specialist reads before responding. These are why output sounds like your company, not like a generic AI. In your shared Drive folder they live as Google Docs with Title Case names (for example, How We Communicate). The plugin creates local working copies with the kebab-case names below when skills run.
/new-project.Each skill reads your context files before responding — your brand voice, your team structure, the current engagement. The output sounds like your company wrote it, because in every meaningful sense, your company did.
Drafts, reviews, and improves any message going to or from a client — status updates, follow-ups, meeting summaries, difficult conversations, scope discussions. Writes in your voice, calibrates tone to the situation, treats every message as relationship capital.
Writes brand-aligned content across every format — emails, proposals, blog posts, LinkedIn, case studies, newsletters, website copy. Adapts tone to the channel while staying inside your company's established voice. A LinkedIn post sounds different from a proposal, but both sound like you.
Tracks project status, surfaces risks before they become problems, maps dependencies across people and timelines, keeps everyone aligned. Produces structured status reports — Progress / Risks / Next Actions — where every action has one named owner and every status is honest.
Produces a complete pre-meeting brief so you walk in informed, prepared, and able to send a follow-up within five minutes of hanging up. Works for both prospect meetings and existing-client check-ins.
Full descriptions and example prompts for every skill: Delegation Guide →
These handle multi-step tasks in one pass and keep the system's memory current. The value isn't any one piece — it's the orchestration and continuity across everything you do.
A consolidated end-of-week brief across every active engagement. Run it once on Friday and walk away with a complete picture plus ready-to-send client check-ins. No engagement falls through the cracks.
Runs as a scheduled task at the end of each workday, or manually when you say "wrap up the day." Reviews everything from the session and writes a structured entry — what got done, what was decided and why, what files changed, what's still open, what to pick up tomorrow. Next morning, Claude reads this first, so every session starts where yesterday left off.
Go to Cowork → Scheduled → set daily-log to run at end of day. Important: schedule this within each project — one schedule doesn't run across all projects.
Makes your voice profile more accurate over time by studying real evidence. Paste examples of what Claude wrote versus what you actually sent — the skill extracts the patterns that define your real voice and updates your profile so every skill produces better output going forward.
Don't try to onboard your whole team on day one. Start with yourself. Run it against one real engagement for a week. When it feels like a tool you reach for without thinking, then roll it out to the next teammate. A plugin used well by one person beats a plugin installed poorly by ten.
The plugin doesn't stay static. Four mechanisms make it better with every use.
When you correct a draft's tone — "too formal," "I wouldn't say it that way" — the skill adjusts and offers to save the learning to your voice profile. Next time, it gets it right without being told. This happens automatically in /client-comms, /content-strategist, and /executive-comms.
Every specialist appends a one-line entry to project-log.md after producing output. Next time any skill responds on the same engagement, it reads the log first — so it knows what's been communicated, what's been decided, what's been flagged. You don't have to re-explain.
At day's end, /daily-log captures what got done, what was decided and why, what changed, and what to pick up tomorrow. Every new session starts by reading it — Claude knows exactly where things stand without a re-brief. Decisions are logged with their reasoning, so "why did we do it that way?" always has an answer.
Run /refine-voice periodically with before/after examples — what Claude wrote versus what you actually sent. The skill extracts the real patterns that define your voice and updates your profile. After one session, drafts match significantly better. Recommended at the 30-day check-in.