@codeyam/codeyam-cli 0.1.0-staging.483fdc2 → 0.1.0-staging.4c0c3c9

package/codeyam-cli/templates/{codeyam:memory.md → codeyam-memory.md}

@@ -1,5 +1,5 @@
 ---
-name: codeyam:memory
+name: codeyam-memory
 autoApprove: true
 description: |
   Generate and maintain Claude Rules for your codebase based on thorough analysis.
@@ -13,19 +13,14 @@ This skill helps you generate and maintain Claude Rules (`.claude/rules/`) that
 
 ## Core Principle: Document Confusion, Not Information
 
-**Good rules** explain things that are NOT obvious from reading the code:
+**Valuable rules** capture knowledge that reading the code alone wouldn't reveal:
 
 - Historical context (why code evolved this way)
 - Hidden relationships (files that must change together)
 - Gotchas that caused bugs
 - Non-obvious conventions
 
-**Bad rules** document things Claude can easily ascertain:
-
-- What functions do (Claude can read the code)
-- Type definitions (Claude can see them)
-- Directory structure (Claude can explore it)
-- Basic patterns (Claude knows common patterns)
+Skip documenting things Claude can determine by reading code: function signatures, type definitions, directory structure, and common patterns.
 
 ## When to Use This Skill
 
@@ -41,24 +36,30 @@ Check if this is the first time running memory.
 
 ### 1A. Add Documentation Section to CLAUDE.md
 
-If CLAUDE.md doesn't contain a "When Confused / With Mistakes" section, add close to the top:
+If CLAUDE.md already contains a "Documenting Confusion / Mistakes" section, skip this step entirely.
+
+Otherwise, add **only** the section below — do not modify or add any other content to CLAUDE.md. If CLAUDE.md doesn't exist, create it with just a `# Project` heading followed by this section:
 
 ```markdown
-## When Confused / With Mistakes: Stop. Ask. Document.
+## Continuous Documentation
+
+As you work, think about any information that might be helpful to know in future work sessions without the user re-providing the information.
 
-- If you are not sure about something stop and ask about it.
-- If you attempt something and it goes wrong then you are confused. Stop and ask about it.
-- If the user is unable to help. Do your best to research.
-- Then document the findings!
+This might include
+
+- High-level architecture for complex areas of the codebase (if not obvious)
+- Specific commands that are recommended
+- Debugging strategies for complex areas of the codebase (if not obvious)
+- Anything confusing that is encountered in the work session
 
 ### Documenting Confusion / Mistakes
 
-It is very important to document any confusion or mistakes you encounter in Claude Rules (`.claude/rules`).
+It is very important to document any tribal knowledge, complex architectural decisions, and any confusion or mistakes you encounter in Claude Rules (`.claude/rules`).
 Please see `.codeyam/rules/instructions.md` for guidance.
-
-After making any code changes please run `codeyam memory status` and follow the instructions.
 ```
 
+**Important:** Do not add project descriptions, architecture summaries, or any other content to CLAUDE.md. Only add the exact section above.
+
 ### 1B. Verify Instructions File
 
 Check that `.codeyam/rules/instructions.md` exists (it should be created during `codeyam init`). If missing, copy it from `codeyam-cli/templates/rules-instructions.md`.
@@ -273,7 +274,7 @@ Before generating each rule, verify it passes these tests:
 
 **2. Code-derivable check**: Read the files the rule will cover. Could the rule's content be determined by reading those files alone?
 
-- If YES → rule probably not needed (Claude can read the code)
+- If YES → the code is its own documentation — prefer keeping rules for non-derivable insights
 - If NO (historical context, edge cases, non-obvious behavior) → rule is valuable
 
 **3. Prevention check**: Would this rule have prevented one of the confusion commits you found?
