Architecture Rules

Define standardized architecture rules for cross-system integration and network configuration.

Updated Jan 27, 2026
One-click install
npx skills add https://github.com/taikiwt/sitecue --skill architecture-rules-taikiwt
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: Architecture Rules
Source: https://github.com/taikiwt/sitecue/tree/main/.agent/skills/architecture
Command: npx skills add https://github.com/taikiwt/sitecue --skill architecture-rules-taikiwt

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architecture guidelines to standardize cross-system integration patterns, network rules, and component boundaries across the extension, API, and app layers.

Core Features & Use Cases

  • One-time data relay patterns: standardize how large payloads move from the extension to App Basecamp, including secure context handling and lifecycle cleanup.
  • Local development network hardening: codify fixed localhost behavior, port binding, and host header normalization to prevent environment-specific errors.
  • Basecamp governance & separation: enforce separation of concerns (Notes vs Drafts), template-driven UI, and robust routing to avoid feature coupling.

Quick Start

Configure and apply the architecture rules to any new integration: copy the standard patterns to your module and adapt them to your boundaries.

Frequently Asked Questions about Architecture Rules

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

FAQPage Schema
How do I standardize cross-system integration patterns for large payload relays?

Standardize cross-system integration by enforcing one-time data relay patterns that handle secure context and lifecycle cleanup for moving large payloads from extensions to App Basecamp. This prevents data duplication and ensures predictable routing across component boundaries.

How do I fix localhost networking issues during local development?

Fix localhost networking issues by codifying fixed localhost behavior, strict port binding, and host header normalization. These network rules prevent environment-specific errors and ensure stable local development configurations across your application layers.

What is the best way to enforce separation of concerns between Notes and Drafts in App Basecamp?

Enforce separation of concerns between Notes and Drafts by applying Basecamp governance rules that mandate template-driven UI and robust routing. This approach avoids feature coupling and maintains strict architectural boundaries within the application.

Are there strict deployment constraints for OpenNext-based deployments?

Yes, OpenNext-based deployments require strict deployment constraints to guide data flows, routing, and security. Applying these standardized architecture rules ensures your extension, API, and app layers maintain proper boundaries during release.

How do I apply architecture rules to a new module integration?

Apply architecture rules to new module integrations by copying the standard data flow and network patterns, then adapting them to your specific component boundaries. This ensures secure cross-system routing from the extension to the API.