claude-code-tutor 1.0.0

package/dist/meta-TZOSLFST.js

@@ -0,0 +1,13 @@
+#!/usr/bin/env node
+import {
+  getMetaPath,
+  isStale,
+  readMeta,
+  writeMeta
+} from "./chunk-OYDUGORC.js";
+export {
+  getMetaPath,
+  isStale,
+  readMeta,
+  writeMeta
+};

package/dist/tutor-memory-M6GNB3LQ.js

@@ -0,0 +1,19 @@
+#!/usr/bin/env node
+import {
+  getBaseDir,
+  getDefaultMemory,
+  logSession,
+  readMemory,
+  setBaseDir,
+  updateMemory,
+  writeMemory
+} from "./chunk-A6ZZXTHB.js";
+export {
+  getBaseDir,
+  getDefaultMemory,
+  logSession,
+  readMemory,
+  setBaseDir,
+  updateMemory,
+  writeMemory
+};

package/package.json

@@ -0,0 +1,61 @@
+{
+  "name": "claude-code-tutor",
+  "version": "1.0.0",
+  "description": "Keep Claude Code alive. Fresh docs, built-in tutor, always in sync.",
+  "type": "module",
+  "bin": {
+    "pulse": "./dist/cli.js"
+  },
+  "files": [
+    "dist",
+    "skills-fallback",
+    "README.md"
+  ],
+  "keywords": [
+    "claude-code",
+    "claude",
+    "anthropic",
+    "skills",
+    "ai",
+    "developer-tools",
+    "mcp",
+    "hooks",
+    "tutor"
+  ],
+  "author": "Erik Rodriguez",
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "https://github.com/Erikole21/claude-code-tutor.git"
+  },
+  "homepage": "https://github.com/Erikole21/claude-code-tutor#readme",
+  "bugs": {
+    "url": "https://github.com/Erikole21/claude-code-tutor/issues"
+  },
+  "engines": {
+    "node": ">=18"
+  },
+  "scripts": {
+    "build": "tsup",
+    "build:skills": "tsx scripts/generate-fallback-skills.ts",
+    "dev": "tsx src/cli.ts",
+    "test": "vitest",
+    "prepublishOnly": "npm run build && npm run build:skills"
+  },
+  "dependencies": {
+    "commander": "^12.1.0",
+    "cosmiconfig": "^9.0.0",
+    "p-limit": "^6.1.0",
+    "remark-parse": "^11.0.0",
+    "remark-stringify": "^11.0.0",
+    "undici": "^6.19.0",
+    "unified": "^11.0.5"
+  },
+  "devDependencies": {
+    "@types/node": "^20.14.0",
+    "tsup": "^8.1.0",
+    "tsx": "^4.15.0",
+    "typescript": "^5.5.0",
+    "vitest": "^1.6.0"
+  }
+}

package/skills-fallback/cc-agent-teams/SKILL.md

