Capabilities
A capability is the category of development setup you want to add. An integration is the specific implementation Avis can install and configure.
Current built-in capabilities:
| Capability ID | Name | Description |
|---|---|---|
state-management |
State Management | Client-side application state. |
data-fetching |
Data Fetching | Client-side server-state and API fetching. |
api |
API | API framework extensions and tooling. |
forms |
Forms | Form state and submission helpers. |
validation |
Validation | Runtime schema validation. |
auth |
Authentication | Authentication and API access control. |
observability |
Observability | Logging, tracing, and error visibility. |
icons |
Icons | Icon libraries and icon systems for application interfaces. |
Example:
avis add state-managementPrefer capability-first commands when you know the purpose but not the specific tool:
avis add iconsavis add apiavis add authavis add observabilityIf exactly one compatible integration exists for the detected project and capability, Avis selects it. If multiple compatible integrations exist, Avis recommends one, explains why, and shows alternatives. Exact integration commands still work when you already know the concrete tool:
avis add lucide-reactRecommendation order is framework-specific first, then project-type-specific, then ecosystem-specific. Avis can also mark a capability as native to a framework, such as FastAPI’s built-in OpenAPI documentation, instead of pretending there is a package to install.
Generated capability and integration metadata is available in Generated Registry.