my prefect server setup
prefect-metrics.waow.tech
python
orchestration
trim curate system prompt — field metadata already covers structure
Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
+7
-47
+7
-47
flows/curate.py
+7
-47
flows/curate.py
···
36
36
37
37
SYSTEM_PROMPT = """\
38
38
you are a dashboard curator for a solo developer's issue tracker.
39
-
given a list of scored items from github and tangled.org, produce a briefing
40
-
with exactly 4 themed sections. group by theme or status, not by source.
41
-
42
-
## tone
43
-
44
-
be honest and proportionate. most days are normal — say so. don't manufacture
45
-
urgency. if nothing is on fire, the headline should reflect that. a calm
46
-
"steady week, nothing blocking" is better than "5 critical items demand
47
-
attention" when it's really just routine activity.
48
-
49
-
reserve words like "critical", "urgent", "demands", "immediate" for genuinely
50
-
exceptional situations — a broken deploy, a security issue, a hard deadline
51
-
this week. routine PRs and stale issues are not emergencies.
52
-
53
-
the title should be 2-3 lowercase words that honestly capture the vibe:
54
-
"quiet week", "steady progress", "a few loose ends", "one thing blocking".
55
-
not every day is a "release crunch" or "bug cluster".
56
-
57
-
the headline should be 1-2 factual sentences. lead with the most useful
58
-
observation, not the most alarming one.
59
-
60
-
## structure
61
-
62
-
the layout is a 2x2 grid — always produce exactly 4 sections.
63
-
keep each section to 4-6 items max — be selective, not exhaustive.
64
-
65
-
section titles should be lowercase, short, descriptive:
66
-
"waiting on review", "getting stale", "small fixes", "just tracking"
67
-
68
-
each item note should be ~10 words of useful context — what it is,
69
-
not why it's supposedly urgent.
70
-
71
-
## visual styling
39
+
given scored items from github and tangled.org, produce a briefing
40
+
with exactly 4 sections. group by theme or status, not by source.
41
+
keep each section to 4-6 items. be selective, not exhaustive.
72
42
73
-
each section has accent and priority fields to control presentation.
74
-
75
-
accent colors — use the one that honestly fits:
76
-
- red: actually blocked or breaking something right now
77
-
- amber: getting old, might need a nudge soon
78
-
- emerald: ready to go, easy to close out
79
-
- sky: background awareness, no action needed now
80
-
- violet: features or ideas, no urgency
81
-
82
-
default to sky or emerald. use red sparingly — maybe once a month.
83
-
84
-
priority — all sections should use "normal" for the 2x2 grid layout.
85
-
86
-
do not set highlight on any items.
43
+
be honest and proportionate. most days are normal — say so.
44
+
don't manufacture urgency. reserve "critical", "urgent", "immediate"
45
+
for genuinely exceptional situations. use red accent sparingly.
46
+
lead with the most useful observation, not the most alarming one.
87
47
"""
88
48
89
49
def make_agent(api_key: str) -> PrefectAgent[Briefing]: