lens-setup

Installs and configures the Lens module by writing project config files and migrating legacy settings.

Updated Apr 7, 2026
One-click install
npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-setup-crisweber2600
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: lens-setup
Source: https://github.com/crisweber2600/Lens.Core.Src/tree/main/_bmad/lens-work/skills/lens-setup
Command: npx skills add https://github.com/crisweber2600/Lens.Core.Src --skill lens-setup-crisweber2600

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires pyyaml, and includes scripts (resource) and assets (resource) components.

What problem does it solve? Setting up the Lens module requires writing consistent configuration across multiple files, migrating legacy per-module configs, and cleaning up installer directories. This Skill automates that entire setup flow so the module is configured correctly on the first run. ## Core Features & Use Cases - Guided Configuration: Collects user preferences (name, language, output paths) with defaults from module.yaml and writes them to config.yaml and config.user.yaml. - Legacy Migration: Detects old per-module config files, uses their values as fallback defaults, and deletes them after a successful merge. - Safe Cleanup: Verifies skills are installed at .claude/skills/ before removing legacy installer directories, with idempotent behavior on re-runs. - Use Case: After installing the Lens module package, run this Skill to consolidate scattered installer config into the shared _bmad/config.yaml format and clean up leftover directories. ## Quick Start Set up the Lens module in this project using the default configuration values.

Frequently Asked Questions about lens-setup

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I install and configure the Lens module in a project?▼

Run the lens-setup skill, which reads module.yaml for defaults, prompts for preferences like user name and language, then writes config.yaml, config.user.yaml, and module-help.csv under the _bmad directory.

How does Lens setup handle existing legacy config files?▼

The merge scripts read legacy per-module config.yaml files as fallback defaults, merge them with new answers, then delete the legacy files. Matching keys are carried forward while removed keys are ignored.

Can I run Lens setup non-interactively with default values?▼

Yes, pass arguments like 'accept all defaults' or inline values such as a user name and language. The skill maps provided values to config keys, uses defaults for the rest, and skips interactive prompting.

Is it safe to delete legacy installer directories after setup?▼

The cleanup script verifies every skill in the legacy directories exists at .claude/skills/ before removing anything. Missing directories from prior runs are not errors, making the operation idempotent.

What is the difference between config.yaml and config.user.yaml?▼

config.yaml holds shared project settings like output_folder and module values, while config.user.yaml stores personal settings like user_name and communication_language that are intended to be gitignored.