feat(LLMsDocs.Cli): default skill installation to user scope

[ArgoZhang]

Link issues

fixes #1115

Summary By Copilot

• default bb-llms install to the user scope for globally discoverable client artifacts
• retain explicit --scope project support for repository-local installation
• update CLI help and README examples for Claude Code, Cursor, Trae, and Codex

Regression?

• Yes
• No

Risk

• High
• Medium
• Low

The change only adjusts the default installation target; callers can retain the previous behavior with --scope project.

Verification

• Manual (required)
• Automated

Packaging changes reviewed?

• Yes
• No
• N/A

☑️ Self Check before Merge

⚠️ Please check all items below before review. ⚠️

• Doc is updated/provided or not needed
• Demo is updated/provided or not needed
• Merge the latest code from the main branch

Summary by Sourcery

Make user scope the default for installed LLM client discovery artifacts while preserving project-scope installation as an explicit option.

New Features:

• Default bb-llms install to user-scoped discovery artifacts so globally installed client integrations work across projects.
• Retain explicit project-scoped installation through --scope project.

Enhancements:

• Update CLI help and usage documentation to reflect user-scope installation and describe client-specific global discovery behavior.

Documentation:

• Revise README examples and guidance for Claude Code, Cursor, Trae, and Codex user- and project-scope installations.

[sourcery-ai]

Reviewer's Guide

The CLI now installs discovery artifacts to user-level locations by default, aligning with global tool installation and enabling discovery across projects, while retaining --scope project for repository-local use; help text and client-specific documentation were updated accordingly.

Flow diagram for default user-scope installation

flowchart TD
    A[bb_llms install] --> B{--scope provided?}
    B -->|No| C[scope = user]
    B -->|--scope project| D[scope = project]
    C --> E[Install discovery artifacts in user home]
    D --> F[Install discovery artifacts in current project]
    E --> G[Clients discover artifacts across projects]
    F --> H[Artifacts apply to one repository]

Loading

File-Level Changes

Change	Details	Files
Changed installation to default to the user scope while preserving explicit project-scoped installation.	Made the CLI pass an omitted scope through to the scaffolder instead of defaulting to project. Defaulted missing scope values to user and retained validation for user/project options. Updated CLI help text to describe user scope as the default.	tools/BootstrapBlazor.LLMsDocs.Cli/CommandFactory.cs tools/BootstrapBlazor.LLMsDocs.Cli/Scaffolder.cs
Updated documentation and examples to reflect globally discoverable user-scoped artifacts.	Changed client examples to show files under user home directories. Documented --scope project as the opt-in repository-local behavior. Clarified default paths and global-installation workflow for Claude Code, Cursor, Trae, and Codex.	tools/BootstrapBlazor.LLMsDocs.Cli/README.md

Assessment against linked issues

Issue	Objective	Addressed	Explanation
#1115	Default bb-llms install to the user scope so discovery artifacts are installed in user-level client directories and work across projects.	✅
#1115	Preserve explicit --scope project support for repository-specific installation.	✅
#1115	Update CLI help and README examples and documentation to reflect the user-scope default and project-scope override.	✅

Possibly linked issues

• feat(LLMsDocs.Cli): default skill installation to user scope #1115: The PR directly implements the issue’s requested default scope, project override, and documentation updates.

---

Tips and commands

Interacting with Sourcery

• Trigger a new review: Comment @sourcery-ai review on the pull request.
• Continue discussions: Reply directly to Sourcery's review comments.
• Generate a GitHub issue from a review comment: Ask Sourcery to create an
  issue from a review comment by replying to it. You can also reply to a
  review comment with @sourcery-ai issue to create an issue from it.
• Generate a pull request title: Write @sourcery-ai anywhere in the pull
  request title to generate a title at any time. You can also comment
  @sourcery-ai title on the pull request to (re-)generate the title at any time.
• Generate a pull request summary: Write @sourcery-ai summary anywhere in
  the pull request body to generate a PR summary at any time exactly where you
  want it. You can also comment @sourcery-ai summary on the pull request to
  (re-)generate the summary at any time.
• Generate reviewer's guide: Comment @sourcery-ai guide on the pull
  request to (re-)generate the reviewer's guide at any time.
• Resolve all Sourcery comments: Comment @sourcery-ai resolve on the
  pull request to resolve all Sourcery comments. Useful if you've already
  addressed all the comments and don't want to see them anymore.
• Dismiss all Sourcery reviews: Comment @sourcery-ai dismiss on the pull
  request to dismiss all existing Sourcery reviews. Especially useful if you
  want to start fresh with a new review - don't forget to comment
  @sourcery-ai review to trigger a new review!

Customizing Your Experience

Access your dashboard to:

• Enable or disable review features such as the Sourcery-generated pull request
  summary, the reviewer's guide, and others.
• Change the review language.
• Add, remove or edit custom review instructions.
• Adjust other review settings.

Getting Help

• Contact our support team for questions or feedback.
• Visit our documentation for detailed guides and information.
• Keep in touch with the Sourcery team by following us on X/Twitter, LinkedIn or GitHub.

[bb-auto]

Auto approved by bb-auto

[sourcery-ai]

Hey - I've reviewed your changes and they look great!

---

Sourcery is free for open source - if you like our reviews please consider sharing them ✨

• X
• Mastodon
• LinkedIn
• Facebook

_{Help me be more useful! Please click 👍 or 👎 on each comment and I'll use the feedback to improve your reviews.}

[bb-auto]

Auto approved by bb-auto