# Create a project > Group the skills, workflows, and apps that serve one goal into a single system you can keep building on. Skills, workflows, and apps are the three things you build in General Input. A project is the layer above them. Nobody sets out to build a skill. They set out to hit a goal, and hitting it usually takes a procedure written down, something that runs on a schedule, an interface a colleague can use, and the reference material behind all three. A project is where those live together, pointed at the same outcome. ## Create the project Open **Projects** in the sidebar and click **New**. Give it a name and an icon. Name it after the goal, not the tooling: "Content engine" or "Client onboarding" rather than "Blog workflow". Add a short description of what the project is for. Agents working inside it read this as standing context. ## Build the system inside it The fastest way to fill a project is to describe the whole system at once and let it get built in place. Open the project and start a chat from it. The project is pinned to the input, so everything created in that conversation lands inside the project instead of loose in your workspace. Describe the system in plain English. Say what should happen, how often, and what it should learn from. One paragraph is enough. Review what comes back. You will usually get several pieces at once: a skill holding the procedure, a workflow on a schedule, and an app to work the output. A useful shape for that first paragraph: what you want produced, where the raw material comes from, when it should run, and what it should imitate. For example, "read yesterday's news at 3am, give me five post ideas, and match the tone of the posts already on our blog." ## Pin work you already have Existing skills, workflows, and apps can move into a project at any time. Open the resource and use **Move to project**, or add it from the project page. A resource lives in exactly one project. Moving it out again returns it to the top level of your workspace. Pinning is an owner action. You can move a resource you own into any project you can edit. ## Add files it should know about Projects hold files as well as automations: brand guidelines, a pricing sheet, last quarter's report, anything the work depends on. Open the **Files** tab on the project and upload what it needs. Chats started from the project mount those files read-only, so an agent can read them without being able to change them. Files are yours to manage. Agents never write into this store, so what you put there stays exactly as you left it. ## What the project learns A project keeps its own memory, separate from your workspace memory and your personal memory. It builds that memory from the project's files, the workflows pinned to it, and how those runs go, so the system gets better at its job over time without you maintaining a prompt by hand. Project memory never reads the chats inside the project. Conversations you have in a project stay private to you, even when the project itself is shared. ## Share it with your team Sharing a project shares what is in it. Give someone access to the project and the workflows, apps, and skills pinned to it come along, which is usually what you want when you hand over a system rather than a file. Access set directly on a resource still wins. Somebody can be an editor on the project and a viewer on one particular workflow inside it. ## Deleting a project Open the project menu and choose **Delete**. Decide what happens to the work inside it. **Delete them too** removes everything you own along with the project. **Keep them in my workspace** moves it all out to the top level, where it keeps working. Deleting is permanent, so a project you may want later is worth keeping. Anything a teammate owns is never deleted; it moves to your workspace instead.