원클릭으로 Manus에서 모든 스킬 실행

xynpos-context

스타3

포크0

업데이트2026년 5월 22일 04:44

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.

설치

Codex 또는 Claude로 설치 이 Prompt를 복사해 Codex, Claude 또는 다른 어시스턴트에 붙여 넣으면 Skill 페이지를 검토하고 설치를 진행할 수 있습니다.

Manus에서 실행

출처

ilramdhan

ilramdhan/XynPOS-Docs

GitHub 저장소 열기 Creator 저장소 보기

다운로드

Manus에서 실행

XynPOS — Master Project Context

XynPOS is a multi-tenant SaaS Point of Sale application by Extended Synaptic (XYN). Load this skill at the start of every XynPOS dev session to get full project orientation.

Quick Load

Read the relevant reference files based on what you need:

Architecture overview → references/architecture.md
Full service map & ports → references/services.md
API standards → references/api-standards.md
Subscription plans & limits → references/plans.md

Project at a Glance

Dimension	Detail
Product	Point of Sale SaaS, Indonesia-first
Company	Extended Synaptic (XYN)
Segments	T1 UMKM → T4 Enterprise
Primary market	Indonesia, SEA expansion Year 2
Repository	github.com/extendedsynaptic/xynpos (monorepo)
Docs repo	github.com/ilramdhan/XynPOS-Docs

Tech Stack Summary

Layer	Stack
Backend	Go 1.22 + Fiber v2 + gRPC (inter-service)
Web	Next.js 14 + TypeScript + Tailwind + shadcn/ui
Mobile	Flutter 3 + Dart + Riverpod + go_router
Database	PostgreSQL 16 (schema-per-tenant) + Redis 7
Search	Meilisearch
Queue	NATS → Kafka (Phase 2)
Storage	Cloudflare R2 (S3-compatible, zero egress)
Cloud	DigitalOcean → AWS Phase 3
Payment	Xendit + Midtrans + Stripe
Push	Firebase FCM

Multi-Tenancy Model

Every tenant gets an isolated PostgreSQL schema tenant_{uuid}. The API Gateway middleware sets search_path from JWT claims before every request. There must be zero cross-tenant data access under any circumstances.

Schemas:
  public_xyn    → tenants, subscriptions, invoices, users (global)
  auth_svc      → refresh_tokens, otps
  tenant_{uuid} → all business data (products, transactions, customers…)

API Standard (non-negotiable)

// Success
{ "success": true, "data": { ... } }
{ "success": true, "data": [...], "meta": { "page":1, "per_page":20, "total":100 } }

// Error
{ "success": false, "error": { "code": "PRODUCT_NOT_FOUND", "message": "...", "http_status": 404 } }

Base URL: /api/v1/ · Auth: Authorization: Bearer {token}

Critical Security Rules

tenantID always from c.Locals("tenantID") (JWT) — never from request body/query
All SQL via GORM parameterized — never string concatenation
No secrets in code, Dockerfiles, or logs
Sensitive data (password, PIN, NPWP) never logged

Monorepo Layout

xynpos/
├── backend/services/{service}/   12 Go microservices
├── backend/shared/               shared packages: jwt, db, response, errors, logger
├── frontend/apps/web-pos/        Kasir interface (Next.js)
├── frontend/apps/web-dashboard/  Owner dashboard (Next.js)
├── mobile/xynpos_mobile/         Flutter iOS + Android
└── infra/                        Terraform, K8s, Docker

For deep detail on any topic, read the appropriate reference file.

이 저장소의 다른 Skills

같은 저장소

xynpos-api-design

ilramdhan/XynPOS-Docs

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.

2026-05-223

xynpos-code-review

ilramdhan/XynPOS-Docs

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.

2026-05-223

xynpos-database

ilramdhan/XynPOS-Docs

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.

2026-05-223

xynpos-devops

ilramdhan/XynPOS-Docs

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.

2026-05-223

xynpos-docs-writer

ilramdhan/XynPOS-Docs

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.

2026-05-223

xynpos-frontend

ilramdhan/XynPOS-Docs

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.

2026-05-223

name	xynpos-context
description	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.
license	See LICENSE.txt

XynPOS — Master Project Context

XynPOS is a multi-tenant SaaS Point of Sale application by Extended Synaptic (XYN). Load this skill at the start of every XynPOS dev session to get full project orientation.

Quick Load

Read the relevant reference files based on what you need:

Architecture overview → references/architecture.md
Full service map & ports → references/services.md
API standards → references/api-standards.md
Subscription plans & limits → references/plans.md

Project at a Glance

Dimension	Detail
Product	Point of Sale SaaS, Indonesia-first
Company	Extended Synaptic (XYN)
Segments	T1 UMKM → T4 Enterprise
Primary market	Indonesia, SEA expansion Year 2
Repository	github.com/extendedsynaptic/xynpos (monorepo)
Docs repo	github.com/ilramdhan/XynPOS-Docs

Tech Stack Summary

Layer	Stack
Backend	Go 1.22 + Fiber v2 + gRPC (inter-service)
Web	Next.js 14 + TypeScript + Tailwind + shadcn/ui
Mobile	Flutter 3 + Dart + Riverpod + go_router
Database	PostgreSQL 16 (schema-per-tenant) + Redis 7
Search	Meilisearch
Queue	NATS → Kafka (Phase 2)
Storage	Cloudflare R2 (S3-compatible, zero egress)
Cloud	DigitalOcean → AWS Phase 3
Payment	Xendit + Midtrans + Stripe
Push	Firebase FCM

Multi-Tenancy Model

Schemas:
  public_xyn    → tenants, subscriptions, invoices, users (global)
  auth_svc      → refresh_tokens, otps
  tenant_{uuid} → all business data (products, transactions, customers…)

API Standard (non-negotiable)

// Success
{ "success": true, "data": { ... } }
{ "success": true, "data": [...], "meta": { "page":1, "per_page":20, "total":100 } }

// Error
{ "success": false, "error": { "code": "PRODUCT_NOT_FOUND", "message": "...", "http_status": 404 } }

Base URL: /api/v1/ · Auth: Authorization: Bearer {token}

Critical Security Rules

tenantID always from c.Locals("tenantID") (JWT) — never from request body/query
All SQL via GORM parameterized — never string concatenation
No secrets in code, Dockerfiles, or logs
Sensitive data (password, PIN, NPWP) never logged

Monorepo Layout

xynpos/
├── backend/services/{service}/   12 Go microservices
├── backend/shared/               shared packages: jwt, db, response, errors, logger
├── frontend/apps/web-pos/        Kasir interface (Next.js)
├── frontend/apps/web-dashboard/  Owner dashboard (Next.js)
├── mobile/xynpos_mobile/         Flutter iOS + Android
└── infra/                        Terraform, K8s, Docker

For deep detail on any topic, read the appropriate reference file.