load-project-profile

To automatically load a project profile, the Skill detects and reads profile.json in the working folder and its immediate subdirectories. It validates required fields like name, systemCode, prefix, framework, db, and author, then activates the matched profile to provide downstream context.

If profile.json is missing or corrupted during project activation, the Skill triggers an error handling mechanism. It displays a guidance message and provides instructions to reset or recreate the necessary profile configuration for your project.

Loading a project profile exposes metadata to downstream commands by reading and validating required fields from profile.json. It updates the lastUsed timestamp to today and injects contextual fields like framework and db into the active workflow for subsequent tasks.

Yes, you can use profile.json to manage context across multiple projects. The Skill searches the working folder and its direct subdirectories to detect profile.json files, automatically activating the matched profile and exposing its metadata for downstream commands.

Yes, you need specific fields in profile.json to initialize project context successfully. The Skill validates that required fields—name, systemCode, prefix, framework, db, author, and lastUsed—are present before activating the profile and exposing contextual data downstream.

Automated project profile activation fails when profile.json is absent, misplaced outside the working folder, or missing required validation fields. Ensure the file contains valid name, systemCode, prefix, framework, db, author, and lastUsed data for successful detection and loading.