context

To build repository context, read canonical docs like CONTEXT.md and DECISIONS.md first, then summarize assumptions, constraints, and affected file paths concisely without pasting long logs. This creates a durable snapshot for correct implementation and decision-making.

The best way to summarize project decisions is prioritizing official documentation like DECISIONS.md over ad-hoc notes, creating path-referenced summaries of constraints and assumptions to resume work without re-reading scattered logs.

Validate project conventions by locating relevant files by path and reading canonical docs first, keeping a concise summary of constraints and assumptions. This ensures correct implementation aligned with existing repository standards.

No, you do not need to copy long logs when summarizing repository context. The approach encourages concise, path-referenced summaries of assumptions and affected files instead of pasting lengthy outputs.

Yes, it works for onboarding to a legacy Node service by directing users to follow steps that quickly identify conventions, key files, and pending design choices before coding, ensuring correct implementation.

You need a repository context snapshot when starting work, resuming after handoff, or validating project conventions across a codebase. It helps contributors make decisions without re-reading scattered documents or logs.