Skip to main content

Guide: Team Leads

You're responsible for your team's AI tooling standards. Workloom gives you the power to define, distribute, and enforce those standards — without chasing people on Slack.

Your Workflow​

1. Define Your Team's Baseline​

Create a package that captures your team's AI configuration standards:

mkdir -p packages/frontend-baseline
cd packages/frontend-baseline

Create the canonical assets:

<!-- instructions/coding-standards.md -->

# Frontend Coding Standards

- Use TypeScript strict mode
- Write tests before implementation (TDD)
- Components use composition over inheritance
- All API calls go through the SDK layer
- Never use `any` — use `unknown` and narrow
<!-- instructions/review-guidelines.md -->

# Code Review Guidelines

When reviewing PRs:

1. Check for type safety first
2. Verify test coverage for new code paths
3. Flag any direct DOM manipulation
4. Ensure accessibility attributes are present

2. Publish as a Draft​

wl push --draft
# → Created draft @acme/frontend-baseline@1.0.0

3. Review and Approve​

Share with your team for feedback. When ready:

wl publish @acme/frontend-baseline@1.0.0
# → Promoted to pending_review

After approval (by you or an org admin):

→ Status: approved
→ Available for workspace assignment

4. Assign to Your Workspace​

Via the web UI or API, add the package to your team's workspace. Every developer bound to that workspace will receive the configuration on their next wl pull.

5. Iterate with Confidence​

When standards evolve:

# Edit your package
# Bump the version
wl push --draft  # → @acme/frontend-baseline@1.1.0
wl publish @acme/frontend-baseline@1.1.0

Previous versions remain available. Teams can pin versions or track the stable channel.

Enforcing Compliance​

CI Drift Check​

Add to every repo's CI pipeline:

- name: AI Config Compliance
  run: wl sync --check

Now if a developer:

  • Deletes a managed file → CI fails
  • Manually edits a managed file → CI fails
  • Falls behind on package versions → CI fails (if workspace revision advanced)

Monitoring Adoption​

The web UI shows:

  • Which workspaces are on the latest revision
  • Which repos have drift
  • Package adoption metrics across the org

Tips for Team Leads​

  1. Start small: One package with core instructions. Ship it. Iterate.
  2. Version meaningfully: Minor version for additions, major for breaking changes (removed instructions change AI behavior).
  3. Use channels: beta for experimental configs, stable for proven ones.
  4. Separate concerns: @acme/security-review and @acme/frontend-baseline as separate packages, not one mega-package.
  5. Document in the package: Your instructions ARE the documentation. Make them clear and specific.
  6. Trust the CI gate: Once wl sync --check is in CI, drift becomes visible and fixable.