check-existing

To check for existing files and templates before creating new code, scan your project directories for exact filename matches, locate available templates in bereshit/word/seed, and identify similar structural patterns to reuse or copy-and-modify instead of starting from scratch.

The best way to prevent file duplication in development workflows is to perform directory scanning for exact filenames and similar patterns first, then decide whether to edit an existing resource, copy a template, or create a new file only when nothing similar exists.

To find and reuse existing templates for documentation and configuration tasks, search within bereshit/word/seed for available template files, copy the matching template, and modify it to follow established project patterns rather than creating a new file.

You should create a new file instead of reusing existing resources only when directory scanning confirms that no exact matches, available templates, or similar structural patterns exist within your project to copy or follow for your current task.

Yes, this workflow discovery process applies directly to bereshit project configurations, applying template-based coding, documentation, and configuration tasks by scanning bereshit/word/seed to find exact matches, templates, or patterns to reuse.