@contextium/cli 1.0.7 → 1.0.8
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/package.json +1 -1
- package/skills/ium/contextium.md +29 -0
package/package.json
CHANGED
package/skills/ium/contextium.md
CHANGED
|
@@ -49,6 +49,35 @@ Workspace
|
|
|
49
49
|
| A role combining multiple skills? | Agent |
|
|
50
50
|
| Ready-to-use context package for a task? | Workflow |
|
|
51
51
|
|
|
52
|
+
## File Routing — Writing Files When Contextium Is Connected
|
|
53
|
+
|
|
54
|
+
When the Contextium MCP is connected or the CLI is active, **any time a new file is about to be created**, intercept it with a routing question before writing:
|
|
55
|
+
|
|
56
|
+
> "Should this file go to a Contextium context library, or stay local?"
|
|
57
|
+
|
|
58
|
+
**If a workflow is loaded in this session:**
|
|
59
|
+
- Default to suggesting the most relevant library from the session context block
|
|
60
|
+
- Offer: `[1] Write to "<library name>" in Contextium [2] Keep local`
|
|
61
|
+
- If the user picks Contextium, use `mcp__contextium__create_file` or `contextium files create` CLI with the library ID from session context — do NOT write it locally
|
|
62
|
+
|
|
63
|
+
**If no workflow is loaded but the MCP/CLI is active:**
|
|
64
|
+
- Ask: "Should this go to Contextium? If yes, which library?"
|
|
65
|
+
- List available libraries only if the user says yes
|
|
66
|
+
- Otherwise write locally as normal
|
|
67
|
+
|
|
68
|
+
**Files that should NEVER be routed to Contextium — always write locally:**
|
|
69
|
+
- Rich text formats: `.docx`, `.doc`, `.pdf`, `.rtf`, `.odt`, `.pages`, `.pptx`, `.xlsx`, and any binary or formatted document
|
|
70
|
+
- Source code files (`.ts`, `.tsx`, `.js`, `.py`, etc.)
|
|
71
|
+
- Config files (`package.json`, `.env`, `tsconfig.json`, etc.)
|
|
72
|
+
- Git-tracked project files in general
|
|
73
|
+
|
|
74
|
+
**Files that SHOULD be offered for Contextium routing (plain text / non-rich text only):**
|
|
75
|
+
- Plain markdown (`.md`) that is NOT part of the project source (e.g. not `README.md`, `CLAUDE.md`)
|
|
76
|
+
- Plain text (`.txt`), YAML (`.yaml`/`.yml`), or JSON files used as documentation or notes
|
|
77
|
+
- Any plain-text file the user explicitly describes as "context", "reference", or "docs"
|
|
78
|
+
|
|
79
|
+
This rule applies to both the `Write` tool and any CLI `echo`/`cat` file creation.
|
|
80
|
+
|
|
52
81
|
## Silent Operation
|
|
53
82
|
|
|
54
83
|
All MCP tool calls and CLI commands must be silent — never show the user raw API responses, tool output, or intermediate results. Only surface the final answer.
|