CURBOS SKILL

Manages secure CurbOS Point-of-Sale integration within the PrepOS application.

Updated Aug 23, 2026
One-click install
npx skills add https://github.com/KuschiKuschbert/prepflow-web --skill curbos-skill
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: CURBOS SKILL
Source: https://github.com/KuschiKuschbert/prepflow-web/tree/main/app/curbos
Command: npx skills add https://github.com/KuschiKuschbert/prepflow-web --skill curbos-skill

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill provides a secure and controlled way to manage the CurbOS Point-of-Sale system integration within the PrepFlow application, ensuring that modifications to this protected area are intentional and well-tested.

Core Features & Use Cases

  • Protected Area Management: Enforces commit hooks and tooling exclusions for the app/curbos/ directory to prevent accidental changes.
  • Integration Overview: Details how CurbOS is integrated as a separate product using PrepFlow's hosting and Supabase.
  • Use Case: A developer needs to update a specific component within the CurbOS integration. This Skill's documentation guides them on the necessary precautions and bypass methods (ALLOW_CURBOS_MODIFY=1) to make the change safely.

Quick Start

Use the CurbOS Skill to review the protected area warnings before committing changes to app/curbos/.

Frequently Asked Questions about CURBOS SKILL

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I protect a POS integration directory from accidental commits?

To protect a POS integration directory, enforce pre-commit hooks and tooling exclusions for the protected area. This prevents accidental changes by ensuring modifications are intentional and well-tested before they reach the repository.

How does a POS system integrate with a Supabase backend?

A POS system integrates with Supabase by running as a separate product using the parent application's hosting infrastructure. This architecture isolates the POS module while sharing the Supabase backend for data management and authentication flows.

Why do pre-commit hooks block changes to my POS integration files?

Pre-commit hooks block changes to POS integration files because the directory is a protected area enforcing strict modification protocols. This mechanism ensures all updates are intentional and prevents accidental tooling modifications.

Does the CurbOS Skill documentation include API routes and authentication flow details?

Yes, the CurbOS Skill documentation provides an overview of the integration architecture, including key files, API routes, and the authentication flow to ensure controlled development and maintenance of the module.