@nolrm/contextkit 1.0.0 → 1.0.1

package/lib/commands/install.js

@@ -584,7 +584,7 @@ All documentation follows a 3-level hierarchy. Each level answers a different qu
 
 High-level system documentation: how the system is structured and how parts interact.
 
-- **Location:** \`docs/architecture.md\` in the project root (or any root-level docs folder)
+- **Location:** Named file in the project root or a \`docs/\` folder (e.g. \`docs/architecture.md\`, \`docs/auth.md\`) — one file per concern, not everything in \`README.md\`
 - **Scope:** Whole product, platform, or cross-cutting feature
 - **Content:** System/domain boundaries, main flows, how services/apps/packages connect and communicate
 - **Artifacts:** Diagrams (Mermaid or similar) for routing, sequence flows, context/containers; architecture decision notes; shared patterns and conventions
@@ -594,6 +594,7 @@ High-level system documentation: how the system is structured and how parts inte
 
 Documentation for a full screen, route, or feature area — the containers that hold many components.
 
+- **Standard filename:** \`README.md\` in the feature/page directory
 - **Scope:** One app, one major feature, or one route/page
 - **Content:** Purpose of the page/feature, main sections and layout, which components and hooks are used, data/state and API usage, key user flows
 - **Artifacts:** Feature or page READMEs; lists of subcomponents and responsibilities; optional simple flow or layout sketches
@@ -603,9 +604,10 @@ Documentation for a full screen, route, or feature area — the containers that
 
 Documentation for a single component or a small, cohesive set of components.
 
+- **Standard filename:** \`README.md\` colocated with the component
 - **Scope:** One component (or a tight group)
 - **Content:** What the component does, props/API, usage examples, behavior and edge cases, where it's used
-- **Artifacts:** README colocated next to the component; props table; code snippets
+- **Artifacts:** \`README.md\` colocated next to the component; props table; code snippets
 - **Audience:** Developers implementing or reusing the component
 
 ## Project Architecture
@@ -645,6 +647,16 @@ Load standards files in this priority order to use your context window efficient
 
 If a standards file is longer than 200 lines, read the sections relevant to your task — not the whole file.
 
+## README.md Context Discovery
+
+\`README.md\` is the standard context file at all 3 documentation levels. Before starting work in any directory or on any feature, check for it:
+
+- **Architecture level**: project root or \`docs/\` directory
+- **Feature/page level**: the directory containing the feature, route, or page you are working in
+- **Component level**: the directory containing the component you are modifying
+
+If a \`README.md\` exists at any of these levels relevant to your task, read it before acting. These files capture decisions, conventions, and context that the codebase alone does not reveal.
+
 ## Standards Loop
 
 This project follows a continuous standards loop:

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nolrm/contextkit",
-  "version": "1.0.0",
+  "version": "1.0.1",
   "description": "ContextKit - Context Engineering + Agentic AI Pipelines. Scaffold structured standards for AI assistants and run autonomous multi-role pipelines (PO → Architect → Dev → Test → Review → Doc) grounded by that same context layer. Works with Cursor, Claude Code, Copilot, Codex, Gemini, Aider, and more.",
   "main": "lib/index.js",
   "bin": {