voice-before-structure

To prevent boilerplate in your README and plugin descriptions, ground them in your project's voice by reading 2-3 philosophy documents and drafting artifacts using the established terminology and tone.

Voice grounding for marketplace metadata and manifests is the process of drafting documentation artifacts using your project's established design language, ensuring consistent tone and preserving project identity across ecosystem-level docs.

Yes, you can write plugin descriptions that match your project philosophy by referencing the project vocabulary and applying the established voice from your design language to draft the metadata.

You keep a consistent tone across ecosystem-level documentation by grounding manifests and metadata in your project's voice, referencing project vocabulary to ensure all artifacts reflect the same design language.

Yes, you need 2-3 philosophy documents to ground your README in your project's voice, as these documents provide the project vocabulary and design language required to draft authentic artifacts.

You should ground your project documentation instead of using generic templates whenever identity matters, specifically for manifests, READMEs, plugin descriptions, and marketplace metadata where preserving project voice is critical.