# Pattern Creator

> Standardized agent pattern creation and validation

- Skill: `gitwalter/pattern-creator` (Agent Skill, multi-file: 15 files)
- Install (CLI): `npx skillmds@latest add gitwalter/pattern-creator`
- Raw SKILL.md: https://api.skillmd.com/api/skills/gitwalter/pattern-creator/raw
- Safety review: pending
- Works with: Claude Code, Claude.ai, OpenAI Codex
- Category: AI & ML
- Author: gitwalter (https://skillmd.com/u/gitwalter)
- Updated: 2026-09-10
- Page: https://skillmd.com/skills/gitwalter/pattern-creator

---


# Pattern Creator

The **Pattern Creator** skill manages the generation and validation of agent patterns. Patterns are meta-definitions used to generate specific agent instances. They reside in `{directories.patterns}/`.

## Standard Structure

Patterns are JSON files that follow the complex schema defined in `agent-pattern.json`. Key sections include:
- `metadata`: Pattern identity (ID, name, category).
- `frontmatter`: Blueprint for the generated agent's metadata.
- `sections`: Blueprint for the agent's markdown content (purpose, workflow, rules).
- `variables`: Parameters to be replaced during generation.

## Process

1.  **Abstraction**: Identify a reusable agent architectural pattern.
2.  **Draft JSON**: Build the pattern object.
3.  **Validate**: Run `scripts/quick_validate.py` (which uses `agent-pattern.json` as its schema).

## When to Use

- When creating a new pattern from scratch
- When improving or refactoring an existing pattern
- When standardizing an pattern to adhere to Factory schemas
- When another skill or agent requests a compliant pattern

## Prerequisites

- Access to the Factory schemas in `schemas/`
- Understanding of the artifact structure defined in this skill
- The `quick_validate.py` script must be available for schema validation

## Best Practices

- Always validate against the schema before finalizing
- Keep the artifact focused and non-redundant with existing ones
- Follow the naming conventions defined in the Factory standards
- Document the artifact's purpose clearly in the description field
- Link related artifacts in the `related_skills` or `related_knowledge` fields