azents

Ship a large, multi-phase feature after Requirements and design discussion are complete. Convert the approved Requirements, ADR, and design into an implementation plan and stacked PRs for phased delivery. Use when: (1) a large feature design is complete and the user says to implement, (2) the user invokes 'ship-feature' for phased delivery, (3) a design document requires multiple implementation phases. Use one focused PR instead for simple fixes and small, self-contained changes.

Requirements-first workflow for new feature design, design documents, and architecture changes. Use for collaborative or autonomous design: interview the user to confirm high-level requirements, preserve an immutable requirements snapshot, use reusable research subagents without blocking the conversation, record design decisions in an ADR, validate repository feasibility, and produce an implementable final design.

Add a path-scoped coding convention to .claude/conventions/. Trigger phrases include "add a rule for X", "we should always do Y", "let's enforce Z", "document our convention for W", "make agents aware that ...", "ban this pattern", or any request to make future agent edits respect a new project-wide invariant. NOT for one-off code comments, workflow how-tos, or domain explanations — those go elsewhere.

Perform code review. Use for: (1) '/code-review' to review the current branch changes, (2) '/code-review PR #123' to review a specific PR, (3) '/code-review staged' to review staged changes, (4) requests such as 'review this code' or 'please review'.

Create and discuss trustworthy UI visual variants from the product's real components. Use when comparing UI options, reviewing visual polish, reproducing a screenshot, choosing spacing/typography/radius/layout alternatives, or presenting responsive desktop/mobile states as rendered images before implementation.

Create a GitHub PR from the current branch. Proactively use when: (1) '/create-pr', (2) requests such as 'create a PR', 'open a PR', 'submit a PR', (3) opening an already prepared branch as a PR. Focus only on PR creation; do not run code review or spec review.

Use when writing multiline Markdown bodies for GitHub PR descriptions, issue comments, review comments, or discussion comments with the `gh` CLI. Use for: (1) long PR descriptions, (2) issue comments, (3) review bodies, (4) cases where raw `\n` appears or escaping breaks.

Guide for adding dependencies to Python projects. Uses the uv package manager, and version specifier rules differ by project type (apps/libs).

Update dependencies in Python projects. Use for Dependabot security alerts, package upgrades, and transitive dependency updates. Use when: (1) resolving Dependabot security alerts, (2) updating a specific package, (3) patching a security vulnerability.

Run the PR shipping flow. Use for: (1) '/ship-pr', (2) requests such as 'create a PR and monitor it'. PR creation itself is delegated to /create-pr.

Check whether a code diff requires updates to docs/azents/spec/**/*.md. Use for: '/spec-review', '/spec-review staged', '/spec-review last', '/spec-review PR #N', or requests such as 'check spec impact'.

Manage stacked PRs: rebase, merge, and retarget sequential PR branches. Use when: (1) the user asks to merge a stacked PR or stack, (2) later stack branches must be rebased after an earlier branch changes, (3) the user asks to inspect stacked PR status.

Database debugging tool for the azents project. Run non-interactive queries with shell.py -c to inspect database state. Use when: (1) inspecting/debugging azents database data, (2) checking runtime data such as events, sessions, and channels, or (3) the user asks to check the DB, inspect events, run a query, or look into the database.

Inspect Dependabot alerts for the Azents repository and summarize actionable vulnerabilities.

Debug Azents E2E tests, fixtures, browser state, and local integration failures.

Frontend UX and visual design guidance for building polished product surfaces, dashboards, admin tools, workflows, and local web apps. Use when designing or reviewing UI layout, interaction flow, information hierarchy, utility copy, responsive behavior, or visual quality before implementing frontend code.

Regenerate Azents API clients from OpenAPI specifications. Use when API routes are added or modified, or when the user asks to regenerate clients, update OpenAPI spec, or sync API changes.

Run Python code quality tools (ruff, pyright, pytest) for an Azents Python subproject. Use when the user asks to check code quality, run linting, type checking, or tests for Python code.

Guide for creating effective skills. This skill should be used when users want to create a new skill (or update an existing skill) that extends Claude's capabilities with specialized knowledge, workflows, or tool integrations.

Update dependencies in the Azents TypeScript workspace.

Run TypeScript format, lint, typecheck, and build checks for Azents TypeScript workspaces.

Create Alembic database migrations for azents. Use when the user asks to create a migration, add/modify database columns, create tables, or make schema changes.