Design Best Practice Domain

Architect a new grimoire domain or sub-domain: decide structure, create plugin files, write seed skills, and verify quality before release.

Why This Is Best Practice

Adopted by: Explicit domain architecture standards are used across major knowledge systems — Apache Software Foundation requires new top-level projects to meet maturity criteria before graduation from incubation, npm's scoped package organization (@scope/package) provides consistent namespacing conventions for domain groupings, and the Library of Congress classification system defines explicit criteria for when a topic warrants its own subject heading vs. being nested under an existing one. Impact: Domains without architecture standards become stubs — single files, no maintainer, no coverage plan — that are never completed and pollute discovery results. Apache's structured incubation model demonstrates that explicit domain criteria prevent project abandonment by establishing minimum viability before release. Consistent naming conventions (applied by npm and Wikipedia's category structure) reduce install and discovery errors by preventing naming collisions and ambiguous paths. Why best: Ad-hoc domain creation — vs. following a defined architecture pattern — produces inconsistent plugin configurations, broken install paths, and stub domains that confuse contributors. A domain architecture checklist ensures every new domain is complete, discoverable, and maintainable before users encounter it.

Sources: Apache Software Foundation incubation policy, npm scoped packages documentation, Library of Congress Classification Outline

Steps

1. Qualify the domain

A new top-level domain qualifies if ALL three are true: