Understanding Your Project Structure
When you create a project using the recommended "JS template" in Bulifier AI, several important files and folders are generated to organize your code and configuration:
schema Folder
This folder contains specialized configuration files (schemas) that guide Bulifier AI's internal prompt generation. They define how your natural language requests in the AI interface (Code, Doc, Chat tabs) are structured before being sent to the underlying large language models.
Advanced Users: You can technically edit these schemas to customize the core behavior of the AI within Bulifier for your specific project. However, modifying these files requires understanding their structure and can significantly alter AI performance and results. Proceed with caution. A "Revert" button is often provided in the schema editing interface to restore the defaults.
dependencies.txt
This file is the heart of Bulifier's simple NPM dependency management system for your web projects. The AI is trained (via its schema instructions) to add necessary libraries to this file when you request features that require them (e.g., "Add confetti effect using the 'canvas-confetti' library").
The format rules are strict:
- Global scope dependencies (most common for browser libraries):
package-name@version(e.g.,three@0.163.0) - Module-specific dependencies (less common):
module package-name@version - One dependency entry per line.
- Always specify an exact version number (
@version) to ensure consistent and predictable builds. Avoid using ranges or omitting the version. - Only list dependencies your project actually uses.
Crucial Integration: For Bulifier to automatically include the necessary <script> tags for these libraries when you run your app, your main HTML file (typically index.html) must contain the HTML comment: {/* Vendor libraries */}. The Bulifier build process searches for this comment and injects the script tags right after it during the Run phase.
.gitignore Files Family
Bulifier utilizes files with syntax similar to Git's .gitignore for different purposes:
.gitignore: This is the standard file used by the Git version control system itself. Any files or patterns listed here will be ignored by Git commands (commit, status, etc.). You should add build artifacts, sensitive files, or environment-specific files here (e.g.,node_modules/if you were using Node.js locally, although Bulifier handles dependencies differently).context.gitignore: This file tells Bulifier AI which files or patterns to exclude when gathering context for the "Code" tab in the AI interface. This prevents sending large, unnecessary, or potentially problematic files to the AI, saving tokens and improving focus. Defaults often include.git/,schema/,*.gitignoreitself, etc.protected.gitignore: This acts more like a "protected files" list (despite the name). Files matching patterns in here are shielded from accidental modification or deletion by certain Bulifier features, potentially including some AI operations. You can edit this file if you intentionally need to modify a core file, but be aware of the risks.
Other Common Files
index.html: The main entry point for your web application. Remember the{/* Vendor libraries */}comment for dependencies.style.css(or similar): For your CSS styling.script.js(or similar): Your main JavaScript code file.assets/folder (optional but recommended): Create this folder to store images, sounds, fonts, JSON data, etc. (See Asset Management).