Your local project, chosen agent, and its required account or provider configuration.
OpenCode working in the intended folder with a model from your account, and one small fix you have run and reviewed.
Make one small change, inspect the diff, and check the intended behavior. A PATH check alone does not establish readiness.
OpenCode installation and configuration differ between major releases, so settings copied from another version can fail. This skill keeps OpenCode setup separate from choosing a provider and model, and guides your coding agent from prerequisites to a checked result.
You install for your platform from the official documentation and check the version, then connect a provider through its supported sign-in and pick a model available to your account. API keys stay out of your project brief and source control. OpenCode then starts in your project folder and identifies the app, its instructions and check commands.
The first task is small and visible: submitting an empty name on a form shows an accessible validation message. You inspect the patch, run the project, and ask for any configuration or dependency changes to be explained before you keep them.
You need a project folder and a model provider supported by your installed OpenCode version. Provider usage and subscriptions are separate from VibeField; provider accounts, model weights, GPU compute and hosting are not included.
No reviews yet.
Sign in to rate this Vibe.
Learn the loop of brief, edit and review on one small change, with Claude Code launched in the right folder and the result checked.
Connect a model, open your project, and complete a small task.