XynPOS API design and documentation — use when designing new REST endpoints, reviewing existing API design, writing Swagger/OpenAPI annotations, planning webhook events, or ensuring API consistency with XynPOS standards. Triggers when someone needs to add a new endpoint, design a resource URL structure, determine correct HTTP method or status code, document an API with Swagger, or review an API for RESTful compliance. Also triggers for questions about API versioning, idempotency, pagination strategy, or rate limiting design.
XynPOS code review assistant — use when reviewing Go, Flutter, or Next.js code for quality, security, architecture compliance, and XynPOS conventions. Triggers when a developer asks to review their code, check a PR, evaluate a code snippet for XynPOS compliance, get feedback on implementation quality, or understand whether their code follows XynPOS patterns. Runs automated checks via scripts and provides structured BLOCKER vs SUGGESTION feedback with specific fix recommendations.
XynPOS master project context — loads essential architecture, stack, conventions, and service map for the XynPOS POS SaaS application by Extended Synaptic. Use this skill at the start of ANY XynPOS development session, or whenever you need to answer questions about the project architecture, service responsibilities, tech stack choices, API standards, multi-tenancy model, subscription plans, or codebase conventions. Also triggers when a developer asks "how does XynPOS work", "what stack do we use", "where does X live in the codebase", or starts working on any XynPOS feature.
XynPOS database, SQL, and migration expert — use when writing PostgreSQL queries, designing schema, creating migrations, optimizing slow queries, working with multi-tenant schema isolation, or managing database changes. Triggers when someone needs to write a SQL migration, add an index, debug a slow query, design a new table, work with GORM, or understand how the tenant schema model works. Also use when asked about data retention, backup strategy, or PostgreSQL configuration.
XynPOS DevOps, infrastructure, and deployment — use when working with Docker, CI/CD pipelines, Terraform, Kubernetes, monitoring, secrets management, or cloud infrastructure for XynPOS. Triggers when someone needs to write a Dockerfile, configure GitHub Actions, setup Kubernetes manifests, troubleshoot deployment issues, manage secrets with Doppler, setup Prometheus/Grafana monitoring, or plan infrastructure changes. Also use for backup strategy, health check configuration, or on-call incident response.
XynPOS documentation writer — use when creating or updating blueprints, writing Architecture Decision Records (ADRs), documenting APIs with Swagger, maintaining the operational runbook, updating CLAUDE.md, writing changelog entries, or creating developer guides for the XynPOS project. Triggers when someone needs to document a new feature or architectural decision, update existing blueprints, write an ADR for a tech decision, add Swagger annotations, update the onboarding guide, or maintain any documentation in the XynPOS-Docs repository.
XynPOS Next.js frontend development — use when building or reviewing React components, pages, hooks, or state management for the web dashboard or web POS application. Triggers when working on Next.js App Router, TypeScript components, TanStack Query data fetching, Zustand stores, React Hook Form, Tailwind CSS, shadcn/ui, or the offline POS interface. Also triggers for questions about frontend architecture, state management decisions, performance optimization, or API integration patterns in the XynPOS web apps.
XynPOS Go backend development — use when writing, reviewing, or debugging Go code for any XynPOS microservice. Covers clean architecture patterns, error handling, GORM database access, JWT/tenant security, Zap logging, Fiber handlers, gRPC, NATS events, and testing. Triggers when a developer asks to create a Go service, write a handler or usecase, fix a Go bug, review Go code, add an API endpoint, write a migration, or work with the XynPOS backend codebase. Also use when questions like "how do I structure this service" or "what's the right way to handle errors" come up.