vibe.analyzelisted

# /vibe.analyze Analyze any target: source code, documents, websites, or Figma designs. ## Usage ``` /vibe.analyze # Full project quality analysis /vibe.analyze "login" # Feature/module code exploration + context collection /vibe.analyze --code # Code quality analysis only /vibe.analyze --deps # Dependency analysis only /vibe.analyze --arch # Architecture analysis only /vibe.analyze report.pdf # Document analysis (PDF, markdown, slides) /vibe.analyze https://example.com # Website analysis (UX, tech, SEO, accessibility) /vibe.analyze https://figma.com/design/... # Figma design analysis ``` ## Input Type Auto-Detection Determine analysis mode from the argument pattern: | Pattern | Mode | Description | |---------|------|-------------| | `*.pdf`, `*.docx`, `*.pptx`, `*.md` (file path) | **Document** | Structure, content, quality, applicability | | `http(s)://figma.com/*` | **Figma** | Design structure, components, tokens | | `http(s)://*` | **Website** | UX, tech stack, SEO, accessibility | | `--code`, `--deps`, `--arch` | **Project Quality** | Code quality, dependencies, architecture | | String (feature name) | **Feature/Module** | Source code exploration + flow analysis | | No argument | **Project Quality** | Full project analysis | **Detection order**: file extension → URL pattern → flag → string. ## File Reading Policy (Mandatory) - **SPEC/Feature files**: Always use the harness's full-file reading capab