Wardian Library System (Prompts & Skills)

Status: Implemented
Date: 2026-03-15
Context:
Wardian requires a centralized, high-efficiency repository for managing reusable Prompts and Skills. Users need to organize these assets logically, discover favorites rapidly, and inject them into active agent sessions without friction.

Decision

1. Unified Class Registry (classes.json):

   • Consolidate default_classes.json and custom_classes.json into a single source of truth: ~/.wardian/classes.json.
   • The backend will perform a one-time merge of defaults into this file if it doesn't exist.
   • Every class will support an assigned_skills: string[] field (legacy support, overridden by physical deployments).

2. Library Storage Model (Physical-First):

   • Prompts: Stored as .md files in ~/.wardian/library/prompts/.
   • Skills: Stored as directories in ~/.wardian/library/skills/, each containing a SKILL.md file.
   • Folders: Physical directories on disk define the organizational hierarchy.
   • Metadata: A library.json sidecar file in the library root will store "Virtual" metadata (Tags, Stars/Favorites) keyed by the relative file path.

3. Workspace Integration:

   • Main View: LibraryView.tsx acts as the primary workspace view for management of all agent "Blueprints". It includes three primary sections:
     • Prompts: Reusable terminal injections.
     • Skills: Physically deployed capabilities (.agents/skills/).
     • Classes: Global agent type definitions (relocated from the sidebar for a more spacious management experience).
   • Injection Hub: The Command Sidebar Tab (CommandPanel.tsx) dynamically displays "Quick Prompts" (starred) for immediate injection into the focused terminal.

4. Skill Deployment Model (Live Links with Copy Fallback):

   • To keep provider skills current without manual redeployment, skills are deployed as live directory links from the Library to the target entity's .agents/skills/ directory.
   • Windows uses junction points (mklink /J) so standard users can link directories without elevation. Unix platforms use standard directory symlinks.
   • If link creation fails, the backend falls back to the previous recursive copy behavior so skill assignment remains robust.
   • Target Scopes:
     • All Agents (Global User Profile): ~/.wardian/common/.agents/skills/
     • Agent Class: ~/.wardian/classes/[class_name]/.agents/skills/
     • Active Agent: ~/.wardian/agents/[session_id]/.agents/skills/
   • Precedence: The physical target paths remain the provider-facing source of truth, while live links keep their contents synchronized with the Library.
   • Updates: Updating a skill in the Library automatically updates every linked user, class, or agent skill deployment. Deploy actions still create or refresh the target path, but are no longer required for ordinary content edits.

5. Technical Implementation:

   • New Tauri command inject_session_input(session_id: String, text: String) writes flattened text directly to the process stdin.
   • Tauri commands deploy_skill, remove_deployed_skill, and list_skill_deployments manage the physical filesystem presence of skills.
   • Zustand store (useLibraryStore) decouples promptTree and skillTree to maintain stable UI states.

Consequences

• Pros:
  • Strict data isolation via the physical folder structure.
  • High visibility for favorites across all views (Grid/Dashboard).
  • Simplified class management via a single JSON registry.
• Cons:
  • Requires a migration path for existing custom_classes.json.
  • Metadata in library.json must be kept in sync if files are moved externally (mitigated by recommending in-app organization).

Schema Definitions

Library Item Metadata

interface LibraryItemMetadata {
  id: string; // UUID
  tags: string[];
  is_starred: boolean;
  last_used?: string;
}

Unified Class Definition

{
  "name": "Architect",
  "description": "...",
  "assigned_skills": ["playwright-cli"]
}