bobo-ai-cli 3.0.4 → 3.0.5

package/knowledge/skills/example-plugin.md

@@ -1,72 +1,72 @@
----
-id: "example-plugin"
-title: "Example Plugin"
-category: "other"
-tags: ["example plugin", "structure", "extension options", "usage"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/example-plugin"
----
-
-# Example Plugin
-
-A comprehensive example plugin demonstrating Claude Code extension options.
-
-## Structure
-
-```
-example-plugin/
-├── .claude-plugin/
-│   └── plugin.json        # Plugin metadata
-├── .mcp.json              # MCP server configuration
-├── commands/
-│   └── example-command.md # Slash command definition
-└── skills/
-    └── example-skill/
-        └── SKILL.md       # Skill definition
-```
-
-## Extension Options
-
-### Commands (`commands/`)
-
-Slash commands are user-invoked via `/command-name`. Define them as markdown files with frontmatter:
-
-```yaml
----
-description: Short description for /help
-argument-hint: <arg1> [optional-arg]
-allowed-tools: [Read, Glob, Grep]
----
-```
-
-### Skills (`skills/`)
-
-Skills are model-invoked capabilities. Create a `SKILL.md` in a subdirectory:
-
-```yaml
----
-name: skill-name
-description: Trigger conditions for this skill
-version: 1.0.0
----
-```
-
-### MCP Servers (`.mcp.json`)
-
-Configure external tool integration via Model Context Protocol:
-
-```json
-{
-  "server-name": {
-    "type": "http",
-    "url": "https://mcp.example.com/api"
-  }
-}
-```
-
-## Usage
-
-- `/example-command [args]` - Run the example slash command
-- The example skill activates based on task context
-- The example MCP activates based on task context
+---
+id: "example-plugin"
+title: "Example Plugin"
+category: "other"
+tags: ["example plugin", "structure", "extension options", "usage"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/example-plugin"
+---
+
+# Example Plugin
+
+A comprehensive example plugin demonstrating Claude Code extension options.
+
+## Structure
+
+```
+example-plugin/
+├── .claude-plugin/
+│   └── plugin.json        # Plugin metadata
+├── .mcp.json              # MCP server configuration
+├── commands/
+│   └── example-command.md # Slash command definition
+└── skills/
+    └── example-skill/
+        └── SKILL.md       # Skill definition
+```
+
+## Extension Options
+
+### Commands (`commands/`)
+
+Slash commands are user-invoked via `/command-name`. Define them as markdown files with frontmatter:
+
+```yaml
+---
+description: Short description for /help
+argument-hint: <arg1> [optional-arg]
+allowed-tools: [Read, Glob, Grep]
+---
+```
+
+### Skills (`skills/`)
+
+Skills are model-invoked capabilities. Create a `SKILL.md` in a subdirectory:
+
+```yaml
+---
+name: skill-name
+description: Trigger conditions for this skill
+version: 1.0.0
+---
+```
+
+### MCP Servers (`.mcp.json`)
+
+Configure external tool integration via Model Context Protocol:
+
+```json
+{
+  "server-name": {
+    "type": "http",
+    "url": "https://mcp.example.com/api"
+  }
+}
+```
+
+## Usage
+
+- `/example-command [args]` - Run the example slash command
+- The example skill activates based on task context
+- The example MCP activates based on task context

package/knowledge/skills/explanatory-output-style.md

@@ -1,82 +1,82 @@
----
-id: "explanatory-output-style"
-title: "Explanatory Output Style Plugin"
-category: "knowledge"
-tags: ["what it does", "how it works", "usage", "migration from output styles", "managing changes"]
-triggers: []
-dependencies: []
-source: "E:/Bobo's Coding cache/.claude/skills/explanatory-output-style"
----
-
-# Explanatory Output Style Plugin
-
-This plugin recreates the deprecated Explanatory output style as a SessionStart
-hook.
-
-WARNING: Do not install this plugin unless you are fine with incurring the token
-cost of this plugin's additional instructions and output.
-
-## What it does
-
-When enabled, this plugin automatically adds instructions at the start of each
-session that encourage Claude to:
-
-1. Provide educational insights about implementation choices
-2. Explain codebase patterns and decisions
-3. Balance task completion with learning opportunities
-
-## How it works
-
-The plugin uses a SessionStart hook to inject additional context into every
-session. This context instructs Claude to provide brief educational explanations
-before and after writing code, formatted as:
-
-```
-`★ Insight ─────────────────────────────────────`
-[2-3 key educational points]
-`─────────────────────────────────────────────────`
-```
-
-## Usage
-
-Once installed, the plugin activates automatically at the start of every
-session. No additional configuration is needed.
-
-The insights focus on:
-
-- Specific implementation choices for your codebase
-- Patterns and conventions in your code
-- Trade-offs and design decisions
-- Codebase-specific details rather than general programming concepts
-
-## Migration from Output Styles
-
-This plugin replaces the deprecated "Explanatory" output style setting. If you
-previously used:
-
-```json
-{
-  "outputStyle": "Explanatory"
-}
-```
-
-You can now achieve the same behavior by installing this plugin instead.
-
-More generally, this SessionStart hook pattern is roughly equivalent to
-CLAUDE.md, but it is more flexible and allows for distribution through plugins.
-
-Note: Output styles that involve tasks besides software development, are better
-expressed as
-[subagents](https://docs.claude.com/en/docs/claude-code/sub-agents), not as
-SessionStart hooks. Subagents change the system prompt while SessionStart hooks
-add to the default system prompt.
-
-## Managing changes
-
-- Disable the plugin - keep the code installed on your device
-- Uninstall the plugin - remove the code from your device
-- Update the plugin - create a local copy of this plugin to personalize this
-  plugin
-  - Hint: Ask Claude to read
-    https://docs.claude.com/en/docs/claude-code/plugins.md and set it up for
-    you!
+---
+id: "explanatory-output-style"
+title: "Explanatory Output Style Plugin"
+category: "knowledge"
+tags: ["what it does", "how it works", "usage", "migration from output styles", "managing changes"]
+triggers: []
+dependencies: []
+source: "E:/Bobo's Coding cache/.claude/skills/explanatory-output-style"
+---
+
+# Explanatory Output Style Plugin
+
+This plugin recreates the deprecated Explanatory output style as a SessionStart
+hook.
+
+WARNING: Do not install this plugin unless you are fine with incurring the token
+cost of this plugin's additional instructions and output.
+
+## What it does
+
+When enabled, this plugin automatically adds instructions at the start of each
+session that encourage Claude to:
+
+1. Provide educational insights about implementation choices
+2. Explain codebase patterns and decisions
+3. Balance task completion with learning opportunities
+
+## How it works
+
+The plugin uses a SessionStart hook to inject additional context into every
+session. This context instructs Claude to provide brief educational explanations
+before and after writing code, formatted as:
+
+```
+`★ Insight ─────────────────────────────────────`
+[2-3 key educational points]
+`─────────────────────────────────────────────────`
+```
+
+## Usage
+
+Once installed, the plugin activates automatically at the start of every
+session. No additional configuration is needed.
+
+The insights focus on:
+
+- Specific implementation choices for your codebase
+- Patterns and conventions in your code
+- Trade-offs and design decisions
+- Codebase-specific details rather than general programming concepts
+
+## Migration from Output Styles
+
+This plugin replaces the deprecated "Explanatory" output style setting. If you
+previously used:
+
+```json
+{
+  "outputStyle": "Explanatory"
+}
+```
+
+You can now achieve the same behavior by installing this plugin instead.
+
+More generally, this SessionStart hook pattern is roughly equivalent to
+CLAUDE.md, but it is more flexible and allows for distribution through plugins.
+
+Note: Output styles that involve tasks besides software development, are better
+expressed as
+[subagents](https://docs.claude.com/en/docs/claude-code/sub-agents), not as
+SessionStart hooks. Subagents change the system prompt while SessionStart hooks
+add to the default system prompt.
+
+## Managing changes
+
+- Disable the plugin - keep the code installed on your device
+- Uninstall the plugin - remove the code from your device
+- Update the plugin - create a local copy of this plugin to personalize this
+  plugin
+  - Hint: Ask Claude to read
+    https://docs.claude.com/en/docs/claude-code/plugins.md and set it up for
+    you!