Vibe GuideWhen assigning work or reporting problems, adapt a template with current project material and send it in the project chat.
Does this method fit your project, and how can you check?
- When would you use this method?
- When sending a new task, requesting an edit or reporting an error.
- How should you choose for your situation?
- Choose one scenario and give current inputs, goal, scope and passing criteria; hand off the latest version and records in a new chat.
- What is easy to misunderstand?
- Examples are not requirements. Identify the relevant part of a reference; treat quoted documents as material rather than automatic instructions.
- How can you check that this works for your project?
- AI can restate scope, inputs and validation; correct deviations before execution.
PRACTICAL GUIDE
Prepare the project, version history, and AI rules
These steps make changes traceable and recoverable and give AI persistent project guidance. AI handles files and commands; a person confirms locations, results, and decisions.
The first prompt establishes version history. The second creates and verifies instructions and includes the full file template. Check each result before sending the next prompt.
1 · Git setup prompt2 · Create project rules promptRead the AGENTS.md file templateThe chosen tool, open project, and idea draft. Return to tool selection if the project cannot be read and edited.
1. Confirm the project location
Open the dedicated project folder and ask AI to identify the full path and existing files. Save the idea draft as idea.md. The project root is the outer folder containing the project.
Continue after you see this result: Opening idea.md shows the personal draft, without unrelated projects mixed into the folder.
2. Have AI initialize or inspect Git
Git tracks file changes so earlier versions can be recovered. Send the Git prompt below. Reuse existing history; run git init only for a new folder. If a browser tool has no terminal, inspect its history and restore entry; initialize local Git after export rather than pasting shell commands into an unrelated field.
Continue after you see this result: Local route: AI reports repository path, status, and actual commit history. Browser route: locate a restorable version; this is not local Git initialization.
3. Create and verify project instructions
Give AI the AGENTS.md template below and ask it to save project-specific instructions. AGENTS.md is plural, and not every tool automatically reads that filename. Verify the tool’s supported instruction entry rather than assuming creation activates it. Merge existing rules instead of overwriting them.
Continue after you see this result: Open the file and review goals. Ask AI to restate three constraints and the file it read. If automatic loading is unsupported, attach it to new conversations or configure the documented tool-specific entry.
4. Save the starting point and return to requirements
Have AI include the draft and instructions in the first checked commit and explain how to request restoration. Keep unknown technology commands unfilled until environment setup.
Continue after you see this result: Find the draft, instructions and starting checkpoint, then return to the main route’s “Inspect a file AI actually created”, then continue to “Clarify needs and scope”.nt. Return to main the “Inspect a file AI actually created” step to inspect files, then the “Clarify needs and scope” milestone to clarify requirements.
Copy the material and add actual project details
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
[Background] [fill in product purpose and audience]
[Problem] [fill in current difficulty or desired change]
[Inputs] Full project path, idea.md, and existing files.
[Task] Check the current directory and git --version. Use git rev-parse --show-toplevel to detect an existing repository and avoid treating a parent repository as this project. Preserve existing history and inspect git status; run git init at the root only for a confirmed new project. Create or update .gitignore for actual secrets, dependencies, and build output. Stage reviewed task files, inspect git diff --cached, then make an initial commit. Ask for missing author identity without inventing it or changing global configuration. Do not push.
[Limits] Preserve approved scope and existing work; avoid unrelated changes.
Work in this order:
1. Read the material and restate the goal. Ask one essential question when missing information affects the result.
2. Perform reading, organization, edits, and checks that AI can handle. For personal actions, identify the page and control.
3. Preserve a recoverable version and unapproved existing changes before editing.
4. Provide actual artifacts, file locations, and the current preview; a plan is not executed work.
[Deliverables] Actual git status and git log -1 output, excluded files and reasons. If Git is unavailable, provide the official installation route for the OS and recheck after installation.
[Acceptance] Check the goal item by item and report actual checks, unverified work, and next steps. Await explicit confirmation before deletion, payment, expanded access, or public release.This is file content, not a chat prompt. Ask AI to merge it into project instructions and fill unknowns from the actual project.
Confirmed · personalized content ready to copy
# Project working instructions
## Goal
- Product purpose: to be confirmed.
- Audience: to be confirmed.
- First-version scope: read docs/requirements.md; clarify if it does not exist.
- Exclusions: follow approved requirements without adding features unasked.
## Before work
1. Read this file and any existing README.md, docs/requirements.md, docs/design.md, and tasks/todo.md.
2. Check the project directory, Git status, and uncommitted changes. Report missing files without inventing them.
3. Restate the task and acceptance criteria; ask only for information that materially affects the result.
## Implementation
- Perform reading, organization, implementation, and checks that can be automated.
- Deliver small inspectable versions. Preserve existing work and avoid unrelated refactors.
- Follow the existing stack and styles; explain impact before changing the approach.
- Explain technical words plainly and provide click targets and expected visible results.
## Commands (verify before filling in)
- Install dependencies: to be confirmed.
- Start preview: to be confirmed.
- Check code: to be confirmed.
- Build output: to be confirmed.
- Keep these unknown until environment setup verifies actual commands.
## Checks and completion
- Check normal actions, empty input, failures, and affected existing behavior against requirements.
- Record execution, passing, failing, and unverified work separately in docs/checks.md.
- Update tasks/todo.md and provide artifact locations, the preview, and next steps.
- A build is not a personal trial. Do not claim unexecuted checks passed.
## Versions and data
- Ensure the current version is recoverable. Commit only task files after checks pass with a clear message.
- Inspect staged files; exclude secrets, personal data, dependency folders, and build output.
- Preserve unrelated uncommitted work; avoid destructive history or forced restoration.
- Git records tracked files, not live database backups.
## Human decisions
- Explain impact and await approval before spending, deleting data, expanding access, pushing remotely, or publishing.
- If blocked, record attempted steps, actual results, and the smallest missing decision.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
Set up AI working instructions in the currently open project.
[Project path] Enter the project folder already open in the tool.
[Purpose] Enter the purpose or read idea.md.
[Tool and version] Enter the tool; verify the version if unknown.
1. Identify the actual root, then read existing instructions and README without discarding content.
2. Check the current tool's official filename, location and loading rules. The shared filename is AGENTS.md, plural, not AGENT.md. If CLAUDE.md, GEMINI.md or a settings entry is required, explain why and configure the current version without conflicting duplicates.
3. Merge the template below into the real project. Fill facts from files and keep unverified commands marked unknown.
4. Reread the saved file; report its full path, changes, three constraints and unknowns.
5. Inspect the session's loaded-instruction record when available; repeat in a new session. Mark automatic loading unverified when it cannot be observed. Self-reported compliance alone is not proof.
6. Do not build product features, push or publish in this task.
File content template:
# Project working instructions
## Goal
- Product purpose: to be confirmed.
- Audience: to be confirmed.
- First-version scope: read docs/requirements.md; clarify if it does not exist.
- Exclusions: follow approved requirements without adding features unasked.
## Before work
1. Read this file and any existing README.md, docs/requirements.md, docs/design.md, and tasks/todo.md.
2. Check the project directory, Git status, and uncommitted changes. Report missing files without inventing them.
3. Restate the task and acceptance criteria; ask only for information that materially affects the result.
## Implementation
- Perform reading, organization, implementation, and checks that can be automated.
- Deliver small inspectable versions. Preserve existing work and avoid unrelated refactors.
- Follow the existing stack and styles; explain impact before changing the approach.
- Explain technical words plainly and provide click targets and expected visible results.
## Commands (verify before filling in)
- Install dependencies: to be confirmed.
- Start preview: to be confirmed.
- Check code: to be confirmed.
- Build output: to be confirmed.
- Keep these unknown until environment setup verifies actual commands.
## Checks and completion
- Check normal actions, empty input, failures, and affected existing behavior against requirements.
- Record execution, passing, failing, and unverified work separately in docs/checks.md.
- Update tasks/todo.md and provide artifact locations, the preview, and next steps.
- A build is not a personal trial. Do not claim unexecuted checks passed.
## Versions and data
- Ensure the current version is recoverable. Commit only task files after checks pass with a clear message.
- Inspect staged files; exclude secrets, personal data, dependency folders, and build output.
- Preserve unrelated uncommitted work; avoid destructive history or forced restoration.
- Git records tracked files, not live database backups.
## Human decisions
- Explain impact and await approval before spending, deleting data, expanding access, pushing remotely, or publishing.
- If blocked, record attempted steps, actual results, and the smallest missing decision.
Tools and rules: troubleshooting
2 situationsThese paths synthesize official docs and public reports, not frequency data. Check the symptom and verify the result.
AI says it edited a file, but no file exists
Observed symptom: Chat returns code without changing the project.
- What should you check first?
Check whether the mode can edit files and identify its working directory.
- Then resolve
Open the actual project folder. Ask AI to create tool-check.md with one test line and read it back; remove the test file afterward.
- Verify the result
The file list and read-back show the same file and text.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: AI says it edited a file, but no file exists.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Check whether the mode can edit files and identify its working directory.
Proposed approach: Open the actual project folder. Ask AI to create tool-check.md with one test line and read it back; remove the test file afterward.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: The file list and read-back show the same file and text.
Report actual checks, unchecked items, and the next step.
If a temporary check file is needed, verify the name is unused. Remove only that newly created check file; preserve all existing files.ReferencesLovable · Project chat and debugging ↗
Rules exist but are not followed
Observed symptom: AI changes excluded files or forgets the start command.
- What should you check first?
Check the plural filename AGENTS.md, directory, tool version, and loaded instructions.
- Then resolve
Ask AI to read and restate three rules. Claude Code support is conditional; check imports when CLAUDE.md exists. Older versions can import @AGENTS.md from CLAUDE.md. Remove conflicting rules.
- Verify the result
A new task identifies the rule source and follows it on a small edit; restating rules is not enforcement.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: Rules exist but are not followed.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Check the plural filename AGENTS.md, directory, tool version, and loaded instructions.
Proposed approach: Ask AI to read and restate three rules. Claude Code support is conditional; check imports when CLAUDE.md exists. Older versions can import @AGENTS.md from CLAUDE.md. Remove conflicting rules.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: A new task identifies the rule source and follows it on a small edit; restating rules is not enforcement.
Report actual checks, unchecked items, and the next step.ReferencesClaude Code · Project instructions ↗Reddit · Original ignored-instructions report ↗
Git and environment: troubleshooting
2 situationsThese paths synthesize official docs and public reports, not frequency data. Check the symptom and verify the result.
Git initialization or the first commit fails
Observed symptom: Git reports no repository, unknown identity, or includes unrelated folders.
- What should you check first?
Check project root, git --version, git rev-parse --show-toplevel, and git status.
- Then resolve
Initialize only a new project root. Inspect ancestor repositories first. Ask the owner for commit name/email and configure this repository only. Review ignored and staged files before committing.
- Verify the result
The root is correct and git log -1 shows the intended commit without secrets or unrelated files.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: Git initialization or the first commit fails.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Check project root, git --version, git rev-parse --show-toplevel, and git status.
Proposed approach: Initialize only a new project root. Inspect ancestor repositories first. Ask the owner for commit name/email and configure this repository only. Review ignored and staged files before committing.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: The root is correct and git log -1 shows the intended commit without secrets or unrelated files.
Report actual checks, unchecked items, and the next step.ReferencesGit · git init ↗GitHub · Commit username ↗GitHub · Commit email ↗
Dependencies fail or preview refuses to open
Observed symptom: A command is missing, installation fails, or the browser refuses a connection.
- What should you check first?
Read README, version files, lockfile, the first terminal error, and current directory.
- Then resolve
Use the required runtime and matching package manager; do not mix lockfiles. Run the defined start command, keep it running, and open its actual URL and port. Inspect logs and listening address if needed.
- Verify the result
The actual URL loads and the terminal has no startup failure; record commands and versions.
Edit the template with actual material, confirm, then copy into the current project conversation. Mark unknowns as undecided and replace examples as needed.
Confirmed · personalized content ready to copy
I am blocked at: Dependencies fail or preview refuses to open.
Project and tool: [name, version, and project path]
Observed behavior: [steps, exact error, or screenshot; remove secrets and personal data]
Expected result: [actual goal]
First inspect: Read README, version files, lockfile, the first terminal error, and current directory.
Proposed approach: Use the required runtime and matching package manager; do not mix lockfiles. Run the defined start command, keep it running, and open its actual URL and port. Inspect logs and listening address if needed.
Explain the evidence and cause before making the smallest relevant fix. Preserve existing changes and do not add features. If I must act, give one precise action at a time and its expected visible result.
Success criteria: The actual URL loads and the terminal has no startup failure; record commands and versions.
Report actual checks, unchecked items, and the next step.Referencesnpm · Install Node.js and npm ↗Astro · Develop and build ↗Vite · Original connection-refused report ↗
Tool differences and official references · checked 2026-09-23
Labels, capabilities, and costs may change. Follow the actual tool and its official documentation. This guide does not register, purchase, or publish on behalf of the reader.
Continue after the checks pass. If a step fails, bring the exact error back to the current AI conversation.
Return to the learning path and continue the current step →Return to this journey step