> For the complete documentation index, see [llms.txt](https://help.transform.ai/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.transform.ai/artifacts/creating-artifacts.md).

# Creating Artifacts

### Overview

Artifact creation standardizes where reference material lives.

It reduces repeated searches across external folders and message threads.

### Key Concepts

* **Account Artifact**: reusable reference available at Account scope
* **Project Artifact**: delivery-specific reference available inside a Project
* **Linking**: adding references from requirements, tasks, and tests

### How It’s Used

Create Account Artifacts for shared standards and templates.

Create Project Artifacts for delivery evidence and working references.

### Benefits

* Clear separation between reusable standards and delivery-specific content
* Faster retrieval during governance reviews
* Better traceability from scope to evidence

### Setup Steps

Select the creation path based on the scope.

* [At Account Level](/artifacts/at-account-level.md)
* [At Project Level](/artifacts/at-project-level.md)

### Best Practices

* Use a stable folder structure aligned to governance.
* Link Artifacts from requirements and tasks instead of copying content into descriptions.
* Keep file names consistent across Projects to support reuse.

### Summary

Create Artifacts at the correct scope, then link them to delivery work for traceability.


---

# 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://help.transform.ai/artifacts/creating-artifacts.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.