9 crews · workforce v1.0.0 · ruleset v0.4.0

12 specialists. 55 skills. One workforce.

Most skill packs hand you a folder and leave you to work out which file to open. This one ships the specialists too: they own a domain, carry a toolbelt, and know what to run first. Product, design, marketing, sales, finance, ops and legal, plus coding rules tailored to your stack.

workforce - sync
npx @ndakita/workforce-sync
Rules: v0.4.0 (cursor, 10 modules) current
Skills: v1.0.0 -> v1.1.0
wrote 58 files, now on v1.1.0
$

Three layers, one bundle

A skill on its own does not know when to fire or what to run first. That is what the middle layer is for.

10

Rules

always in context

Invariants that constrain every edit. Verify the webhook signature. RLS on every table. These are here rather than in a skill because nobody asks for them at the moment they are writing the vulnerable line.

.cursor/rules/

12

Specialists

on delegation

Own a domain, carry a toolbelt, and know the order to use it in. Ask for a design check and the Frontend Architect captures the rendered page before it audits anything.

.claude/agents/

55

Skills

on demand

The capabilities themselves, across 9 crews. Loaded only when the work calls for them, so installing all of them costs nothing until one fires.

.claude/skills/

Example: "design-check my site"

orchestrator routes to Frontend Architect which runs webapp-testing to ui-ux-pro-max to frontend-design to webapp-testing

Capture how it actually renders, audit that, fix by severity, then verify. Run the audit before the capture and you are reviewing source code instead of an interface.

Build your bundle

Pick your skills and the specialists who use them come with it. 14 skills are free, including at least one from every crew, no signup.

1

Skills

55 across 9 crews, loaded on demand

Your crew

derived from your skills, not picked

A specialist ships when you own a tool it uses. It knows which of its tools to reach for and in what order, which is the part a bare skill cannot tell you.

  • Orchestrator3/3 tools

    Deciding which specialist a task belongs to, and refusing to start on a vague brief.

    When any request that will take more than a single edit:

    superpowers to superpowers

  • Frontend Architect2/7 tools

    Everything a user sees: layout, hierarchy, states, responsive behaviour, motion, and visual assets.

    When asked to design-check, review, or critique something already built:

    webapp-testing to ui-ux-pro-max to frontend-design to webapp-testing

2

Your stack

not listed? pick Other and type it
3

Always-on rules

in context for every edit, not just when asked

The whole business, not just the code

Most skill packs stop at engineering. This one covers what to build, how to sell it, what to charge, and what to sign - the parts that actually decide whether the code was worth writing.

Routing, not just a folder of files

Every skill has an owning specialist, and every specialist has ordered workflows. You describe the job, not the filename. Nothing is left for you to wire up.

Works in any AI editor

Plain markdown throughout. Rules load natively in Cursor, Windsurf, Copilot and Cline, with the routing table embedded. Claude Code additionally gets real subagents with their own context.

Simple pricing

Start free. Upgrade when you want the premium modules and always-current updates.

Free

$0

  • 14 skills - at least one from every one of the 9 crews
  • All 6 curated Developers installs
  • The specialists who own those skills, with their workflows
  • Orchestrator + Frontend rule modules
  • Unlimited generations, no signup
Build free

Pro

$8/mo

  • Everything in Free
  • The remaining 41 skills - all 55 across every crew
  • All 12 specialists with full toolbelts
  • 8 Pro rule modules - backend, revenue, security, testing, performance, SEO, a11y & deployment
  • Always-current updates as tools change
  • New skills & crews as they ship
Go Pro