> ## Documentation Index > Fetch the complete documentation index at: https://aidocs.ethanbragdon.icu/llms.txt > Use this file to discover all available pages before exploring further. # Create & Manage Projects > Create Starfire AI projects, choose ownership context, manage project metadata, and organize long-running work. # Create & manage projects Projects are the preferred home for work that spans multiple conversations, files, builds, or research runs. ## Create a project 1. Open the Projects area in Starfire AI. 2. Create a new project. 3. Choose the intended personal or organization context. 4. Give the project a clear name and description. 5. Add durable project instructions when the work has stable requirements. 6. Add files, Knowledge sources, repositories, or conversations as needed. ## Choose ownership carefully Ownership affects: * who can access the project * which organization policies apply * which billing/credit context funds work * who owns generated artifacts * what happens when a team member leaves A business-critical project should generally be organization-owned when that ownership model is available. ## Project naming Use names that identify the body of work, not one immediate task. Good: * `Starfire AI Alpha 1.6.3` * `Panther City Roleplay 2.0` * `Customer Support Knowledge Base` Less useful: * `New project` * `Fix bug` * `Stuff` ## Archive vs delete If Starfire exposes archiving, prefer archive for completed work you may need to reference later. Deletion is appropriate when the project and its dependent resources are no longer needed. Before deleting, review files, Knowledge, builds, artifacts, and organization ownership. ## Move conversations into project context When supported by the current build, associate related conversations with the project so future work can discover durable context without turning one chat into the project database. Changing project ownership can affect permissions and billing. Treat ownership transfer as an administrative action, not a cosmetic rename.