Project agent instructions

Use agreed requirements, technical decisions, and the existing repository to write only stable, non-obvious guidance. For a targeted AGENTS.md edit, update the affected instructions directly; do not require an installer, new PRD, or full interview. Keep progress in the project's memory/handoff file rather than the always-loaded rules.

For initial Vibe Workflow setup, use the configured manifest paths. If the vibeworkflow CLI is available, inspect npx vibeworkflow --dry-run --json and initialize within the user's authorization. Preserve existing files; replacement flags are for intentional replacements whose affected files have been reviewed. The CLI installs files directly, not into a new templates/ directory.

Fill relevant placeholders from known decisions. Keep task-specific procedures in skills or references and load them only when relevant. Distinguish local implementation from external sends, production changes, and new access. Do not enable broad tool permissions just to make setup convenient.