AI Design Patterns

The system

Patterns organise action

A pattern captures a recurring problem, its competing forces and a reusable response—at a level that survives tool changes but remains specific enough to guide work.

From need to accountable action

The library separates layers that are often collapsed. A pattern is not a prompt. A module is not a pattern. A generated output is not an approved decision.

  1. Design patternRecognise the recurring problem and organising response.
  2. WorkflowOrder the stages, hand-offs, failures and human decisions.
  3. ModuleSelect a reusable capability with a stable input–operation–output contract.
  4. SubmoduleChoose the focused component task needed now.
  5. Prompt templateInstantiate a bounded instruction with authorised context.
  6. Human decisionInspect evidence and outputs; approve, correct, reject, pause or escalate.

Two ways in

The guided wizard offers editorial navigation through three controlled questions. Explore lets you move through explicitly recorded relationships or scan the equivalent list.

Publication scope

This read-only website is generated from the public, accepted pattern system in the repository. It publishes the canonical pattern, workflow, module, submodule and glossary layers needed to understand and use the system. Author-review documents, source extracts, working research records, spreadsheets and local QA material are outside the public site boundary.

The repository remains the editorial source of truth. Search indexes, atlas coordinates, relationship counts and wizard mappings are disposable or reviewable navigation products; they do not replace canonical content.