When AI agents publish HydePHP views they publish everything in that category and you end up with bloat. So thinking if we can make the interactive publisher easier for AI to use. Maybe set output if an AI is detected to list all views + their descriptions, and then add a command option to publish a single file.
That way, if the user asks an agent to publish the footer component the agent can run php hyde publish:views --list (or optionally php hyde publish:views --list | grep footer) and then for example php hyde publish:views --path=resources/views/vendor/hyde/layouts/footer.blade.php
When AI agents publish HydePHP views they publish everything in that category and you end up with bloat. So thinking if we can make the interactive publisher easier for AI to use. Maybe set output if an AI is detected to list all views + their descriptions, and then add a command option to publish a single file.
That way, if the user asks an agent to publish the footer component the agent can run
php hyde publish:views --list(or optionallyphp hyde publish:views --list | grep footer) and then for examplephp hyde publish:views --path=resources/views/vendor/hyde/layouts/footer.blade.php