Keep your next idea moving.

Describe the result you want, the relevant files, and the behavior you expect. Include the project’s setup instructions and any constraints, such as files that should stay unchanged. Start with one well-defined task.

Check which project and files you are referring to. Point out the relevant entry point and explain any incorrect assumptions. Provide a small example of the expected behavior instead of adding unrelated project material.

Split it into smaller outcomes, such as understanding the existing behavior, changing one feature, and reviewing the result. State the scope and expected result for each part, especially when several files are involved.

Read the changes and compare them with your request. Pay attention to dependencies, configuration, data access, and any unexpected edits. Use your project’s normal review and validation process before merging or deploying.

Preserve any work you want to keep, then compare the change against your version-control history or backup. Restore only the affected changes you understand. Avoid discarding a whole working directory when it contains unrelated work.

Record the exact error, the command or request, the relevant working directory, and your operating system. Include any setup requirements and the steps that led to the failure. Remove secrets from logs before sharing them.

Check whether a running command is waiting for input, a permission decision, or a network response. Preserve your work before restarting anything. If you retry, use a smaller task and explain where progress stopped.

Use the installation and compatibility information supplied with your Meteor release. This support page provides general workflow guidance and does not publish a verified installer, version matrix, or list of supported extensions.