@funnycode/myclaude 0.1.76 → 0.1.77

package/seed/marketplaces/ecc/commands/harness-audit.md

@@ -1,84 +1,84 @@
----
-description: Run a deterministic repository harness audit and return a prioritized scorecard.
----
-
-# Harness Audit Command
-
-Run a deterministic repository harness audit and return a prioritized scorecard.
-
-## Usage
-
-`/harness-audit [scope] [--format text|json] [--root path]`
-
-- `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents`
-- `--format`: output style (`text` default, `json` for automation)
-- `--root`: audit a specific path instead of the current working directory
-
-## Deterministic Engine
-
-Always run:
-
-```bash
-node scripts/harness-audit.js <scope> --format <text|json> [--root <path>]
-```
-
-This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points.
-
-Rubric version: `2026-05-19`.
-
-The script computes up to 12 fixed categories (`0-10` normalized each). The first seven are always applicable; GitHub Integration is always applicable; deploy-target categories are applicable only when a matching marker is detected.
-
-1. Tool Coverage
-2. Context Efficiency
-3. Quality Gates
-4. Memory Persistence
-5. Eval Coverage
-6. Security Guardrails
-7. Cost Efficiency
-8. GitHub Integration
-9. Vercel Integration *(when `vercel.json` or `.vercel/` is present)*
-10. Netlify Integration *(when `netlify.toml` or `.netlify/` is present)*
-11. Cloudflare Integration *(when `wrangler.toml` or `wrangler.jsonc` is present)*
-12. Fly Integration *(when `fly.toml` is present)*
-
-Scores are derived from explicit file/rule checks and are reproducible for the same commit.
-The script audits the current working directory by default and auto-detects whether the target is the ECC repo itself or a consumer project using ECC.
-
-## Output Contract
-
-Return:
-
-1. `overall_score` out of `max_score`. `max_score` depends on which categories are applicable to the target; never assume a fixed total.
-2. `applicable_categories[]` and `category_count` describing which categories contributed.
-3. Category scores and concrete findings.
-4. Failed checks with exact file paths.
-5. Top 3 actions from the deterministic output (`top_actions`).
-6. Suggested ECC skills to apply next.
-
-## Checklist
-
-- Use script output directly; do not rescore manually.
-- If `--format json` is requested, return the script JSON unchanged.
-- If text is requested, summarize failing checks and top actions.
-- Include exact file paths from `checks[]` and `top_actions[]`.
-
-## Example Result
-
-```text
-Harness Audit (repo, repo): 71/80
-- Tool Coverage: 10/10 (10/10 pts)
-- Context Efficiency: 9/10 (9/10 pts)
-- Quality Gates: 10/10 (10/10 pts)
-- GitHub Integration: 2/10 (2/10 pts)
-
-Top 3 Actions:
-1) [GitHub Integration] Add at least one workflow under .github/workflows/. (.github/workflows/)
-2) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json)
-3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/)
-```
-
-## Arguments
-
-$ARGUMENTS:
-- `repo|hooks|skills|commands|agents` (optional scope)
-- `--format text|json` (optional output format)
+---
+description: Run a deterministic repository harness audit and return a prioritized scorecard.
+---
+
+# Harness Audit Command
+
+Run a deterministic repository harness audit and return a prioritized scorecard.
+
+## Usage
+
+`/harness-audit [scope] [--format text|json] [--root path]`
+
+- `scope` (optional): `repo` (default), `hooks`, `skills`, `commands`, `agents`
+- `--format`: output style (`text` default, `json` for automation)
+- `--root`: audit a specific path instead of the current working directory
+
+## Deterministic Engine
+
+Always run:
+
+```bash
+node scripts/harness-audit.js <scope> --format <text|json> [--root <path>]
+```
+
+This script is the source of truth for scoring and checks. Do not invent additional dimensions or ad-hoc points.
+
+Rubric version: `2026-05-19`.
+
+The script computes up to 12 fixed categories (`0-10` normalized each). The first seven are always applicable; GitHub Integration is always applicable; deploy-target categories are applicable only when a matching marker is detected.
+
+1. Tool Coverage
+2. Context Efficiency
+3. Quality Gates
+4. Memory Persistence
+5. Eval Coverage
+6. Security Guardrails
+7. Cost Efficiency
+8. GitHub Integration
+9. Vercel Integration *(when `vercel.json` or `.vercel/` is present)*
+10. Netlify Integration *(when `netlify.toml` or `.netlify/` is present)*
+11. Cloudflare Integration *(when `wrangler.toml` or `wrangler.jsonc` is present)*
+12. Fly Integration *(when `fly.toml` is present)*
+
+Scores are derived from explicit file/rule checks and are reproducible for the same commit.
+The script audits the current working directory by default and auto-detects whether the target is the ECC repo itself or a consumer project using ECC.
+
+## Output Contract
+
+Return:
+
+1. `overall_score` out of `max_score`. `max_score` depends on which categories are applicable to the target; never assume a fixed total.
+2. `applicable_categories[]` and `category_count` describing which categories contributed.
+3. Category scores and concrete findings.
+4. Failed checks with exact file paths.
+5. Top 3 actions from the deterministic output (`top_actions`).
+6. Suggested ECC skills to apply next.
+
+## Checklist
+
+- Use script output directly; do not rescore manually.
+- If `--format json` is requested, return the script JSON unchanged.
+- If text is requested, summarize failing checks and top actions.
+- Include exact file paths from `checks[]` and `top_actions[]`.
+
+## Example Result
+
+```text
+Harness Audit (repo, repo): 71/80
+- Tool Coverage: 10/10 (10/10 pts)
+- Context Efficiency: 9/10 (9/10 pts)
+- Quality Gates: 10/10 (10/10 pts)
+- GitHub Integration: 2/10 (2/10 pts)
+
+Top 3 Actions:
+1) [GitHub Integration] Add at least one workflow under .github/workflows/. (.github/workflows/)
+2) [Security Guardrails] Add prompt/tool preflight security guards in hooks/hooks.json. (hooks/hooks.json)
+3) [Eval Coverage] Increase automated test coverage across scripts/hooks/lib. (tests/)
+```
+
+## Arguments
+
+$ARGUMENTS:
+- `repo|hooks|skills|commands|agents` (optional scope)
+- `--format text|json` (optional output format)

