stella

Drive the stella command-line client (@stll/cli), a legal-workspace CLI whose command surface is generated from the stella MCP tool registry. Covers install, OAuth login, the full command tree grouped by domain, JSON output for scripting, the --input escape hatch for deep payloads, cursor pagination, destructive-op confirmation, and exit codes.

Apply when writing or reviewing React effects in apps/web. Direct useEffect is banned; use the sanctioned wrappers or a better primitive.

Apply when writing or modifying database schema, queries, or migrations.

Apply when a performance-guard check (network baseline, bundle baseline, DB query count, loader-prefetch lint, RC bailouts) fails or when touching a hot route/endpoint.

Internationalization conventions for Stella. Apply when adding or modifying user-facing strings.

Apply when building or modifying user-facing UI components.

Review and update third-party dependencies. Use this when asked to upgrade packages, survey new minor or major releases for useful features, assess whether Stella can adopt them, or validate whether a release looks suspicious before bumping it.

Answers data-protection (GDPR) questions grounded in the regulation and supervisory guidance, with a citation for every claim. Use for questions about personal data, consent, or data-subject rights.

Rewrite this description — it is the trigger the assistant uses to decide when to run this skill.

Reviews a non-disclosure agreement against the firm's NDA checklist and reports findings with citations. Use when the user attaches an NDA and asks to check or review it.

Collects the facts of an unpaid invoice, then drafts a payment demand letter. Use when the user asks to draft a demand letter or a payment reminder.

Track down a behavior that used to work and now fails, changed, or regressed. Use this when a bug report points to a recent breakage, especially when the cause is not obvious yet.

Apply when writing code that touches auth, data access, file handling, or external APIs. Stella handles privileged legal data (attorney-client privilege, litigation holds, personal data).

Apply when making architectural decisions, designing new endpoints, or adding database tables.

Prepare the current worktree branch for a pull request: rebase, self-review, quality checks, and open a draft PR.

Process automated PR review comments systematically in one pass for CodeRabbit, Google Code Assist (Gemini), GitHub Copilot, Devin, and similar review bots.

Scan the Stella codebase for security issues. We handle sensitive legal documents — security is non-negotiable.

Launch the local dev environment using the project's dev-runner. The runner handles env symlinks, Docker services, port allocation, health checks, and browser opening automatically.

Autonomous browser-based QA and UX smoke test. Starts the dev server, takes control of Chrome, walks through user stories for a feature area, monitors the console, and produces a structured report on what works, what breaks, and what feels wrong.

Apply when writing or reviewing tests.

Scaffold a new Elysia API handler following Stella's conventions.

Create a new plan file in `.agents/plans/` for a feature or task.

Assess a feature idea through a product lens before writing any plan or code. This is a conversational exercise: no code changes, no files produced. The output is clarity on whether and how to build something.

Shape a feature or problem before implementation. Use this when the request is still fuzzy, when several solutions are possible, or when execution risks outrunning product clarity.