# Introduction

## Introduction

In the Python community, developers have a great programming style reference provided as part of the language enhancement process specifications ([PEP-8](https://www.python.org/dev/peps/pep-0008/)), but in the PowerShell world there has been no official documentation of community preferences.

This document is an attempt to come to an agreement on a style-guide because we know that the more people follow the same set of code-style habits, the more readable the community's code will be. In other words, although the recommendations of this guide are *just recommendations*, if you follow them, you will write PowerShell code that is more easily read, understood, and maintained.

## Table of Contents

* [Code Layout and Formatting](/powershell-practice-and-style/style-guide/code-layout-and-formatting.md)
* [Function Structure](/powershell-practice-and-style/style-guide/function-structure.md)
* [Documentation and Comments](/powershell-practice-and-style/style-guide/documentation-and-comments.md)
* [Readability](/powershell-practice-and-style/style-guide/readability.md)
* [Naming Conventions](/powershell-practice-and-style/style-guide/naming-conventions.md)


---

# 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://poshcode.gitbook.io/powershell-practice-and-style/style-guide/introduction.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.