Stats
Actions
Tags
From project-lens
Initialize project-lens on a new or existing project. Scans all code files with a cheap OpenRouter LLM and generates per-feature documentation in .lens/. Run this once when starting work on any project.
How this skill is triggered — by the user, by Claude, or both
Slash command
/project-lens:initThe summary Claude sees in its skill listing — used to decide when to auto-load this skill
Run the full project scan and generate `.lens/` documentation.
Run the full project scan and generate .lens/ documentation.
$CWD)CLAUDE_PLUGIN_OPTION_openrouter_key is set — if not, tell the user:
Run: claude plugin config project-lens openrouter_key YOUR_KEY
bash ${CLAUDE_PLUGIN_ROOT}/scripts/init.sh <project_root>
$PROJECT_ROOT/.lens/overview.md and summarize what was found for the user.lens/features/.lens/ to .gitignore?" — if yes, append it.lens/
overview.md ← project architecture summary
index.md ← file → feature mapping
features/
<feature>.md ← one doc per detected feature
Tell the user: "From now on, every time you ask me to edit a file, I will automatically receive the full file content and its feature doc before touching anything. No more skipping."
npx claudepluginhub 0serenvale/project-lens --plugin project-lensBootstraps or updates projects for Claude Code — generates CLAUDE.md with progressive disclosure docs, installs auto-format hooks, sets up test infrastructure, audits existing docs against source code. Supports single projects, monorepos, and multi-repo workspaces.
Scans codebase to auto-generate CLAUDE.md project config and .rune/ state files for full context in AI coding sessions. Use on new repos or missing/stale context.
Analyzes unfamiliar codebases to generate structured onboarding guides with architecture maps, key entry points, conventions, and starter CLAUDE.md.