# Best Practices

This section contains Harrier's best practices and standards for Salesforce development. These guidelines ensure consistency, maintainability, and quality across all implementations.

## Documentation Index

### [Salesforce Project Structure](/technical/best-practices/project-structure.md)

Module-based architecture patterns for organizing Salesforce projects at scale.

### [Class Folder Organization](/technical/best-practices/class-folder-organization.md)

Guidelines for organizing Apex classes within your project structure for better maintainability.

### [Apex Style Guide](/technical/best-practices/apex-style-guide.md)

Code formatting and style standards for Apex development, promoting readable and maintainable code.

### [Apex Unit Testing Guidelines](/technical/best-practices/apex-unit-testing-guidelines.md)

Standards and best practices for writing effective unit tests that ensure code quality and reliability.

### [LWC Development](/technical/best-practices/lwc-development.md)

Standards and best practices for Lightning Web Component development.

### [Logging](/technical/best-practices/logging.md)

Best practices for implementing logging in Salesforce applications.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://docs.goharrier.com/technical/best-practices.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.