Pattern Harvester (PHV) Prompts¶

Six prompts for the Pattern Harvester — the docs_as_code persona at Zachman cell ENTERPRISE/WHAT that harvests recurring structural patterns across the 164-persona catalog, 312 actions, 33 scenarios, and 27 Streamlit apps, then proposes pattern catalog additions.

PHV is how FCC prevents "pattern dark matter": patterns that recur but never get named. A named pattern is a reusable pattern.

Context for Claude¶

As PHV you scan repo-wide, cluster by structural similarity, and name candidate patterns. You work alongside TLDR (for cross-layer pattern sync) and ZCA (for Zachman-cell grouping).

Prompt 1: Harvest a workflow pattern¶

PHV, scan the 7 workflow graphs (5-node, 20-node, 24-node, 55-node
extended_84, + 2 solution-level EAIFC). Identify:
- 3 recurring node pairs
- 2 recurring subgraph shapes
- Any un-named pattern worth lifting to docs/patterns/

Expected outcome: pattern roster + lift recommendations.

Prompt 2: Persona-interaction pattern atlas¶

Scan the cross_reference.yaml matrix. Identify 5 recurring
interaction patterns (e.g., "upstream + peer + downstream triad",
"sentinel pair"). For each, name, describe, cite 2 examples.

Close with a "pattern taxonomy" tree suitable for
docs/personas/archetype-atlas.md.

Expected outcome: pattern atlas.

Prompt 3: Streamlit app pattern survey¶

27 Streamlit apps live under apps/streamlit/. Survey them and
name the 4 recurring UI patterns (e.g., "left-nav + center-graph +
right-inspector"). For each pattern:
- Example apps using it
- Strength / weakness
- Recommended when-to-use

Expected outcome: UI pattern survey.

Prompt 4: Anti-pattern detection¶

Anti-patterns are patterns worth *not* repeating. Harvest the repo
for 3 anti-patterns around:
- Persona YAML authorship
- Workflow graph scaffolding
- ADR drafting

For each: example, why it is an anti-pattern, corrective pattern.

Expected outcome: 3 anti-patterns + correctives.

Prompt 5: Pattern promotion ladder¶

For a candidate pattern, what is the promotion ladder?
- Observation (3 uses)
- Candidate (documented)
- Accepted (adopted in catalog)
- Deprecated

Draft the ladder + adoption criteria per step.

Expected outcome: promotion ladder.

Prompt 6: Cross-project pattern¶

Collaborating with VDS: identify 2 patterns that appear in both
FCC and ATHENIUM. For each:
- Pattern name (proposed)
- Evidence across both repos
- Owner for cross-project catalog entry

Expected outcome: cross-repo pattern candidates.

Persona YAML: src/fcc/data/personas/pattern_harvester.yaml
Related prompts: persona-tldr-prompts.md, persona-zca-prompts.md, archetype-evolution-guide.md
Planned: docs/personas/archetype-atlas.md (v1.5.3 Pool D1)