Define end-to-end feature integration for the V.O.I.D./The Lab monorepo.
npx skills add https://github.com/CYBERSTALKER07/ATOMOS --skill the-lab-doctrine
Please help me install this Agent Skill. Skill: the-lab-doctrine Source: https://github.com/CYBERSTALKER07/ATOMOS/tree/main/.agents/skills/the-lab-doctrine Command: npx skills add https://github.com/CYBERSTALKER07/ATOMOS --skill the-lab-doctrine
Canonical playbook for implementing, extending, or auditing features across the V.O.I.D. / The Lab Industries monorepo. Use whenever the user asks to add a feature, endpoint, event, page, screen, or data field — before any code is authored. Captures the role→app matrix, backend package topology, the six-step mutating-handler shape, the dual event path (transactional outbox + EmitNotification), Spanner/cache/idempotency primitives, WebSocket hub discipline, auth scoping, H3 spatial rules, cross-role sync, and the local-simulator + physical-device dev loop so a new feature lands coherently across every surface that consumes it.
Follow this playbook at the outset of a feature to ensure end-to-end wiring across every surface before any code is authored.
High-intent search queries and answers about installing and using this skill.
To wire a new feature end-to-end, follow a canonical playbook that maps roles to apps and enforces a six-step mutating-handler pattern, dual event paths, and WebSocket hub discipline across all consuming surfaces.
The six-step mutating-handler pattern is a canonical workflow shape for Go backends that ensures fault-tolerant, idempotent operations by integrating Spanner, caching, and dual event paths for transactional outbox and notifications.
Implement multi-tenant auth scoping and idempotency by applying canonical architectural alignment rules that enforce Spanner primitives and fault-tolerant workflows before authoring any feature code in the monorepo.
Use a dual event path combining a transactional outbox and EmitNotification when adding a feature, event, or endpoint to ensure cross-role synchronization and consistent delivery across Kafka and WebSocket surfaces.
Yes, the feature integration playbook supports both local simulator and physical device dev loops to ensure new data fields, pages, and screens land coherently across mobile clients and backend surfaces.
The best way to scope a new endpoint is to apply initial feature scoping and architectural alignment guidelines, mapping roles to apps and verifying cross-surface wiring before any code is authored.
vlad-ryzhkovAudit Go backend repositories for API endpoints, infrastructure, and test coverage.
zangxin75Publishes events to both Kafka and Redis for durable and real-time delivery.
ricardohg1998-createStructure SaaS/CRM foundations with tenancy, RBAC, audit, and idempotent primitives.
changjian-wangGenerate C# domain event records, handlers, and service integrations for .NET.
