> For the complete documentation index, see [llms.txt](https://docs.seismic.systems/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.seismic.systems/tutorials/understanding-the-clown-beatdown-contract/setting-up-your-project/initialize-contracts.md).

# Initialize contracts

1. **Navigate to the contracts subdirectory:**

```bash
cd packages/contracts
```

2. **Initialize a project with `sforge`:**

```bash
sforge init && rm -rf .github
```

This command will:

* Create the contract project structure (e.g., `src/`, `test/`, `foundry.toml`).
* Automatically install the Forge standard library (`forge-std`) as a submodule.
* Remove the `.github` workflow folder (not required)

3. Edit the `.gitignore` file to be the following:

```bash
.env
broadcast/
cache/
```

4. Delete the default contract, test and script files (`Counter.sol` and `Counter.t.sol` and `Counter.s.sol`) and replace them with their `ClownBeatdown` counterparts (`ClownBeatdown.sol`, `ClownBeatdown.t.sol` and `ClownBeatdown.s.sol`):

```bash
# Remove the Counter files
rm -f src/Counter.sol test/Counter.t.sol script/Counter.s.sol

# Create empty ClownBeatdown files in the same locations
touch src/ClownBeatdown.sol test/ClownBeatdown.t.sol script/ClownBeatdown.s.sol
```

These files are empty for now, but we will add to them as we go along.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://docs.seismic.systems/tutorials/understanding-the-clown-beatdown-contract/setting-up-your-project/initialize-contracts.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.