All authors
Claude Skills by Nano-Core
github.com/Nano-Core58 skills0 installs8 views
- Nano Add Eventing ProviderAdd a Nano eventing provider (currently only RabbitMq) to a Nano.Library-based application - registers it in Program.cs, adds the Eventing configuration section, the local docker-compose broker service, and the Kubernetes secret reference for Staging/Production. Use when the user asks to add eventing, pub/sub messaging, or a message broker to a Nano API, Web, or Console application.Votes: 0GitHub stars: 5
- Nano Add IdentityConfigure Nano's persistent Identity store (Data:Identity) on a Nano.Library-based application that already has a Data provider - adds the Identity configuration section and the User entity/mapping/controller triplet Nano's identity actions attach to. Use when the user asks to add user accounts, a user store, sign-up, or persistent identity to a Nano API, Web, or Console application - not when they ask for login/JWT/authentication itself, that's a separate concern.Votes: 0GitHub stars: 5
- Nano Add Public ExposureExpose a Nano API or Web application publicly - adds HTTPS hosting config, Kubernetes HTTPRoute (Gateway API) resources for ports 80/443, and the CI step that derives the app's public hostname from every configured Azure DNS zone. Use when the user asks to expose a Nano application publicly, add HTTPS/a public domain, or add an HTTPRoute to a Nano API or Web application.Votes: 0GitHub stars: 5
- Nano Add Storage ProviderAdd a Nano storage provider (Local or Azure) to a Nano.Library-based application - registers it in Program.cs, adds the Storage configuration section, the local docker-compose volume mount, and the Kubernetes persistent volume (plus, for Azure, the Staging/Production fileshare-provisioning CI step). Use when the user asks to add file storage, a fileshare, or a specific storage provider to a Nano API, Web, or Console application.Votes: 0GitHub stars: 5
- Nano Remove Api Client ConfigurationStop consuming a Nano Api Client from this application - removes the App:Apis configuration entry and the client's injection site, without touching the client's definition in the owning service. Use when the user asks to remove a call to another Nano service/API, stop consuming an internal service, or drop an API client from this app's Public API composition in a Nano API, Web, or Console application.Votes: 0GitHub stars: 5
- Nano Remove Custom EndpointRemove a custom, non-CRUD HTTP endpoint - two genuinely different shapes depending on the controller. A Public API endpoint's removal is just the controller action, its DTOs, and possibly a now-unused Api Client injection. An internal-service endpoint's removal is the controller action plus the paired Api Client custom request/method that called it, removed together since they're one contract. Use when the user asks to remove, delete, or drop a one-off custom action/endpoint from a Nano API o...Votes: 0GitHub stars: 5
- Nano Remove Data ProviderRemove a Nano data provider (MySql, PostgreSQL, SqlServer, SqLite, or InMemory) from a Nano.Library-based application - unregisters it in Program.cs and removes the DbContext/DbContextFactory, Data configuration, docker-compose database service, and (for MySql/PostgreSQL/SqlServer) the Staging/Production migration CI step and Kubernetes secret, or (for SqLite) the persistent volume. Use when the user asks to remove a database, drop persistence, or strip a data provider out of a Nano API, Web,...Votes: 0GitHub stars: 5
- Nano Remove EntityRemove a Nano.Library entity end-to-end - data model, EF Core mapping, query criteria, and CRUD controller - following Nano framework conventions. Use when the user asks to remove, delete, or drop a specific entity/resource from a Nano-based application, as a standalone request (not as a side effect of removing a whole Data provider or Identity - see nano-remove-data-provider/nano-remove-identity for those).Votes: 0GitHub stars: 5