> For the complete documentation index, see [llms.txt](https://intro-to-github-docs.beliciarodriguez.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://intro-to-github-docs.beliciarodriguez.com/repository/untitled.md).

# Introduction

This section will explain how to create a repository that will be found both on your account on github and on your local computer. There are two methods; the first starts on github.com and clones the repository onto your local computer. The second method takes a folder on your local computer, makes it a repository, and pushes the repository to your github account. We will only be showing how to do the first method because it is the most common, but it is good to be aware that there are different ways of creating repositories.

Later in this section, we will begin using the terminal. The only command that I use besides the git commands is "cd", meaning "change directories." "cd" changes the directory your terminal is currently looking into. If you want to check what files can be found in the location your terminal is currently viewing, type "ls". These commands may only be native to Mac computers, so if you have Windows or a Linux computer you many need to do some Google searching on what your commands are for your terminal.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## 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, and the optional `goal` query parameter:

```
GET https://intro-to-github-docs.beliciarodriguez.com/repository/untitled.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.