technical-context-discovery

To establish technical context, inspect repository root rules like .cursor/rules/*.md and AGENTS.md, analyze codebase patterns for architecture and naming conventions, and consult external documentation to ensure alignment before coding.

The best way to analyze codebase patterns is to systematically mirror established conventions for architecture, error handling, validation, testing, and configuration, applying an implementation rule decision hierarchy to minimize conflicts and risk.

Cursor rules and instruction files help maintain conventions by providing explicit agent configurations and guidelines at the repository root, which developers can review to align feature work with existing project patterns.

You should consult external documentation when internal repository rules are insufficient for your current task, allowing you to apply industry best practices and security considerations to fill the context gaps.

You prevent conflicting conventions by applying an implementation rule decision hierarchy that checks repository instructions, mirrors existing codebase patterns, and reviews external documentation before starting any code modifications.

Yes, technical context discovery works for onboarding, feature work, and architectural decisions by systematically identifying project rules, analyzing established patterns, and reviewing documentation to ensure alignment before changes.