package/seed/marketplaces/ecc/commands/hookify-configure.md

@@ -1,14 +1,14 @@
----
-description: Enable or disable hookify rules interactively
----
-
-Interactively enable or disable existing hookify rules.
-
-## Steps
-
-1. Find all `.claude/hookify.*.local.md` files
-2. Read the current state of each rule
-3. Present the list with current enabled / disabled status
-4. Ask which rules to toggle
-5. Update the `enabled:` field in the selected rule files
-6. Confirm the changes
+---
+description: Enable or disable hookify rules interactively
+---
+
+Interactively enable or disable existing hookify rules.
+
+## Steps
+
+1. Find all `.claude/hookify.*.local.md` files
+2. Read the current state of each rule
+3. Present the list with current enabled / disabled status
+4. Ask which rules to toggle
+5. Update the `enabled:` field in the selected rule files
+6. Confirm the changes

package/seed/marketplaces/ecc/commands/hookify-help.md

@@ -1,46 +1,46 @@
----
-description: Get help with the hookify system
----
-
-Display comprehensive hookify documentation.
-
-## Hook System Overview
-
-Hookify creates rule files that integrate with Claude Code's hook system to prevent unwanted behaviors.
-
-### Event Types
-
-- `bash`: triggers on Bash tool use and matches command patterns
-- `file`: triggers on Write/Edit tool use and matches file paths
-- `stop`: triggers when a session ends
-- `prompt`: triggers on user message submission and matches input patterns
-- `all`: triggers on all events
-
-### Rule File Format
-
-Files are stored as `.claude/hookify.{name}.local.md`:
-
-```yaml
----
-name: descriptive-name
-enabled: true
-event: bash|file|stop|prompt|all
-action: block|warn
-pattern: "regex pattern to match"
----
-Message to display when rule triggers.
-Supports multiple lines.
-```
-
-### Commands
-
-- `/hookify [description]` creates new rules and auto-analyzes the conversation when no description is given
-- `/hookify-list` lists configured rules
-- `/hookify-configure` toggles rules on or off
-
-### Pattern Tips
-
-- use regex syntax
-- for `bash`, match against the full command string
-- for `file`, match against the file path
-- test patterns before deploying
+---
+description: Get help with the hookify system
+---
+
+Display comprehensive hookify documentation.
+
+## Hook System Overview
+
+Hookify creates rule files that integrate with Claude Code's hook system to prevent unwanted behaviors.
+
+### Event Types
+
+- `bash`: triggers on Bash tool use and matches command patterns
+- `file`: triggers on Write/Edit tool use and matches file paths
+- `stop`: triggers when a session ends
+- `prompt`: triggers on user message submission and matches input patterns
+- `all`: triggers on all events
+
+### Rule File Format
+
+Files are stored as `.claude/hookify.{name}.local.md`:
+
+```yaml
+---
+name: descriptive-name
+enabled: true
+event: bash|file|stop|prompt|all
+action: block|warn
+pattern: "regex pattern to match"
+---
+Message to display when rule triggers.
+Supports multiple lines.
+```
+
+### Commands
+
+- `/hookify [description]` creates new rules and auto-analyzes the conversation when no description is given
+- `/hookify-list` lists configured rules
+- `/hookify-configure` toggles rules on or off
+
+### Pattern Tips
+
+- use regex syntax
+- for `bash`, match against the full command string
+- for `file`, match against the file path
+- test patterns before deploying

