---
name: azur-codirector-workflow
description: |
  Azur's operating mode — co-director of Ghost Protocol (Pvt) Ltd alongside
  Ryan. Generalist who wears business / design / engineering hats as the
  moment requires. The hat in play changes per project — a client kickoff
  is business mode, polishing a landing page is design mode, fixing a
  Cloudflare config is engineering mode. Trigger when she says "spin up a
  client", "review the design", "fix the deploy", "what should we ship",
  or any work that needs cross-discipline coordination.
argument-hint: "[business | design | engineering | autodetect]"
user-invocable: true
---

# Azur's Co-Director Workflow

You're working with **Azur** — co-director of Ghost Protocol (Pvt) Ltd
alongside Ryan. She's a **full-stack generalist**: depending on what the
moment needs, she's running business ops, doing design review, or shipping
engineering changes herself. Don't assume a single discipline.

The hat in play depends on what she's asking about. Read the cue and adapt.

## Hat detection — auto-pick a mode

| Cue she gives | Hat | Defaults |
|---------------|-----|----------|
| "Set up a new client" / "send a proposal" / "follow up on the invoice" / "the meeting is Tuesday" | **Business** | Use Stripe / Paddle, generate Wyrm invoices, write proposals from `client-proposals-business-dev` skill, track time via `wyrm_hours_report` |
| "Review the design" / "this doesn't feel right" / "make the hero pop" / "what's our brand again" | **Design** | Pull project design tokens from Wyrm, reach for `frontend-design` skill, match Constitution rule II palette unless project overrides, prefer framer-motion for transitions |
| "Fix the deploy" / "the build is broken" / "why is X slow" / "rerun the pipeline" | **Engineering** | Run `npm run build`, surface error in plain English, dig into the actual stack trace, check Cloudflare logs if it's a deploy issue |
| Ambiguous | **Ask once** | One short question: "is this a client / design / engineering thing?" — then commit |

She'll often switch mid-conversation. When she does, **switch with her** —
don't keep replying in engineering mode if she's clearly moved to client ops.

## Business mode

For client work, proposals, deliverables, invoicing:

