docs: added imports, prompts, envs

Author: butschster

docs/configuration.md

@@ -22,6 +22,8 @@ If you prefer YAML syntax, you can use the following format.
 Create a `context.yaml` file in your project root:
 
 ```yaml
+$schema: https://raw.githubusercontent.com/context-hub/generator/refs/heads/main/json-schema.json
+
 documents:
   - description: API Documentation
     outputPath: docs/api.md
@@ -62,6 +64,7 @@ Create a `context.json` file in your project root:
 
 ```json
 {
+  "$schema": "https://raw.githubusercontent.com/context-hub/generator/refs/heads/main/json-schema.json",
   "documents": [
     {
       "description": "API Documentation",
@@ -114,12 +117,51 @@ As you can see it's pretty simple.
 For large projects with multiple components or services, you can split your configuration across multiple files using
 the import functionality.
 
-- Import paths are resolved relative to the importing file
-- You can apply path prefixes to source paths in imported configurations
-- Imports can be nested (configurations can import other configurations)
-- Circular imports are automatically detected and prevented
+### Key Features
+
+* Import paths are resolved relative to the importing file
+* You can apply path prefixes to source paths in imported configurations
+* Imports can be nested (configurations can import other configurations)
+* Circular imports are automatically detected and prevented
+
+### Import Formats
+
+The `import` section supports several formats:
+
+#### String Format (Simplest)
+
+```yaml
+import:
+  - "services/api/context.yaml"
+```
+
+#### Object Format with Path
+
+```yaml
+import:
+  - path: services/api/context.yaml
+```
+
+#### Object Format with Path and Prefix
+
+```yaml
+import:
+  - path: services/api/context.yaml
+    pathPrefix: /api
+```
+
+#### Explicit Type Format
 
-### Import Example in YAML
+```yaml
+import:
+  - type: file
+    path: services/api/context.yaml
+    pathPrefix: /api
+  - type: url
+    url: https://example.com/shared-config.json
+```
+
+### Example in YAML
 
 ```yaml
 import:
@@ -136,7 +178,7 @@ documents:
           This is the main project documentation.
 ```
 
-### Import Example in JSON
+### Example in JSON
 
 ```json
 {
@@ -160,6 +202,13 @@ documents:
 }
 ```
 
+### Import Types
+
+| Type   | Description                                                 | Required Fields |
+|--------|-------------------------------------------------------------|-----------------|
+| `file` | Imports configuration from a local file                     | `path`          |
+| `url`  | Imports configuration (`prompts` section) from a remote URL | `url`           |
+
 ## Using Environment Variables
 
 Context Generator supports configuration via environment variables, which provides a flexible way to override settings

docs/mcp-server.md

@@ -161,7 +161,7 @@ You can configure the MCP server using environment variables.
 You can customize how document names appear in Claude's interface.
 
 ```dotenv
-CTX_DOCUMENT_NAME_FORMAT="{description} ({tags}) - {path}"
+MCP_DOCUMENT_NAME_FORMAT="{description} ({tags}) - {path}"
 ```
 
 Available placeholders:
@@ -170,4 +170,14 @@ Available placeholders:
 - `{description}` - The document description
 - `{tags}` - Comma-separated list of document tags
 
-By default, the format is: `[{path}] {description}`
+By default, the format is: `[{path}] {description}`
+
+### Configuring File Read/Write
+
+You can turn off file read/write operations in the MCP server.
+
+```dotenv
+MCP_FILE_OPERATIONS=false
+```
+
+By default, file operations are enabled. Set this to `false` to disable them.

docs/mcp/prompts.md

@@ -80,53 +80,36 @@ projects and teams. This creates an ecosystem where:
 - Specialized domain knowledge can be packaged into reusable templates
 - The community can collaborate on high-quality prompt libraries
 
-Context Generator currently supports basic configuration imports from local filesystem sources.
+Context Generator supports configuration imports from multiple sources to enable modular configuration management:
 
-**Coming soon**, we're extending this functionality to include remote sources, with a particular focus on making MCP
-prompts more accessible and shareable:
+### Import Capabilities
 
-### Upcoming Import Capabilities
-
-- **GitHub Repositories**: Import prompts directly from public or private GitHub repos
-- **Composer Packages**: Leverage prompts bundled in PHP Composer packages
-- **Remote URLs**: Reference prompt configurations via direct URLs
+- **Local Files**: Import prompts from local filesystem files
+- **URL Sources**: Import prompts directly from remote URLs
 - **Selective Imports**: Import only specific prompts from any source
 
-This will transform how teams work with AI by enabling:
+This transforms how teams work with AI by enabling:
 
 - **Reusability**: Create prompt repositories once, use them across multiple projects
 - **Community Sharing**: Participate in an ecosystem of community-maintained prompt libraries
 - **Standardization**: Promote best practices through shared prompt configurations
 - **Version Control**: Reference specific versions of remote prompt repositories
 
-### Example Remote Import Configuration
+### Example Import Configuration
 
 ```yaml
 import:
-  # Local import (current implementation)
+  # Local import
   - path: services/api/context.yaml
     type: local # default, can be omitted
 
-  # GitHub import (coming soon)
-  - path: butschster/ctx-prompts/prompts/refactoring.yaml
-    type: github
-    ref: main # optional, defaults to main/master
-    token: ${GITHUB_TOKEN} # optional, for private repos
-
-  # Composer package import (coming soon)
-  - path: vendor/butschster/ctx-prompts/prompts/refactoring.yaml
-    type: composer
-
-  # URL import (coming soon)
-  - path: https://example.com/context-configs/api-prompts.yaml
+  # URL import
+  - url: https://example.com/context-configs/api-prompts.yaml
     type: url
     headers: # optional HTTP headers
       Authorization: "Bearer ${API_TOKEN}"
 
-  # Selective import (coming soon, works with any source type)
-  - path: butschster/ctx-prompts/prompts/all.yaml
-    type: github
-    docs:
-      - refactoring/extract-method.md
-      - refactoring/rename-class.md
+  # GitHub Gist import (using URL)
+  - url: https://gist.githubusercontent.com/butschster/1b7e597691cc1a6476b15dc120ecbddb/raw/8c0f9d0145dcd260b814f866ec130ec630c80ee8/prompts.yaml
+    type: url
 ```

docs/quick-start.md

@@ -130,6 +130,14 @@ prompts:
 
 > **Note:** Read more about [Prompts](/mcp/prompts) for detailed configuration options.
 
+Import sharable prompts from the community or create your own to enhance your workflow.
+
+```yaml
+import:
+  - type: url
+    path: https://gist.githubusercontent.com/butschster/1b7e597691cc1a6476b15dc120ecbddb/raw/8c0f9d0145dcd260b814f866ec130ec630c80ee8/prompts.yaml
+```
+
 ## JSON Schema
 
 For better editing experience, Context Generator provides a JSON schema for autocompletion and validation in your IDE: