stella

Apply when writing or reviewing tests.

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…

Apply when building or modifying user-facing UI components.

Apply when writing or modifying database schema, queries, migrations, transactions, or tenant-scoped persistence.

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

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.

Inventory, assess, update, and validate third-party dependencies across Bun, Python/uv, Cargo, Docker, and GitHub Actions without hiding ecosystem or supply-chain risk.

Apply when making architectural decisions, designing endpoints or workers, adding database tables, or changing data-volume behavior.

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

Integrate and use @stll/folio-agents, the framework-neutral LLM tool layer over @stll/folio-core: function-calling tools that read and mutate a .docx document, with every mutation landing as a tracked change or comment pending human review. Load this skill…

Create a new implementation plan in the repo's planning area.

Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.

Run a security-focused code audit with a generic checklist first, then layer on repo-specific risks.

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

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

Create a new implementation plan in the repo's planning area.

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.

Process automated PR review comments systematically. Use this for CodeRabbit, Gemini, GitHub Copilot, Devin, Greptile, and similar bots.

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.

Run a security-focused code audit with a generic checklist first, then layer on repo-specific risks.

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.

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

Run SkillGuard before installing third-party Agent Skills, with optional semantic review only when the user explicitly allows network/model use.

Audit a repository, path, or Git diff for security defects using threat modeling, evidence-backed validation, attack-path analysis, and explicit coverage. Use for security reviews; keep audits read-only unless remediation is explicitly requested.