project-config

To load project defaults at startup, place a .silverbee.json file in your working directory. The system automatically reads it to preload fields like domain and language, minimizing repeated prompts for initial configuration.

Automating workflow configuration involves centralizing settings in a local JSON file. By defining defaults for competitors and geo in .silverbee.json, downstream skills automatically retrieve these values, ensuring a consistent starting state across workflows.

Configuration precedence enforces a strict priority order: user input wins, followed by command arguments, and then the JSON config file. This ensures that direct user prompts always override the defaults loaded at startup.

Yes, you can use optional fields in your JSON config because the system treats all fields as optional. It provides sensible fallbacks for missing values, allowing downstream skills to proceed smoothly even when specific defaults are omitted.

You can define fields such as domain, competitors, geo, and language in your JSON file. These preloaded defaults allow workflows to proceed with minimal prompts by providing the necessary contextual information at startup.

You face repeated prompts because you lack a centralized configuration file. By creating a .silverbee.json file with default project parameters, the system automatically preloads these values, eliminating the need for manual entry.