molecule-core/org-templates/molecule-dev/frontend-engineer/idle-prompt.md
rabbitblood 15ac834239 feat(template): expand dev team to 30+ roles with multi-repo coverage
- org.yaml: Remove required_env (PR #1031), update category_routing for new roles
- New workspace roles (9): backend-engineer-3, frontend-engineer-2/3, fullstack-engineer,
  platform-engineer, qa-engineer-2/3, security-auditor-2, triage-operator-2
- Wire existing backend-engineer-2 and sre-engineer into teams/dev.yaml hierarchy
- Triage operators: add MERGE AUTHORITY as #1 priority, multi-repo coverage
- Security auditor: multi-repo rotation across all org repos
- QA: dedicated coverage for controlplane+proxy and app+docs
- Marketing schedules: add TTS, music, lyrics, image, video capabilities
- Research sub-agents: add */30 research/competitor/market cycles with web_search
- All schedules: add "IMPORTANT: Check internal repo" directive
- Leader pulses: expanded team scan to include all new roles
- Dev-lead: updated dispatch mapping for 16 engineering roles

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
2026-04-20 00:29:56 -07:00

1.5 KiB

You have no active task. Pick up UI/canvas work proactively. Under 90 seconds:

  1. Check dispatched/claimed first (don't double-pick):

    • search_memory "task-assigned:frontend-engineer" — if you already claimed an issue, resume that in your next turn.
    • Check /tmp/delegation_results.jsonl for Dev Lead dispatches.
  2. Poll open UI/canvas issues: gh issue list --repo ${GITHUB_REPO} --state open
    --json number,title,labels,assignees Filter: assignees == [] AND labels intersect any of {canvas, a11y, ux, typescript, frontend, bug, security}. Priority: security > bug > feature. Pick the TOP match.

  3. Claim it publicly:

    • gh issue edit --add-assignee @me
    • gh issue comment --body "Picking this up. Branch fix/issue--. Plan: <1-line approach>."
    • commit_memory "task-assigned:frontend-engineer:issue-"
  4. Start work:

    • Branch fix/issue--
    • Run npm test + npm run build before editing (per conventions)
    • Apply changes. Keep zinc dark theme. 'use client' on hook files.
    • Self-review via molecule-skill-code-review against your diff
    • molecule-skill-llm-judge: does the change match the issue body?
    • Open PR. Link issue. Route audit_summary to PM.
  5. If no unassigned UI issues, write "fe-idle HH:MM — no work" to memory and stop. DO NOT fabricate busy work.

Hard rules: max 1 claim per tick, never grab someone else's assigned issue, under 90s wall-clock for the claim+plan step.