Init skills

[kindermax]

Summary by Sourcery

Define and document agent skills, domain context, and issue workflows for the repo while updating UI-related dependencies.

New Features:

• Add a root CONTEXT.md to formalize domain vocabulary, execution flow, and configuration relationships for the lets CLI.
• Introduce a UBIQUITOUS_LANGUAGE.md glossary capturing stable terminology for configuration, issues, documentation layout, and roles.
• Add agent-facing documentation describing domain docs, GitHub-based issue tracking, and triage label conventions for skills.

Enhancements:

• Document agent skills usage in AGENTS.md and clarify how they relate to repo context and ADRs.
• Update Go module dependencies for lipgloss and runewidth and add new indirect UI-related libraries.

[sourcery-ai]

Reviewer's Guide

Defines initial agent skills and domain language docs for the repo, wiring them into AGENTS.md, and bumps a few Charm ecosystem dependencies to newer patch/minor versions.

Entity relationship diagram for GitHub issues and triage labels

erDiagram
  GITHUB_ISSUE ||--o{ TRIAGE_LABEL : has_label
  GITHUB_ISSUE {
    int number
    string title
  }
  TRIAGE_LABEL {
    string name
    string canonical_role
  }

Loading

Flow diagram for agent skills using domain docs and issue tracker

flowchart TD
  AgentSkill[Agent skill] --> Context[CONTEXT.md]
  AgentSkill --> ADRs[docs/adr/]
  AgentSkill --> AgentDocs[docs/agents/*]
  AgentSkill --> IssueTracker[GitHub issue tracker]
  IssueTracker --> GitHubIssues[GitHub Issues in lets-cli/lets]
  GitHubIssues --> TriageLabels[Triage labels needs-triage, needs-info, ready-for-agent, ready-for-human, wontfix]

Loading

File-Level Changes

Change	Details	Files
Document initial agent skills context and how agents should use issue tracker, triage labels, and domain docs.	Add an Agent skills section to the agent guide describing issue tracker, triage labels, and domain docs expectations. Introduce a root Context document defining the project’s domain vocabulary, configuration/command/execution model, and precedence rules. Add a ubiquitous language log to capture stable terminology and ambiguities across configuration, workflow, docs, and people roles.	AGENTS.md CONTEXT.md UBIQUITOUS_LANGUAGE.md
Define agent-facing domain, issue-tracker, and triage-label behavior docs under docs/agents.	Add domain docs guidance telling skills to use CONTEXT.md and root ADRs as the single source of truth and how to behave if they’re missing. Add an issue-tracker guide standardizing on GitHub Issues and the gh CLI, with canonical commands for common operations. Add a triage-labels guide mapping canonical triage roles to exact GitHub label strings used in this repo.	docs/agents/domain.md docs/agents/issue-tracker.md docs/agents/triage-labels.md
Update Charm-related Go module dependencies to newer versions.	Bump charm.land/lipgloss/v2 to v2.0.2 and github.com/mattn/go-runewidth to v0.0.21. Add new indirect dependencies for charm.land/bubbles/v2, charm.land/bubbletea/v2, and github.com/charmbracelet/harmonica. Refresh go.sum to match the updated module graph.	go.mod go.sum

---

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.

[sourcery-ai]

Hey - I've found 1 issue, and left some high level feedback:

• There’s quite a bit of overlap between CONTEXT.md and UBIQUITOUS_LANGUAGE.md; consider making one the single source of truth (with links or brief summaries in the other) to reduce the risk of terminology drifting out of sync over time.

Prompt for AI Agents

Please address the comments from this code review:

## Overall Comments
- There’s quite a bit of overlap between `CONTEXT.md` and `UBIQUITOUS_LANGUAGE.md`; consider making one the single source of truth (with links or brief summaries in the other) to reduce the risk of terminology drifting out of sync over time.

## Individual Comments

### Comment 1
<location path="UBIQUITOUS_LANGUAGE.md" line_range="10" />
<code_context>
+| **Settings** | Per-user lets behavior stored in `~/.config/lets/config.yaml`. | Config, `lets.yaml`, project config |
+| **Project config** | Repository command and runtime configuration stored in `lets.yaml`. | Settings, user config |
+| **Theme** | A named visual style for lets help and styled error output. | Color scheme, palette |
+| **Default theme** | The standard lets theme. | Normal theme, builtin colors |
+| **ANSI theme** | A theme limited to broadly supported ANSI terminal colors. | Plain theme, basic colors |
+| **Synthwave theme** | A high-contrast neon lets theme. | Vaporwave, purple theme |
</code_context>
<issue_to_address>
**suggestion (typo):** Consider hyphenating “builtin” to “built-in” for clarity.

In the **Default theme** aliases, please change “builtin colors” to “built-in colors” to avoid it looking like a typo and to match common usage.

```suggestion
| **Default theme** | The standard lets theme. | Normal theme, built-in colors |
```
</issue_to_address>

---

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.}

[sourcery-ai]

suggestion (typo): Consider hyphenating “builtin” to “built-in” for clarity.

In the Default theme aliases, please change “builtin colors” to “built-in colors” to avoid it looking like a typo and to match common usage.

Suggested change

	| **Default theme** | The standard lets theme. | Normal theme, builtin colors |
	| **Default theme** | The standard lets theme. | Normal theme, built-in colors |