> For the complete documentation index, see [llms.txt](https://snowconedao.gitbook.io/snowconedao/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://snowconedao.gitbook.io/snowconedao/build/getting-started.md).

# Getting Started

**Import**[**​**](https://info.juicebox.money/dev/learn/risks/#import)

Add the protocol files to the project.

```solidity
# command linenpm install @Snowcones/snowcones-icy-contracts/
```

If referencing from typescript:

```solidity
const contract = require(`@Snowcones/snowcones-icy-contracts/deployments/${network}/${contractName}.json`)
```

If referencing from a contract:

```solidity
import '@Snowcone/snowcones-icy-contracts/contracts/[file-path].sol'
```

**Now what**[**​**](https://info.juicebox.money/dev/learn/risks/#now-what)

From here, you can build the following:

Basics - Interact with the protocol's basic functionality. Useful for building front-ends. 

Pay a project - Deploy or inherit from a contract that makes it easy to forward funds to Snowcone projects.

Split payments - Deploy or inherit from a contract that makes it easy to forward funds to groups of splits whose members are either addresses, Snowcone projects, or arbitrary contracts that inherit from `ISNOWSplitAllocator`.

Program a treasury - Get familiar with the configurable properties available when launching a project. 

Program project permissions - Build custom Snowcone Project NFT logic to create your own project access controls.

Program treasury extensions - Create custom contractual rules defining what happens when a project receives funds, and under what conditions funds can leave the treasury during a funding cycle.


---

# 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 following URL with the `ask` and `goal` query parameters:

```
GET https://snowconedao.gitbook.io/snowconedao/build/getting-started.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 `build a script that syncs our docs to a CMS` 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.