weltenbibliothek-architektur

Enforce architectural constraints and security protocols for dual-stack Flutter applications with Supabase and Cloudflare.

Updated Nov 23, 2025
One-click install
npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill weltenbibliothek-architektur
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: weltenbibliothek-architektur
Source: https://github.com/manuelbrandner85/Weltenbibliothekapp/tree/main/.claude/skills/weltenbibliothek-architektur
Command: npx skills add https://github.com/manuelbrandner85/Weltenbibliothekapp --skill weltenbibliothek-architektur

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill prevents architectural drift and security vulnerabilities by enforcing strict separation of concerns between the Flutter frontend, Supabase backend, and Cloudflare edge infrastructure.

Core Features & Use Cases

  • Boundary Enforcement: Ensures that specific logic, such as AI processing or media handling, is strictly routed to the correct infrastructure layer.
  • Credential Safety: Provides clear guidelines on where to store sensitive keys versus client-side configuration.
  • Use Case: When adding a new feature, use this Skill to verify whether the logic belongs in a Cloudflare Worker or a Supabase database function to maintain system integrity.

Quick Start

Apply the weltenbibliothek-architektur skill to validate the proposed implementation plan for the new community chat module.

Frequently Asked Questions about weltenbibliothek-architektur

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

FAQPage Schema
How do I enforce architectural boundaries between a Flutter frontend and a Supabase backend?

To enforce architectural boundaries between Flutter and Supabase, apply strict separation of concerns rules that route specific logic to the correct infrastructure layer, preventing unauthorized data access and logic leakage across the stack.

What is the best way to separate logic when using Cloudflare Workers with a Supabase database?

Separating logic with Cloudflare Workers and Supabase requires validating whether new features belong in edge functions or database functions to maintain system integrity and prevent architectural drift in production environments.

Where should I store API credentials and sensitive keys in a Flutter and Supabase dual-stack application?

Store API credentials and sensitive keys in a Flutter and Supabase stack by following strict credential safety guidelines that distinguish between server-side key storage and client-side configuration to prevent unauthorized access.

How do I validate that my Flutter and Cloudflare deployment workflow follows security protocols?

Validate your Flutter and Cloudflare deployment workflow by checking compliance against established security protocols, ensuring that routing for tasks like AI processing or media handling strictly targets the correct infrastructure layer.

When do I need to route AI processing logic to Cloudflare edge infrastructure instead of Supabase?

You need to route AI processing logic to Cloudflare edge infrastructure instead of Supabase when enforcing strict architectural constraints, ensuring heavy processing happens at the edge to prevent logic leakage and maintain database layer integrity.