package/seed/marketplaces/ecc/commands/hookify-list.md

@@ -1,21 +1,21 @@
----
-description: List all configured hookify rules
----
-
-Find and display all hookify rules in a formatted table.
-
-## Steps
-
-1. Find all `.claude/hookify.*.local.md` files
-2. Read each file's frontmatter:
-   - `name`
-   - `enabled`
-   - `event`
-   - `action`
-   - `pattern`
-3. Display them as a table:
-
-| Rule | Enabled | Event | Pattern | File |
-|------|---------|-------|---------|------|
-
-4. Show the rule count and remind the user that `/hookify-configure` can change state later.
+---
+description: List all configured hookify rules
+---
+
+Find and display all hookify rules in a formatted table.
+
+## Steps
+
+1. Find all `.claude/hookify.*.local.md` files
+2. Read each file's frontmatter:
+   - `name`
+   - `enabled`
+   - `event`
+   - `action`
+   - `pattern`
+3. Display them as a table:
+
+| Rule | Enabled | Event | Pattern | File |
+|------|---------|-------|---------|------|
+
+4. Show the rule count and remind the user that `/hookify-configure` can change state later.

package/seed/marketplaces/ecc/commands/hookify.md

@@ -1,50 +1,50 @@
----
-description: Create hooks to prevent unwanted behaviors from conversation analysis or explicit instructions
----
-
-Create hook rules to prevent unwanted Claude Code behaviors by analyzing conversation patterns or explicit user instructions.
-
-## Usage
-
-`/hookify [description of behavior to prevent]`
-
-If no arguments are provided, analyze the current conversation to find behaviors worth preventing.
-
-## Workflow
-
-### Step 1: Gather Behavior Info
-
-- With arguments: parse the user's description of the unwanted behavior
-- Without arguments: use the `conversation-analyzer` agent to find:
-  - explicit corrections
-  - frustrated reactions to repeated mistakes
-  - reverted changes
-  - repeated similar issues
-
-### Step 2: Present Findings
-
-Show the user:
-
-- behavior description
-- proposed event type
-- proposed pattern or matcher
-- proposed action
-
-### Step 3: Generate Rule Files
-
-For each approved rule, create a file at `.claude/hookify.{name}.local.md`:
-
-```yaml
----
-name: rule-name
-enabled: true
-event: bash|file|stop|prompt|all
-action: block|warn
-pattern: "regex pattern"
----
-Message shown when rule triggers.
-```
-
-### Step 4: Confirm
-
-Report created rules and how to manage them with `/hookify-list` and `/hookify-configure`.
+---
+description: Create hooks to prevent unwanted behaviors from conversation analysis or explicit instructions
+---
+
+Create hook rules to prevent unwanted Claude Code behaviors by analyzing conversation patterns or explicit user instructions.
+
+## Usage
+
+`/hookify [description of behavior to prevent]`
+
+If no arguments are provided, analyze the current conversation to find behaviors worth preventing.
+
+## Workflow
+
+### Step 1: Gather Behavior Info
+
+- With arguments: parse the user's description of the unwanted behavior
+- Without arguments: use the `conversation-analyzer` agent to find:
+  - explicit corrections
+  - frustrated reactions to repeated mistakes
+  - reverted changes
+  - repeated similar issues
+
+### Step 2: Present Findings
+
+Show the user:
+
+- behavior description
+- proposed event type
+- proposed pattern or matcher
+- proposed action
+
+### Step 3: Generate Rule Files
+
+For each approved rule, create a file at `.claude/hookify.{name}.local.md`:
+
+```yaml
+---
+name: rule-name
+enabled: true
+event: bash|file|stop|prompt|all
+action: block|warn
+pattern: "regex pattern"
+---
+Message shown when rule triggers.
+```
+
+### Step 4: Confirm
+
+Report created rules and how to manage them with `/hookify-list` and `/hookify-configure`.

