pattern-library-manager

Pattern Library Manager

Purpose

Add, tighten, or document reusable approved patterns and anti-patterns in this bundle without leaking host-project facts into publishable rules.

This skill owns small reusable pattern-library changes: descriptions, bad/good examples, graph links, trigger/output evals, and validation alignment.

When To Use

Use this skill when the user asks to:

• add a reusable approved pattern;
• add a reusable anti-pattern;
• tighten an existing common pattern or anti-pattern;
• add code examples to a pattern or anti-pattern;
• add pattern examples sourced from official documentation or user-provided snippets;
• add eval coverage for a pattern-routing regression;
• update common/approved-patterns.md, common/anti-patterns.md, or common/anti-patterns/** for reusable behavior.

When Not To Use

Do not use this skill for:

• project-specific patterns or anti-patterns; use local-only project/** overlays instead;
• general skill creation unrelated to patterns; use agent-rules-skill-author;
• implementation, bugfix, refactor, visual QA, or review work;
• adding examples copied from private project code into reusable docs;
• adding long third-party code excerpts.

Required Context

1. Read AGENTS.md.
2. Read common/documentation-maintenance.md.
3. Read common/approved-patterns.md or common/anti-patterns.md depending on the requested change.
4. Read the existing target pattern or anti-pattern file when modifying one.
5. Read references/pattern-entry-template.md before creating a new entry.
6. Read references/example-sourcing-policy.md before adding code examples.
7. Read evals/trigger-evals.json or evals/output-evals.json when routing or output behavior changes.

Tool Contract

• Use the project_files capability for repository file reads and writes.
• May use official documentation or trusted maintainer sources to understand a pattern when examples are not supplied by the user.
• Activate openai_platform_docs only when a reusable pattern depends on current OpenAI or Codex behavior.
• Must propose sourced examples to the user before committing them when they come from external material or host-project-specific context.
• Must write original, short examples instead of copying long third-party code.
• Must not install packages, change runtime code, create tests, or modify host-project documentation.
• Must not use Figma MCP.