Skip to content
Back to skills

Architecture Guard

ASecurity

Enforces Boklo Wallet’s backend-authoritative, event-driven FinTech architecture. Rejects any suggestion that violates the Source of Truth.

  • 2 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added September 27, 2026
developmentfrontendbackend

Works with

  • cli

Security analysis

A100/100

Scanned September 27, 2026

npx -y skills add David-Li0406/meta-skill-evloving --skill architecture-guard --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Architecture Guard?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Architecture Guard
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/david-li0406-architecture-guard/badge)](https://www.skillsdirectory.com/skills/david-li0406-architecture-guard)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: architecture-guard
description: Enforces Boklo Wallet’s backend-authoritative, event-driven FinTech architecture. Rejects any suggestion that violates the Source of Truth.
---

# Architecture Guard

## When to use this skill

- When proposing major architectural changes.
- When designing new features that involve financial transactions.
- When a user request seems to conflict with the Backend-Authoritative principle.
- To verify if a proposed solution respects the Single Source of Truth rules.

## How to use it

1. **Analyze the Proposal**: Review the proposed code or design against the `SOURCE_OF_TRUTH.md` and core Boklo Wallet rules.
2. **Check for Violations**:
   - Does the client write to the ledger/balance? (VIOLATION)
   - Is logic placed in the Eventarc router instead of a consumer? (VIOLATION)
   - Is the frontend calculating financial states? (VIOLATION)
3. **Enforce Rules**:
   - If a violation is found, **REJECT** the proposal immediately.
   - Cite the specific rule from `SOURCE_OF_TRUTH.md` that was violated.
   - Provide a compliant alternative (e.g., "Instead of updating the balance locally, emit a `transaction.created` event and listen for the backend response").
4. **Guard the boundaries**: Ensure that the boundary between Client (Observer) and Backend (Authority) is distinct and rigid.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…