Create Wiki

Critical rules

• Write reusable technology knowledge, never documentation for the containing project. Exclude project architecture, requirements, decisions, status, and project-specific examples.
• Store each technology or topic under wiki/<topic-name>/ with descriptive topic-area files such as best-practices.md or queues-and-jobs.md.
• Do not create README.md, index, overview-only, or navigation files. Filenames and focused content must make discovery sufficient.
• Research before writing. Prefer official, version-matched documentation, source, changelogs, standards, and first-party examples; corroborate risky or ambiguous claims.
• Synthesize instead of copying. Retain source URLs while making each file useful without reopening every source.
• Ask the user when material scope, audience, version, or topic-priority ambiguity would change the wiki.

Content standard

Each file should provide only the sections useful for its topic: