project-context

To retrieve cross-project context, fetch data from a central registry.json file that stores project identities, goals, and focus. The system reads this registry and returns a searchable summary of all available projects.

To list all projects from the hub registry, invoke the skill without arguments. It reads registry.json and outputs a searchable summary sorted alphabetically with columns for Project, Type, and Summary.

Yes, you can fetch a specific project's identity and goals by supplying a partial name. The skill uses fuzzy matching against the registry to find the correct project and reads up to three project files for details.

The best way to access architecture and tech notes is to fetch the specific project from the registry. The skill automatically surfaces optional architecture and tech documentation if present in the project's memory-bank.

A limitation when fetching project files is that the skill reads a maximum of three project files per request. Additional architecture and tech docs are only surfaced if explicitly present in the project's memory-bank.