@@ -0,0 +1,38 @@
+---
+name: cc-agent-teams
+description: "Agent teams en Claude Code: coordinar múltiples sesiones, asignar tareas, hablar con teammates, display modes, token costs."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/agent-teams.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Orchestrate teams of Claude Code sessions
+
+> Coordinate multiple Claude Code instances working together as a team, with shared tasks, inter-agent messaging, and centralized management.
+
+Agent teams let you coordinate multiple Claude Code instances working together. One session acts as the team lead, coordinating work, assigning tasks, and synthesizing results. Teammates work independently, each in its own context window, and communicate directly with each other.
+
+Unlike [subagents](/en/sub-agents), which run within a single session and can only report back to the main agent, you can also interact with individual teammates directly without going through the lead.
+
+This page covers:
+
+- [When to use agent teams](#when-to-use-agent-teams), including best use cases and how they compare with subagents
+- [Starting a team](#start-your-first-agent-team)
+- [Controlling teammates](#control-your-agent-team), including display modes, task assignment, and delegation
+- [Best practices for parallel work](#best-practices)
+
+## When to use agent teams
+
+Agent teams are most effective for tasks where parallel exploration adds real value. See [use case examples](#use-case-examples) for full scenarios. The strongest use cases are:
+
+- **Research and review**: multiple teammates can investigate different aspects of a problem simultaneously, then share and challenge each other's findings
+- **New modules or features**: teammates can each own a separate piece without stepping on each other
+- **Debugging with competing hypotheses**: teammates test different theories in parallel and converge on the answer faster
+- **Cross-layer coordination**: changes that span frontend, backend, and tests, each owned by a different teammate
+
+Agent teams add coordination overhead and use significantly more tokens than a single session. They work best when teammates can operate independently. For sequential tasks, same-file edits, or work with many dependencies, a single session or [subagents](/en/sub-agents) are more effective.

package/skills-fallback/cc-best-practices/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: cc-best-practices
+description: "Best practices de Claude Code: dar contexto efectivo, gestionar contexto, course-correct, evitar patrones de fallo comunes."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/best-practices.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Best Practices for Claude Code
+
+> Tips and patterns for getting the most out of Claude Code, from configuring your environment to scaling across parallel sessions.
+
+Claude Code is an agentic coding environment. Unlike a chatbot that answers questions and waits, Claude Code can read your files, run commands, make changes, and autonomously work through problems while you watch, redirect, or step away entirely.
+
+This changes how you work. Instead of writing code yourself and asking Claude to review it, you describe what you want and Claude figures out how to build it. Claude explores, plans, and implements.
+
+But this autonomy still comes with a learning curve. Claude works within certain constraints you need to understand.
+
+This guide covers patterns that have proven effective across Anthropic's internal teams and for engineers using Claude Code across various codebases, languages, and environments. For how the agentic loop works under the hood, see [How Claude Code works](/en/how-claude-code-works).
+
+***
+
+Most best practices are based on one constraint: Claude's context window fills up fast, and performance degrades as it fills.
+
+Claude's context window holds your entire conversation, including every message, every file Claude reads, and every command output. However, this can fill up fast. A single debugging session or codebase exploration might generate and consume tens of thousands of tokens.
+
+This matters since LLM performance degrades as context fills. When the context window is getting full, Claude may start "forgetting" earlier instructions or making more mistakes. The context window is the most important resource to manage. To see how a session fills up in practice, [watch an interactive walkthrough](/en/context-window) of what loads at startup and what each file read costs. Track context usage continuously with a [custom status line](/en/statusline), and see [Reduce token usage](/en/costs#reduce-token-usage) for strategies on reducing token usage.
+
+***

package/skills-fallback/cc-changelog/SKILL.md

@@ -0,0 +1,20 @@
+---
+name: cc-changelog
+description: "Changelog y novedades recientes de Claude Code. Úsame cuando pregunten qué hay de nuevo, qué cambió en una versión, o qué features se agregaron recientemente."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/changelog.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Changelog
+
+> Release notes for Claude Code, including new features, improvements, and bug fixes by version.
+
+This page is generated from the [CHANGELOG.md on GitHub](https://github.com/anthropics/claude-code/blob/main/CHANGELOG.md).
+
+Run `claude --version` to check your installed version.

package/skills-fallback/cc-channels/SKILL.md

@@ -0,0 +1,34 @@
+---
+name: cc-channels
+description: "Channels en Claude Code: push events a sesiones activas, webhooks, alertas de CI, chat messages desde MCP server."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/channels.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# Push events into a running session with channels
+
+> Use channels to push messages, alerts, and webhooks into your Claude Code session from an MCP server. Forward CI results, chat messages, and monitoring events so Claude can react while you're away.
+
+A channel is an MCP server that pushes events into your running Claude Code session, so Claude can react to things that happen while you're not at the terminal. Channels can be two-way: Claude reads the event and replies back through the same channel, like a chat bridge. Events only arrive while the session is open, so for an always-on setup you run Claude in a background process or persistent terminal.
+
+Unlike integrations that spawn a fresh cloud session or wait to be polled, the event arrives in the session you already have open: see [how channels compare](#how-channels-compare).
+
+You install a channel as a plugin and configure it with your own credentials. Telegram, Discord, and iMessage are included in the research preview.
+
+When Claude replies through a channel, you see the inbound message in your terminal but not the reply text. The terminal shows the tool call and a confirmation (like "sent"), and the actual reply appears on the other platform.
+
+This page covers:
+
+- [Supported channels](#supported-channels): Telegram, Discord, and iMessage setup
+- [Install and run a channel](#quickstart) with fakechat, a localhost demo
+- [Who can push messages](#security): sender allowlists and how you pair
+- [Enable channels for your organization](#enterprise-controls) on Team and Enterprise
+- [How channels compare](#how-channels-compare) to web sessions, Slack, MCP, and Remote Control
+
+To build your own channel, see the [Channels reference](/en/channels-reference).

package/skills-fallback/cc-cli-reference/SKILL.md

@@ -0,0 +1,16 @@
+---
+name: cc-cli-reference
+description: "Referencia completa CLI de Claude Code: flags, comandos, system prompt flags, opciones de headless."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/cli-reference.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.
+
+# CLI reference
+
+> Complete reference for Claude Code command-line interface, including commands and flags.

package/skills-fallback/cc-commands/SKILL.md

@@ -0,0 +1,12 @@
+---
+name: cc-commands
+description: "Comandos built-in de Claude Code: /batch, /debug, /loop, /simplify, /claude-api, /compact, /memory y más."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/commands.md"
+---
+> ## Documentation Index
+>
+> Fetch the complete documentation index at: https://code.claude.com/docs/llms.txt
+> Use this file to discover all available pages before exploring further.

package/skills-fallback/cc-common-workflows-ask-claude-about-its-capabilities/SKILL.md

@@ -0,0 +1,43 @@
+---
+name: cc-common-workflows-ask-claude-about-its-capabilities
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Ask Claude about its capabilities
+
+Claude has built-in access to its documentation and can answer questions about its own features and limitations.
+
+### Example questions
+
+```text theme={null}
+can Claude Code create pull requests?
+```
+
+```text theme={null}
+how does Claude Code handle permissions?
+```
+
+```text theme={null}
+what skills are available?
+```
+
+```text theme={null}
+how do I use MCP with Claude Code?
+```
+
+```text theme={null}
+how do I configure Claude Code for Amazon Bedrock?
+```
+
+```text theme={null}
+what are the limitations of Claude Code?
+```
+
+- Claude always has access to the latest Claude Code documentation, regardless of the version you're using
+- Ask specific questions to get detailed answers
+- Claude can explain complex features like MCP integration, enterprise configurations, and advanced workflows
+
+***

package/skills-fallback/cc-common-workflows-create-pull-requests/SKILL.md

@@ -0,0 +1,26 @@
+---
+name: cc-common-workflows-create-pull-requests
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Create pull requests
+
+You can create pull requests by asking Claude directly ("create a pr for my changes"), or guide Claude through it step-by-step:
+
+  <Step title="Generate a pull request">
+    ```text  theme={null}
+    create a pr
+    ```
+  </Step>
+
+  <Step title="Review and refine">
+    ```text  theme={null}
+    enhance the PR description with more context about the security improvements
+    ```
+  </Step>
+</Steps>
+
+When you create a PR using `gh pr create`, the session is automatically linked to that PR. You can resume it later with `claude --from-pr <number>`.

package/skills-fallback/cc-common-workflows-fix-bugs-efficiently/SKILL.md

@@ -0,0 +1,30 @@
+---
+name: cc-common-workflows-fix-bugs-efficiently
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Fix bugs efficiently
+
+Suppose you've encountered an error message and need to find and fix its source.
+
+  <Step title="Ask for fix recommendations">
+    ```text  theme={null}
+    suggest a few ways to fix the @ts-ignore in user.ts
+    ```
+  </Step>
+
+  <Step title="Apply the fix">
+    ```text  theme={null}
+    update user.ts to add the null check you suggested
+    ```
+  </Step>
+</Steps>
+
+- Tell Claude the command to reproduce the issue and get a stack trace
+- Mention any steps to reproduce the error
+- Let Claude know if the error is intermittent or consistent
+
+***

package/skills-fallback/cc-common-workflows-get-notified-when-claude-needs-your-attention/SKILL.md

@@ -0,0 +1,95 @@
+---
+name: cc-common-workflows-get-notified-when-claude-needs-your-attention
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Get notified when Claude needs your attention
+
+When you kick off a long-running task and switch to another window, you can set up desktop notifications so you know when Claude finishes or needs your input. This uses the `Notification` [hook event](/en/hooks-guide#get-notified-when-claude-needs-input), which fires whenever Claude is waiting for permission, idle and ready for a new prompt, or completing authentication.
+
+````
+<Tabs>
+  <Tab title="macOS">
+    ```json  theme={null}
+    {
+      "hooks": {
+        "Notification": [
+          {
+            "matcher": "",
+            "hooks": [
+              {
+                "type": "command",
+                "command": "osascript -e 'display notification \"Claude Code needs your attention\" with title \"Claude Code\"'"
+              }
+            ]
+          }
+        ]
+      }
+    }
+    ```
+  </Tab>
+
+  <Tab title="Linux">
+    ```json  theme={null}
+    {
+      "hooks": {
+        "Notification": [
+          {
+            "matcher": "",
+            "hooks": [
+              {
+                "type": "command",
+                "command": "notify-send 'Claude Code' 'Claude Code needs your attention'"
+              }
+            ]
+          }
+        ]
+      }
+    }
+    ```
+  </Tab>
+
+  <Tab title="Windows">
+    ```json  theme={null}
+    {
+      "hooks": {
+        "Notification": [
+          {
+            "matcher": "",
+            "hooks": [
+              {
+                "type": "command",
+                "command": "powershell.exe -Command \"[System.Reflection.Assembly]::LoadWithPartialName('System.Windows.Forms'); [System.Windows.Forms.MessageBox]::Show('Claude Code needs your attention', 'Claude Code')\""
+              }
+            ]
+          }
+        ]
+      }
+    }
+    ```
+  </Tab>
+</Tabs>
+
+If your settings file already has a `hooks` key, merge the `Notification` entry into it rather than overwriting. You can also ask Claude to write the hook for you by describing what you want in the CLI.
+````
+
+  </Step>
+
+  <Step title="Optionally narrow the matcher">
+    By default the hook fires on all notification types. To fire only for specific events, set the `matcher` field to one of these values:
+
+```
+| Matcher              | Fires when                                      |
+| :------------------- | :---------------------------------------------- |
+| `permission_prompt`  | Claude needs you to approve a tool use          |
+| `idle_prompt`        | Claude is done and waiting for your next prompt |
+| `auth_success`       | Authentication completes                        |
+| `elicitation_dialog` | Claude is asking you a question                 |
+```
+
+  </Step>
+
+  <Step title="Verify the hook">

package/skills-fallback/cc-common-workflows-handle-documentation/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: cc-common-workflows-handle-documentation
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Handle documentation
+
+Suppose you need to add or update documentation for your code.
+
+  <Step title="Generate documentation">
+    ```text  theme={null}
+    add JSDoc comments to the undocumented functions in auth.js
+    ```
+  </Step>
+
+  <Step title="Review and enhance">
+    ```text  theme={null}
+    improve the generated documentation with more context and examples
+    ```
+  </Step>
+
+  <Step title="Verify documentation">
+    ```text  theme={null}
+    check if the documentation follows our project standards
+    ```
+  </Step>
+</Steps>
+
+- Specify the documentation style you want (JSDoc, docstrings, etc.)
+- Ask for examples in the documentation
+- Request documentation for public APIs, interfaces, and complex logic
+
+***

package/skills-fallback/cc-common-workflows-next-steps/SKILL.md

@@ -0,0 +1,22 @@
+---
+name: cc-common-workflows-next-steps
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Next steps
+
+  <Card title="How Claude Code works" icon="gear" href="/en/how-claude-code-works">
+    Understand the agentic loop and context management
+  </Card>
+
+  <Card title="Extend Claude Code" icon="puzzle-piece" href="/en/features-overview">
+    Add skills, hooks, MCP, subagents, and plugins
+  </Card>
+
+  <Card title="Reference implementation" icon="code" href="https://github.com/anthropics/claude-code/tree/main/.devcontainer">
+    Clone the development container reference implementation
+  </Card>
+</CardGroup>

package/skills-fallback/cc-common-workflows-refactor-code/SKILL.md

@@ -0,0 +1,36 @@
+---
+name: cc-common-workflows-refactor-code
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Refactor code
+
+Suppose you need to update old code to use modern patterns and practices.
+
+  <Step title="Get refactoring recommendations">
+    ```text  theme={null}
+    suggest how to refactor utils.js to use modern JavaScript features
+    ```
+  </Step>
+
+  <Step title="Apply the changes safely">
+    ```text  theme={null}
+    refactor utils.js to use ES2024 features while maintaining the same behavior
+    ```
+  </Step>
+
+  <Step title="Verify the refactoring">
+    ```text  theme={null}
+    run tests for the refactored code
+    ```
+  </Step>
+</Steps>
+
+- Ask Claude to explain the benefits of the modern approach
+- Request that changes maintain backward compatibility when needed
+- Do refactoring in small, testable increments
+
+***

package/skills-fallback/cc-common-workflows-reference-files-and-directories/SKILL.md

@@ -0,0 +1,47 @@
+---
+name: cc-common-workflows-reference-files-and-directories
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Reference files and directories
+
+Use @ to quickly include files or directories without waiting for Claude to read them.
+
+```
+This includes the full content of the file in the conversation.
+```
+
+  </Step>
+
+  <Step title="Reference a directory">
+    ```text  theme={null}
+    What's the structure of @src/components?
+    ```
+
+```
+This provides a directory listing with file information.
+```
+
+  </Step>
+
+  <Step title="Reference MCP resources">
+    ```text  theme={null}
+    Show me the data from @github:repos/owner/repo/issues
+    ```
+
+```
+This fetches data from connected MCP servers using the format @server:resource. See [MCP resources](/en/mcp#use-mcp-resources) for details.
+```
+
+  </Step>
+</Steps>
+
+- File paths can be relative or absolute
+- @ file references add `CLAUDE.md` in the file's directory and parent directories to context
+- Directory references show file listings, not contents
+- You can reference multiple files in a single message (for example, "@file1.js and @file2.js")
+
+***

package/skills-fallback/cc-common-workflows-resume-previous-conversations/SKILL.md

@@ -0,0 +1,57 @@
+---
+name: cc-common-workflows-resume-previous-conversations
+description: "Flujos de trabajo comunes en Claude Code: worktrees paralelos, git workflows, plan mode, extended thinking, pipe input/output."
+invocation: auto
+_pulse: true
+_syncedAt: "2026-04-07T04:44:06.766Z"
+_source: "https://code.claude.com/docs/en/common-workflows.md"
+---
+## Resume previous conversations
+
+When starting Claude Code, you can resume a previous session:
+
+- `claude --continue` continues the most recent conversation in the current directory
+- `claude --resume` opens a conversation picker or resumes by name
+- `claude --from-pr 123` resumes sessions linked to a specific pull request
+
+From inside an active session, use `/resume` to switch to a different conversation.
+
+Sessions are stored per project directory. The `/resume` picker shows interactive sessions from the same git repository, including worktrees. Sessions created by `claude -p` or SDK invocations do not appear in the picker, but you can still resume one by passing its session ID directly to `claude --resume <session-id>`.
+
+### Name your sessions
+
+Give sessions descriptive names to find them later. This is a best practice when working on multiple tasks or features.
+
+````
+```bash  theme={null}
+claude -n auth-refactor
+```
+
+Or use `/rename` during a session, which also shows the name on the prompt bar:
+
+```text  theme={null}
+/rename auth-refactor
+```
+
+You can also rename any session from the picker: run `/resume`, navigate to a session, and press `R`.
+````
+
+  </Step>
+
+  <Step title="Resume by name later">
+    From the command line:
+
+````
+```bash  theme={null}
+claude --resume auth-refactor
+```
+
+Or from inside an active session:
+
+```text  theme={null}
+/resume auth-refactor
+```
+````
+
+  </Step>
+</Steps>