nostrstack-api
Nostrstack API development (Fastify + Prisma) including routing patterns, services, tenancy resolution, LightningProvider integration, and Nostr endpoints. Use when editing apps/api (routes, services, providers, Prisma schema, OpenAPI) or adding API features/tests.
When & Why to Use This Skill
The Nostrstack API skill streamlines the development and maintenance of backend services built with Fastify and Prisma. It specializes in implementing complex routing patterns, multi-tenancy resolution, and seamless integration with the Nostr protocol and Lightning Network for payments. By enforcing architectural guardrails and automating OpenAPI documentation, it ensures high-quality, scalable API development for decentralized applications.
Use Cases
- Developing and testing new Nostr protocol endpoints, including specialized event handling and ID parsing.
- Configuring multi-tenant architecture through tenant-resolver logic and host/domain-based routing rules.
- Integrating Lightning Network payment providers while maintaining robust webhook processing and retry behaviors.
- Managing database schema evolution using Prisma migrations and ensuring seed data remains aligned with API changes.
- Automating the update of OpenAPI specifications and technical documentation when route shapes or responses change.
| name | nostrstack-api |
|---|---|
| description | Nostrstack API development (Fastify + Prisma) including routing patterns, services, tenancy resolution, LightningProvider integration, and Nostr endpoints. Use when editing apps/api (routes, services, providers, Prisma schema, OpenAPI) or adding API features/tests. |
Nostrstack API
Use this skill when working inside apps/api.
Workflow
- Read
references/architecture.mdfor system context and data flow. - Consult
references/api-structure.mdfor code layout and key files. - For Nostr endpoints or ID parsing, also read
references/nostr.md. - Update or add tests per
references/testing.md.
Guardrails
- Keep tenant resolution consistent (
tenant-resolver.tsand host/domain rules). - Lightning provider changes must preserve webhook/payment flow and retry behavior.
- Ensure Prisma migrations and seeds stay aligned with schema changes.
When to add docs
- If routes or response shapes change, update
apps/api/openapi.jsonand relevant docs.