[Fleet Execution] Add Tier 2 Workflow Agent Skills

[jules-fleet]

Objective

Create Tier 2 Agent Skills covering workflow-based iterations, specifically design-iteration and design-system-extraction, establishing patterns for refinement loops and config reconciliation.

Code-Level Diagnosis

Code path: packages/sdk/examples/
Mechanism: Reusable workflow skills for generic iteration tasks are not documented.
Root cause: Absence of explicit workflow directives (e.g. SKILL.md) guiding agents on evaluating generated output and resolving conflicts (like merged Tailwind tokens).

Current Implementation

// Missing workflow iteration skills

Proposed Implementation

Files to modify: Scaffold directories for design-iteration and design-system-extraction including SKILL.md rules, helper scripts, and README.md.

Integration (Before -> After)

+ packages/sdk/examples/design-iteration/SKILL.md
+ packages/sdk/examples/design-iteration/README.md
+ packages/sdk/examples/design-system-extraction/SKILL.md
+ packages/sdk/examples/design-system-extraction/scripts/extract-tokens.ts
+ packages/sdk/examples/design-system-extraction/README.md

Test Scenarios

1. Execute bun run scripts/extract-tokens.ts -> Evaluates and merges disparate style objects.

Target Files

• packages/sdk/examples/design-iteration/SKILL.md
• packages/sdk/examples/design-iteration/README.md
• packages/sdk/examples/design-system-extraction/SKILL.md
• packages/sdk/examples/design-system-extraction/scripts/extract-tokens.ts
• packages/sdk/examples/design-system-extraction/README.md

Boundary Rules

Restrict your modifications exclusively to the files listed in the Target Files section. Ensure your source changes are entirely backward-compatible if unowned tests outside your boundary fail. Retain all existing file names and locations outside your explicitly declared target list.

---

Fleet Context

• Source: jules:session:13713548963527251485
• Link: https://jules.google.com/session/13713548963527251485