Set the Standards. Save the Playbook.
Brief your team once. Two new ways to make sure they remember - and run the same play twice as fast.
Picture briefing a great new hire on day one. You walk them through how you write, how you handle clients, the three things you never want to see in a draft. They get it. They run with it.
Now picture re-doing that same brief every Monday morning, for the rest of your career. That's how most AI tools work. Today, your Flockx team gets two new tools that fix it.
The Short Version
Rules are the standards your team follows on every project. Your brand voice, your formatting, your hard nos. Skills are the saved playbooks your team runs by name. The newsletter draft. The client onboarding sequence. The Friday wrap. Set them once. Reuse them forever.
Why a Team Needs Both
A real team has shared standards and shared playbooks. The standards keep everyone's output sounding like one company. The playbooks keep the team from reinventing the wheel every Tuesday at 4pm.
Up to now, you've been giving your AI team that brief in the chat, every time. Re-explaining the voice. Re-pasting the structure. Re-listing the things you don't want them to do. Rules and Skills mean you do it once, and everyone, every project, just knows.
Rules: The Standards Your Whole Team Follows
A Rule is a short, plain-English standard. One sentence. The kind of thing you'd write on a whiteboard for a new hire on their first day. Your team reads it, holds it, and applies it to everything they touch from then on.
Rules can apply to your whole team, or to one team member. You might want Clara to always end blog posts with a single reflective question. You might want everyone, across the board, to never use the word “leverage” in a draft.
Rules creators are saving today
- Brand voice. "Write like a friend at a kitchen table, not a panelist on a podcast."
- Structural defaults. "Every newsletter starts with a hook, ends with a clear call to one action."
- Hard nos. "Never use the word 'unlock'. Never start a sentence with 'In today's world'."
- Working preferences. "Send drafts as outlines first, full prose only after I approve."
- Audience guardrails. "Assume the reader is smart, busy, and has read the last newsletter."
Rules are the things you'd say in a hiring conversation and then never want to repeat. Your team holds them so you don't have to.
Write Rules the way you'd onboard a new hire
Don't try to anticipate every edge case. Don't write paragraphs. Pick the five to ten things a great new hire would need to know on day one to sound like part of the team. Save those. Add more as you notice what keeps coming up.
Skills: The Playbooks Your Team Already Knows by Heart
A Skill is a saved play. Give it a name, write the steps, and from then on you can ask any team member to run it without rebuilding the brief from scratch.
Skills work like the SOPs a small agency would write up after their third repeat client. The first three times you ran the play, you figured it out. The fourth time, you wrote it down so the next person on your team could run it the same way without you in the room.
Skills creators are saving today
Weekly newsletter draft
Open the newsletter folder, scan the week's published content, write a 600-word draft in our voice, end with a single CTA.
Launch announcement pack
One LinkedIn post, three tweets, one Instagram caption, one short email. All ready for the same launch, all hitting the same key points.
Client onboarding email
Pull the client's preferences from our notes, write a personalized intro email, attach the welcome packet, schedule the kickoff hold.
Friday wrap
Three things the team finished this week, one thing that slipped, one thing I want to think about over the weekend. In my voice. Five sentences max.
Each one of those used to take a paragraph of setup. Now you ask Clara to run the newsletter draft, or Sage to run the Friday wrap, and the play moves while you do something else.
The Magic Is in the Stack
Rules and Skills are good on their own. Together, they're a small operations system for one person.
Your Rule says “write in my voice, never use ‘unlock’.” Your Skill says “write the weekly newsletter from this week's posts.” You ask Clara to run the newsletter Skill. She runs the play, in your voice, without ‘unlock’ anywhere on the page, without you needing to say it again.
The Rule is the standard. The Skill is the play. Stacked, you get the same output a small agency would deliver, in the time it takes to type three words.
When to Use Each
Make it a Rule when…
- You want it true on every project, every time
- It's about voice, format, or what's off limits
- You'd want a new hire to know it on day one
- You'd hate having to remind your team again
Save it as a Skill when…
- You ask for it more than three times a month
- It has a clear shape: input, steps, output
- You'd rather call it by name than re-brief it
- It deserves a name, not a paragraph
How to Add a Rule
Open Workbench HQ
Click Add Rule
Pick the scope
Save and test
How to Save a Skill
Find the brief you keep retyping
Open Skills in Workbench HQ
Name it like you'd actually say it
Write the steps
Run it from the chat
Best Practices We've Picked Up
Start with the things you've already said three times
Scroll back through your last week of Flockx chat. Every time you find yourself typing “actually, can you…” or “next time, please…” that's either a Rule or a Skill trying to get out. Save it before you lose it again.
Keep them named like you'd say them out loud
“Friday wrap” beats “Weekly retrospective summary report.” You are going to call this Skill by name in 14 seconds when you are walking into a meeting and need it to fire. Make the name something a tired version of you can remember.
Save Skills you do at least three times a month
One-off briefs are not Skills. The bar for saving a Skill is: you have done it three times, you can already see when you will do it next, and you want it to be the same shape every time. If something only happens once, just write it in chat.
Audit them once a quarter
Open your Rules list. Open your Skills list. Delete the ones you don't use. Sharpen the ones that work. The team gets better every time the standards and playbooks get cleaner. Two hours a quarter is enough.
Let your team coach you back
If a Rule keeps tripping the team up, the Rule is wrong, not the team. If a Skill keeps producing something that's 80% right, look at the steps, not the team member. Your standards and your playbooks are written by you, for you. They get better the same way your work does, by editing in public with the people who use them.
Where This Fits in the Bigger Picture
You've already got a team that remembers the moves of every project. You've got a brand voice setup that points everyone in the same direction. Rules and Skills are the next layer: the standards and playbooks the team works by, not just the things they remember.
Memory is the past. Rules describe the present. Skills make the future repeatable. Together, that's a team you actually run, instead of a team you keep re-introducing yourself to.