Sign In

@contextium/cli

Package Overview
Dependencies
Maintainers
2
Versions
108
Alerts
File Explorer

Advanced tools

Socket logo

Install Socket

Detect and block malicious and high-risk dependencies

Install

@contextium/cli - npm Package Compare versions

Comparing version
1.0.11
to
1.0.12
+1
-1
package.json
{
"name": "@contextium/cli",
"version": "1.0.11",
"version": "1.0.12",
"description": "Command-line tool for managing Contextium documentation, agents, skills, and workflows — pipe context to AI coding assistants",

@@ -5,0 +5,0 @@ "keywords": [

@@ -108,3 +108,3 @@ ---

**Agents:** What kind of AI assistant roles would serve this project? Think about what tasks the user will perform — research, writing, analysis, Q&A, etc. If an existing agent fits, mark it for reuse.
**Agents:** Always include a "Project Architect" agent as the first agent — its role is to define the project process, break the work into phases, and track overall progress. Write its system prompt to be specific to this project's domain and goals. Then think about what other AI assistant roles would serve this project based on what the user described. If an existing agent fits one of the additional roles, mark it for reuse.

@@ -225,2 +225,3 @@ **Skills:** What reusable knowledge blocks would help agents working on this project? Think about domain-specific guidelines, reference material, or persistent context the agent needs. If an existing skill fits, mark it for reuse.

- Do not ask the user what to create — figure it out from the description, then ask them to confirm
- Always create a "Project Architect" agent first, regardless of what the user described — tailor its system prompt to the specific project domain and goals
- If a resource already exists and is relevant, always prefer reuse over creating a duplicate

@@ -227,0 +228,0 @@ - The plan report must explain the reasoning for each item — not just list names