Skip to content

Promote to Pattern

Explicit gate from work-thinking (or a public source) into the personal patterns corpus. Never auto-sweep.

When to use

  • "Promote this design" / "file this as a pattern".
  • Capturing AWS Well-Architected / opea.dev / similar public prior art into the same schema.

What you produce

  • A draft using knowledge/patterns/TEMPLATE.md.
  • After approval: knowledge/patterns/<slug>.md and an optional AnyType Pattern pointer in Agent space.
  • Audit-log row.

Procedure

  1. Point at the source (workspace file, chat excerpt, or public URL).
  2. Draft the template sections. For internal/work sources:
  3. Names → roles; accounts/VPC/IP → placeholders; strip customer nouns and screenshots.
  4. Note remaining-risk (what might still identify a tenant).
  5. Public sources skip IP strip; still use the same headings.
  6. Topics from topic-tags.json. Unknown → ask.
  7. Show the draft. Do not write until the user approves.
  8. Write knowledge/patterns/<slug>.md. Do not overwrite an existing slug without asking.
  9. Optional: create an AnyType Pattern pointer in Agent (not Work space) per object-types.md. Body stays in markdown.
  10. Offer cd patterns && uv run patterns index so the MCP sees it.
  11. Audit log: action write, rationale promote-to-pattern.

Anti-patterns

  • Don't index Work-space dumps or data_root/lab/**.
  • Don't skip the approval step.
  • Don't put the pattern body only in AnyType.