@@ -299,7 +300,7 @@ This caused a bug where `entity` matched `entityCode` (siblings, not parent-chil
 - Not code-derivable: Code doesn't explain why boundary checking matters
 - Prevention: Would prevent future prefix-matching bugs
 
-**❌ Bad rule** (fails tests):
+**Compare with a weaker alternative** (fails the checks):
 
 ```markdown
 ## Running Tests
@@ -307,9 +308,7 @@ This caused a bug where `entity` matched `entityCode` (siblings, not parent-chil
 Use `pnpm jest` to run tests. Configuration is in `jest.config.ts`.
 ```
 
-- No confusion evidence (no commits showing people struggled with this)
-- Code-derivable: Anyone can see `jest.config.ts` exists
-- Doesn't prevent any confusion
+- No confusion evidence, code-derivable, and wouldn't prevent future mistakes
 
 ### 5B. Rule File Guidelines
 
@@ -317,17 +316,13 @@ Use `pnpm jest` to run tests. Configuration is in `jest.config.ts`.
    - Rule for `src/api/` → `.claude/rules/src/api/architecture.md`
    - Rule for testing patterns → `.claude/rules/testing-patterns.md`
 
-2. **Paths must be specific**
-   - Good: `paths: ['src/api/**/*.ts']`
-   - Bad: `paths: ['**/*.ts']` (too broad, wastes context)
+2. **Paths must be specific** — use `paths: ['src/api/**/*.ts']` rather than `'**/*.ts'` (too broad wastes context)
 
 3. **Content should explain "why" not just "what"**
    - Focus on the reasoning, history, or gotcha
    - Be concise - every word costs context
 
-4. **Timestamp must be current**
-   - Use ISO 8601 format: `2026-01-27T15:30:00Z`
-   - This enables the pre-commit hook enforcement
+4. **Audit dates live in `.claude/codeyam-rule-state.json`** (managed by `codeyam memory touch`). Keep rule frontmatter limited to `paths`.
 
 ### Rule Template
 
@@ -335,8 +330,6 @@ Use `pnpm jest` to run tests. Configuration is in `jest.config.ts`.
 ---
 paths:
   - 'specific/path/**/*.ts'
-category: architecture | testing | faq
-timestamp: [CURRENT_ISO_TIMESTAMP]
 ---
 
 ## [Clear, Descriptive Title]
@@ -373,7 +366,7 @@ After generating rules based on your analysis and user answers:
 5. **Remind the user** to commit the new rules:
    ```
    git add .claude/rules/ .codeyam/rules/
-   git commit -m "Add rules for Claude Code (generated via /codeyam:memory)"
+   git commit -m "Add rules for Claude Code (generated via /codeyam-memory)"
    ```
 
 ---
@@ -393,11 +386,11 @@ After generating rules based on your analysis and user answers:
 The pre-commit hook **blocks commits** when:
 
 - Code files matching a rule's `paths` are modified
-- The rule's `timestamp` is older than the code changes
+- The rule's `lastAuditedAt` in `.claude/codeyam-rule-state.json` is older than the code changes
 
 To proceed:
 
 1. Review the flagged rule(s)
 2. Update content if needed
-3. Update the `timestamp` to current time
+3. Run `codeyam memory touch` to mark rules as audited in `.claude/codeyam-rule-state.json`
 4. Stage and commit

package/codeyam-cli/templates/codeyam-new-rule.md

@@ -0,0 +1,13 @@
+---
+name: codeyam-new-rule
+autoApprove: true
+description: |
+  Create a new Claude Rule for documenting codebase patterns.
+  Use when: User wants to add documentation for a specific area of the codebase.
+---
+
+# Create New Claude Rule
+
+Read `.codeyam/rules/instructions.md` for detailed guidance on structure and formatting.
+
+If the instructions file doesn't exist, copy it from `codeyam-cli/templates/rules-instructions.md`.

package/codeyam-cli/templates/{codeyam:setup.md → codeyam-setup.md}

@@ -1,5 +1,5 @@
 ---
-name: codeyam:setup
+name: codeyam-setup
 autoApprove: true
 description: |
   Use this skill when the user asks to "setup CodeYam" or needs to configure CodeYam for their project.
@@ -52,6 +52,18 @@ codeyam validate-mock .codeyam/universal-mocks/{path-to-your-mock}
 
 ## Setup Workflow
 
+### Step 0: Ensure Simulation Infrastructure
+
+Before configuring the dev server or mocks, ensure the simulation infrastructure is installed.
+
+```bash
+codeyam setup-simulations
+```
+
+This is **idempotent** — if already set up, each step is detected and skipped. On first run it installs analyzer dependencies, Playwright chromium, and creates baseline entities (several minutes). Subsequent runs complete in seconds.
+
+If it fails with "No web applications found", the project doesn't support simulations — inform the user and stop.
+
 ### Step 1: Configure Webapp Start Command
 
 **ACTION 1:** Read configuration files:

package/codeyam-cli/templates/{codeyam:sim.md → codeyam-sim.md}

@@ -1,5 +1,5 @@
 ---
-name: codeyam:sim
+name: codeyam-sim
 autoApprove: true
 description: |
   Use this skill to create interactive simulations of components and functions using CodeYam's analysis.

package/codeyam-cli/templates/{codeyam:test.md → codeyam-test.md}

@@ -1,5 +1,5 @@
 ---
-name: codeyam:test
+name: codeyam-test
 autoApprove: true
 description: |
   Use this skill to write comprehensive unit and integration tests using CodeYam's mock generation.

package/codeyam-cli/templates/{codeyam:verify.md → codeyam-verify.md}

@@ -1,5 +1,5 @@
 ---
-name: codeyam:verify
+name: codeyam-verify
 autoApprove: true
 description: |
   Use this skill after making code changes that impact application functionality.

package/codeyam-cli/templates/rule-notification-hook.py

@@ -0,0 +1,56 @@
+#!/usr/bin/env python3
+"""
+UserPromptSubmit hook: surfaces rule-reflection notifications to the main session.
+
+The background rule-reflection agents write summaries to notification files
+in /tmp/claude-rule-markers/ when they create or update rules.
+This hook checks for those files on each user message, prints them to stdout
+(which Claude sees as injected context), and deletes them.
+
+Supports four notification files (legacy combined + split agents):
+- rule-notification.md (legacy/backward-compat)
+- rule-notification-stale.md (stale rules agent)
+- rule-notification-conversation.md (conversation review agent)
+- rule-notification-interruption.md (interruption review agent)
+"""
+
+import os
+import sys
+
+MARKER_DIR = '/tmp/claude-rule-markers'
+NOTIFICATION_FILES = [
+    'rule-notification.md',
+    'rule-notification-stale.md',
+    'rule-notification-conversation.md',
+    'rule-notification-interruption.md',
+]
+
+
+def main():
+    collected = []
+
+    for filename in NOTIFICATION_FILES:
+        filepath = os.path.join(MARKER_DIR, filename)
+        if not os.path.exists(filepath):
+            continue
+
+        try:
+            with open(filepath, 'r') as f:
+                content = f.read().strip()
+        except IOError:
+            continue
+
+        if content:
+            collected.append(content)
+
+        try:
+            os.remove(filepath)
+        except OSError:
+            pass
+
+    if collected:
+        print('\n\n'.join(collected))
+
+
+if __name__ == '__main__':
+    main()