Your daily dose of Peace, Love, and Linux-fu, delivered to your browser.
npx skills add https://github.com/ehfazrezwan/neuralscape --skill project-ehfazrezwan
Please help me install this Agent Skill. Skill: project Source: https://github.com/ehfazrezwan/neuralscape/tree/main/neuralscape-plugin/skills/project Command: npx skills add https://github.com/ehfazrezwan/neuralscape --skill project-ehfazrezwan
When using AI assistants like Claude Cowork that have no native working directory to infer project context, it is impossible to automatically scope Neuralscape memory operations to a specific project, leading to disorganized, unscoped memory that is difficult to manage and retrieve across sessions.
Tell the AI to set your active Neuralscape project to the e-commerce platform redesign you are currently working on.
High-intent search queries and answers about installing and using this skill.
To scope AI assistant memory operations, you can select or create a specific Neuralscape project context. This ensures all memory recall and storage is restricted to your active work, preventing disorganized, unscoped data across sessions.
Persistent project selection for Claude Code works by pinning your chosen project to a repo-level marker file. This ensures the selected project context is automatically used across all future sessions and subdirectories without manual reconfiguration.
Yes, you can create new Neuralscape memory projects on the fly. The process includes input validation to reject malformed names and near-duplicate checks to prevent accidentally creating duplicate project scopes.
You can retrieve a full list of your private and team-shared Neuralscape projects. This allows you to easily review available scopes and switch your memory context to the relevant client or task project.
Explicit project scoping for memory management is needed when AI assistants lack a native working directory to infer context. Without it, memory operations become unscoped, making saved data difficult to organize and retrieve across multiple projects.
A limitation of using repo-level marker files for project switching is that the persistent selection is tied to the specific repository. You must manually switch project scopes if you are working across different repositories or outside the marked directory.
NeKon69Resolve the project root directory by searching upward for marker files.
johnnymo87Persist task context across sessions using Git-backed beads.
ClementATHManage local skills across user and project scopes via CLI.
somsubhroGenerate a self-contained assistant directory from interview data.
