Results for “file-system”

Coordinates a goal lifecycle: define, decompose, activate, track, and execute goals using a set of system skills that write markdown files.

Read, write, edit, list, copy, move, and search files directly using builtin tools, with fallback to Python or bash for complex operations.

Uses the filesystem as a durable overflow layer for agent context, enabling scratch pads, plan persistence, sub-agent communication, dynamic skill loading, and log management.

Organizes files into folders by type, size, or date, with preview, undo, and custom rule support.

Reads the contents of text, configuration, and code files when the user needs to view or cat a file.

Locates files by name and searches file contents using the fd and ripgrep command-line tools.

Automatically organizes files in a directory into a clean structure based on configurable rules — by file type, date, project, or priority — with support for duplicate detection, naming conventions, and archival strategies. Use when the user requests file organization or provides relevant inputs for this workflow.

Organizes files and folders by analyzing structure, finding duplicates, and proposing logical groupings, with user approval before any changes.

Organizes digital files and folders by building naming conventions, folder structures, and retrieval workflows, including project management and critical document inventory.

Creates and maintains persistent markdown planning files that survive session resets by hooking into Claude Code's lifecycle.

Backs up important files before modification, prompts the user to review changes, and deletes the backup only after explicit confirmation.

Detects available memory tools and maps them to a structured memory system for cross-session recall, with file-based fallback.

Manage a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across local files, MCP memory, vector stores, and Git repos.

Detects and fixes common MSBuild anti-patterns in .csproj, .vbproj, .fsproj, .props, .targets, and .proj files, covering Exec misuse, unquoted conditions, hardcoded paths, and more.

Manages a multi-layered knowledge system for ingesting, organizing, syncing, and retrieving knowledge across local files, MCP memory, vector stores, and Git repos.

Manages a personal operating system for content creation, relationship management, goal tracking, and weekly reviews using progressive disclosure and append-only data files.

Turns any long-running domain (business, relationships, health, career, learning, investing) into a local knowledge project with four layers, source tags, immutable snapshots, and a concept library that learns patterns over time.