Efficiently Identifying Kubernetes Resource Manifests in Argo CD by Deployment Name

[h-c-a]

Question:

If I know the deployment name in Kubernetes, is there a way to use Argo CD to directly identify the specific manifest responsible for the resource requests and limits, without manually walking through the directory structure (especially in setups with ApplicationSets or overlays)? What are the best practices to achieve this efficiently?