Document Pattern

Create one project skill and one linked convention for the requested code pattern.

Inputs

Require a pattern name. Convert it to lowercase kebab case as [patternName].

Gather these facts before writing:

• Pattern purpose and use cases.
• Existing implementations that represent the pattern.
• Required structure, naming, dependencies, registration, tests, and verification commands.
• Existing project conventions that constrain the pattern.

Ask for missing facts. Do not invent project-specific paths, APIs, commands, or rules.

Outputs