workspace-context-populate
Workspace Context Populate
Use this skill when a workspace has empty canonical context sections in the dashboard or an agent needs to refresh shared workspace context safely.
Behavior
-
Resolve the target workspace
- Prefer the current workspace already in scope.
- If needed, register or confirm the workspace ID with
memory_workspace(action: "register"|"info").
-
Populate canonical workspace sections through the existing tool surface
- Call
memory_context(action: "workspace_populate", workspace_id: "..."). - This action fills canonical sections such as
project_details,purpose,dependencies,modules,test_confirmations,dev_patterns, andresources. - It only writes sections that are missing or empty.
- It preserves non-empty user-authored content and custom sections.
- Call
-
Verify the result
- Read back with
memory_context(action: "workspace_get", workspace_id: "..."). - Confirm the canonical sections now contain summaries or items.
- Read back with
-
When additional manual context is needed
- Use
memory_context(action: "workspace_update")for specific authored additions after population. - Do not overwrite populated sections wholesale unless the user explicitly requests it.
- Use
Guardrails
- Prefer
workspace_populateover ad hocworkspace_updatecalls when the goal is to repair empty canonical sections. - Do not delete existing workspace context to repopulate it.
- Treat
important_context,chat_session_details, and other custom sections as user or agent authored unless instructed otherwise.
Output Format
Return a concise report:
- Workspace ID
- Canonical sections populated
- Any sections intentionally skipped because they already had content
- Follow-up manual edits still recommended
More from ds-codi/project-memory-mcp
pyside6-mvc
Use this skill when building Python desktop applications using PySide6 with strict MVC architecture where all UI is defined by .ui files. Covers architecture patterns, controller/model/view separation, signal handling, and .ui file workflows.
95pyside6-qml-views
Use this skill when creating QML view files, designing QML component hierarchies, building layouts, styling QML controls, creating reusable QML components, implementing QML navigation / page switching, or working with QML resources. Covers QML file structure, component patterns, Material/Controls styling, resource management, and common QML idioms for desktop applications.
49pyside6-qml-architecture
Use this skill when creating a new PySide6 + QML desktop application with MVC architecture, setting up project structure, implementing the application bootstrap / DI container, or understanding how the MVC layers connect. Covers project scaffolding, entry points, singleton application class, service locator, signal registry, and lifecycle management.
47mvc-architecture
Use this skill when implementing Model-View-Controller architecture. Covers core MVC principles, layer separation, dependency injection, event-driven communication, and patterns for controllers, models, and views.
40pyside6-qml-models-services
Use this skill when creating domain models with Qt signal support, implementing the repository pattern for data persistence, building service classes for external interactions, designing the central signal registry, or working with application state management. Covers BaseModel, model serialization, database repositories, service patterns, signal definitions, and the ApplicationState singleton.
34pyside6-qml-bridge
Use this skill when exposing Python objects to QML, creating bridge classes, defining Qt properties with NOTIFY signals, implementing invokable methods / slots, or connecting QML user actions to Python controllers. Covers the QObject bridge pattern, property decorators, type conversions, context properties, and QML type registration.
32