← ClaudeAtlas

filedatasourcelisted

Guidance for using FileDataSource and creating custom file reader extensions in BeepDM. Use when implementing or extending DataManagementEngineStandard/FileManager with new formats via IFileFormatReader and FileReaderFactory.
The-Tech-Idea/BeepDM · ★ 1 · Data & Documents · score 65
Install: claude install-skill The-Tech-Idea/BeepDM
# FileDataSource Guide Use this skill when working on `DataManagementEngineStandard/FileManager` to either: - use `FileDataSource` correctly as an `IDataSource`, or - add a new file-format reader extension. ## Use this skill when - Implementing or fixing `FileDataSource` behavior (connection, schema, query, CRUD). - Adding support for a new file type via `IFileFormatReader`. - Registering custom readers in `FileReaderFactory`. - Debugging format-specific parse behavior, diagnostics, or schema inference. ## Do not use this skill when - The task is only generic `IDataSource` behavior. Use [`idatasource`](../idatasource/SKILL.md). - The task is only connection config modeling. Use [`connectionproperties`](../connectionproperties/SKILL.md) and [`connection`](../connection/SKILL.md). - The task is primarily ingestion orchestration policies. Use [`importing`](../importing/SKILL.md). ## Responsibilities - Keep `FileDataSource` format-agnostic and delegate parsing/writing to `_reader`. - Implement reader-specific logic only in `IFileFormatReader` implementations. - Keep schema inference and row parsing consistent with existing file readers. - Preserve `IDataSource` contract behavior (`ErrorObject`, `ConnectionStatus`, `Entities`, `EntitiesNames`). ## Core API Surface - `FileDataSource`: - `Openconnection()`, `Closeconnection()` - `GetEntityStructure(...)`, `GetEntity(...)`, CRUD methods - `ResolveEntityFilePath(...)` - Reader contract: - `IFileFormatReader` (`Configure`,