- **Default monetization stack:** Stripe for Stripe-supported countries;
  Paddle for everywhere else (Sri Lanka isn't direct-Stripe).
- **Time tracking lives in Wyrm.** Sessions become hour entries. Use
  `wyrm_hours_report` for per-project totals, `wyrm_invoice_generate` for
  markdown invoices. **Never** lose hours — every session worked on a
  client project should be reflected.
- **Client onboarding pattern:** see [[client-acquisition-pipeline]] and
  [[client-proposals-business-dev]] skills. Don't reinvent.
- **Sri Lankan clients first.** The agency portfolio (Vision Works,
  Upali's, Dankotuwa, Moye Moye Ella, biofuellanka) is the local market.
  Pricing, terms, and timelines are tuned to LKR + Sri Lankan business
  norms — see [[sri-lanka-market-intelligence]] when context matters.
- **Communication style:** professional but warm. Match Ghost Protocol's
  voice — confident without being corporate-bland.
- **Proposals → Paddle/Stripe checkout link** wherever possible. Reduce
  friction between "yes" and money received.

## Design mode

For visual work, brand consistency, UI craft:

- **Constitution rule II is the floor** — teal `#00B89F` primary,
  red `#ff5a55` critical, Inter sans, h1 weight 900 / 2.5rem /
  -0.02em, **never black-and-green**. This is the Dragon-stack default
  but applies to agency work too unless the client has their own brand.
- **Per-project design tokens live in Wyrm.** Use `wyrm_token_set` /
  `wyrm_token_get` (new in 5.9.0) to record palette / type / spacing /
  motion per project. New work checks tokens first.
- **Reference library lives in Wyrm.** Use `wyrm_reference_add` to clip
  URLs / screenshots she's inspired by. Builds a per-project mood board
  over time.
- **Skills to reach for:** [[frontend-design]] (built-in plugin),
  [[clean-design-language]], [[designer-grade-theming]],
  [[startup-studio-design-language]], [[professional-ascii-art]] (for
  terminal-product mascots like the Wyrm one).
- **Animation defaults:** framer-motion for state transitions, lenis for
  smooth scroll, GSAP only when framer-motion can't do the thing.
  Motion should serve content, not perform.
- **Mobile-first** for agency work. Sri Lankan internet leans mobile;
  desktop is often the second-class viewport. Test at 360px and 768px
  before shipping.

## Engineering mode

For fixes, deploys, infrastructure:

- **Stack is Next.js 16 / React 19 / TS / Tailwind / shadcn / Cloudflare
  Pages.** Same as Ryan's and Sachintha's. See [[ryan-founder-workflow]]
  for cross-product context.
- **Plain-language debugging.** When something's broken, explain in
  English what's happening, then fix. Skip the jargon unless it's the
  actual word she needs to learn the next time it happens.
- **Cloudflare-first.** Pages auto-deploys from main, `_redirects` and
  `_headers` files handle routing / security. If a build fails, check
  Cloudflare deploy logs in dashboard → Workers & Pages → Deployments
  → failed run → build logs.
- **Skills to reach for:** [[cloudflare]] (plugin), [[mcp-server-dev]],
  [[buddy-protocol]], [[wyrm-release-workflow]] for npm-published
  packages, [[dragon-spec-author]] for non-trivial changes.
- **Build hygiene:** always run `npm run build` after a meaningful
  change. Catch errors before push, not after Cloudflare deploys break.

## What both modes share

- **Wyrm everywhere.** Every project gets a `.wyrm/` folder; every
  session priming pulls the right context. See [[wyrm-project-bootstrap]]
  for the 30-second setup.
- **Spec before code for ≥4h work or ≥2-repo changes** — constitution
  rule VI applies to her too. See [[dragon-spec-author]].
- **Cloudflare-Pages auto-deploy** — ghosts.lk and all client sites
  live there. Push to main, deploy in ~60s.
- **Squash-merge always.** Keeps main linear; spec-task IDs in commits
  stay readable.
- **Plain English when explaining** — she's technical but also wears
  the business hat. Don't over-jargonize.

## Common cross-mode flows

**Client kickoff:**
1. Business: write proposal, get signed, Stripe/Paddle invoice
2. Engineering: bootstrap Next.js repo, wire Cloudflare Pages, set up Wyrm
3. Design: set project design tokens, build first hero, get client approval

**Bug report from a client:**
1. Engineering: reproduce, fix, build, deploy
2. Business: communicate the fix to the client in plain English, no jargon
3. Wyrm: `wyrm_failure_record` so the same bug doesn't ship twice

**Quarterly review of the portfolio:**
1. Business: `wyrm_hours_report` and `wyrm_invoice_generate` per client
2. Design: which sites look stale? Which need a refresh?
3. Engineering: which deps are 6+ months out of date? Which CI is red?

## Don't lock her in — innovation guardrails

This skill captures **current** practice. The agency / product / brand
landscape evolves; so should this.

- **Defaults are starting points.** If a client genuinely needs Astro
  for a content-heavy site or Tauri for a desktop app, deviate.
  Don't reflexively pick Next.js.
- **Surface emerging tools.** "Motion One is a smaller alternative to
  framer-motion; want to try on the next client?" — let her decide.
- **Flag pattern fatigue.** If five agency clients in a row got the
  same hero layout, suggest a different approach for the sixth.
- **Skills are living documents.** When her habits shift (new
  monetization stack, new design language, new framework), update this
  skill in the same PR. Don't let it become a museum piece.

## What NOT to do

- ❌ Don't assume she's in engineering mode just because there's code on
  screen. Sometimes the "code change" is actually a client decision in
  disguise.
- ❌ Don't run a long requirements interview before starting client
  work. Default to Ghost Protocol's standard stack + agency template,
  refine as the client reacts.
- ❌ Don't push for over-architecture. She and Ryan ship a lot solo;
  monorepos / microservices / Turborepo introduce more friction than
  they remove for a two-director team.
- ❌ Don't surface every dep update as a question. Batch them via
  Dependabot (see [[sachintha-creative-stack]] for the template).
- ❌ Don't lose hours. Every session worked on a client should leave
  enough trace in Wyrm for `wyrm_hours_report` to bill it.

## When you don't know

Ask one short question to disambiguate the hat. Don't ask "what should I
do" — ask "is this client-facing, design, or under-the-hood?" Then commit
and ship.