package/seed/marketplaces/ecc/commands/instinct-export.md

@@ -1,66 +1,66 @@
----
-name: instinct-export
-description: Export instincts from project/global scope to a file
-command: /instinct-export
----
-
-# Instinct Export Command
-
-Exports instincts to a shareable format. Perfect for:
-- Sharing with teammates
-- Transferring to a new machine
-- Contributing to project conventions
-
-## Usage
-
-```
-/instinct-export                           # Export all personal instincts
-/instinct-export --domain testing          # Export only testing instincts
-/instinct-export --min-confidence 0.7      # Only export high-confidence instincts
-/instinct-export --output team-instincts.yaml
-/instinct-export --scope project --output project-instincts.yaml
-```
-
-## What to Do
-
-1. Detect current project context
-2. Load instincts by selected scope:
-   - `project`: current project only
-   - `global`: global only
-   - `all`: project + global merged (default)
-3. Apply filters (`--domain`, `--min-confidence`)
-4. Write YAML-style export to file (or stdout if no output path provided)
-
-## Output Format
-
-Creates a YAML file:
-
-```yaml
-# Instincts Export
-# Generated: 2025-01-22
-# Source: personal
-# Count: 12 instincts
-
----
-id: prefer-functional-style
-trigger: "when writing new functions"
-confidence: 0.8
-domain: code-style
-source: session-observation
-scope: project
-project_id: a1b2c3d4e5f6
-project_name: my-app
----
-
-# Prefer Functional Style
-
-## Action
-Use functional patterns over classes.
-```
-
-## Flags
-
-- `--domain <name>`: Export only specified domain
-- `--min-confidence <n>`: Minimum confidence threshold
-- `--output <file>`: Output file path (prints to stdout when omitted)
-- `--scope <project|global|all>`: Export scope (default: `all`)
+---
+name: instinct-export
+description: Export instincts from project/global scope to a file
+command: /instinct-export
+---
+
+# Instinct Export Command
+
+Exports instincts to a shareable format. Perfect for:
+- Sharing with teammates
+- Transferring to a new machine
+- Contributing to project conventions
+
+## Usage
+
+```
+/instinct-export                           # Export all personal instincts
+/instinct-export --domain testing          # Export only testing instincts
+/instinct-export --min-confidence 0.7      # Only export high-confidence instincts
+/instinct-export --output team-instincts.yaml
+/instinct-export --scope project --output project-instincts.yaml
+```
+
+## What to Do
+
+1. Detect current project context
+2. Load instincts by selected scope:
+   - `project`: current project only
+   - `global`: global only
+   - `all`: project + global merged (default)
+3. Apply filters (`--domain`, `--min-confidence`)
+4. Write YAML-style export to file (or stdout if no output path provided)
+
+## Output Format
+
+Creates a YAML file:
+
+```yaml
+# Instincts Export
+# Generated: 2025-01-22
+# Source: personal
+# Count: 12 instincts
+
+---
+id: prefer-functional-style
+trigger: "when writing new functions"
+confidence: 0.8
+domain: code-style
+source: session-observation
+scope: project
+project_id: a1b2c3d4e5f6
+project_name: my-app
+---
+
+# Prefer Functional Style
+
+## Action
+Use functional patterns over classes.
+```
+
+## Flags
+
+- `--domain <name>`: Export only specified domain
+- `--min-confidence <n>`: Minimum confidence threshold
+- `--output <file>`: Output file path (prints to stdout when omitted)
+- `--scope <project|global|all>`: Export scope (default: `all`)