Vibeflow Teach.prompt

---
name: 'vibeflow-teach'
description: 'Updates .vibeflow/ with corrections, new conventions, decisions, or patterns. Also imports from external repos via --from.'
agent: 'vibeflow-architect'
---

# Vibeflow: Teach

> format-agnostic, repo-local prompt asset

Teach the project knowledge base. Update `.vibeflow/` docs with
corrections, new conventions, decisions, or patterns based on
natural language feedback. Also imports patterns from external
reference repos via `--from <url|path>`.

**Usage:** Provide your feedback as input, or use `--from <url|path>` to import from an external repo.

---

## Language

Detect the language of the user's input.
Write ALL output in that same language.
Technical terms in English are acceptable regardless of the detected language.

## Before Starting

1. Check if `.vibeflow/` exists.
   - **YES** → read `.vibeflow/index.md` for orientation.
   - **NO** → warn: "`.vibeflow/` does not exist. Run the vibeflow-analyze
     prompt first to create the knowledge base." and STOP.

2. **Check for `--from` flag.**
   If input contains `--from`, go to **## Import from external repo**.
   Otherwise, continue to **## Classify the Feedback**.

---

## Import from external repo

This flow imports patterns and conventions from an external reference repo
(e.g., shared architecture docs, coding guidelines).

### Step 1: Parse arguments

- Extract the `<url|path>` after `--from`.
- If `--name <alias>` is present, use `<alias>` as the repo name.
- Otherwise, auto-detect the name:
  - URL: use the last path segment without `.git` (e.g., `https://github.com/org/platform-patterns.git` → `platform-patterns`)
  - Local path: use the directory name (e.g., `./my-patterns` → `my-patterns`)

### Step 2: Get the repo

- **URL (contains `://` or starts with `git@`):**
  1. Clone to a temp directory: `git clone --depth 1 <url> $TMPDIR/vibeflow-teach-$(date +%s)`
  2. Set `$REPO_PATH` to the clone directory.
  3. Mark for cleanup at the end.

- **Local path:**
  1. Verify the path exists and is a directory.
  2. Set `$REPO_PATH` to the resolved absolute path.
  3. No cleanup needed.

### Step 3: Detect knowledge sources

Scan `$REPO_PATH` for these knowledge sources (in order):

| Source | Glob pattern |
|--------|-------------|
| Claude Code skills | `.claude/skills/*/SKILL.md` |
| CLAUDE.md | `CLAUDE.md` |
| Knowledge docs | `knowledge/**/*.md` |
| Documentation | `docs/**/*.md` |
| Cursor rules | `.cursorrules` |
| Cursor rule files | `.cursor/rules/*.mdc` |
| AGENTS.md | `AGENTS.md` |

For each source found:
1. Read the file.
2. Extract a **title** (first `#` heading, or filename if no heading).
3. Extract a **summary** (first 3-5 lines of meaningful content, or the
   `description` from YAML frontmatter if present).
4. Classify as `pattern` or `convention` based on content:
   - If it describes architecture, module structure, code organization → `pattern`
   - If it describes coding rules, naming, formatting, process → `convention`

If NO sources are found: report "No knowledge sources found in `<repo>`."
and STOP (after cleanup if cloned).

### Step 4: Interactive review

Present the findings to the user: