Skill

data-flow-architecture

Firebase real-time sync patterns. Firestore triggers to Cloud Functions event chains. Data pipeline design. [EXPLICIT]

Install

Run in your terminal

npx claudepluginhub javimontano/jm-adk-alfa

Tool Access

This skill uses the workspace's default tool permissions.

Supporting Assets

View in Repository

agents/guardian.md

agents/lead.md

agents/specialist.md

agents/support.md

evals/evals.json

knowledge/body-of-knowledge.md

knowledge/knowledge-graph.md

prompts/meta.md

prompts/primary.md

prompts/variations/deep.md

prompts/variations/quick.md

templates/output.docx.md

templates/output.html

Skill Content

Similar Skills

skill-lookup

Searches, retrieves, and installs Agent Skills from prompts.chat registry using MCP tools like search_skills and get_skill. Activates for finding skills, browsing catalogs, or extending Claude.

prompts.chat

157.5k

prompt-lookup

Searches prompts.chat for AI prompt templates by keyword or category, retrieves by ID with variable handling, and improves prompts via AI. Use for discovering or enhancing prompts.

prompts.chat

157.5k

agent-eval

Compares coding agents like Claude Code and Aider on custom YAML-defined codebase tasks using git worktrees, measuring pass rate, cost, time, and consistency.

everything-claude-code

139.2k

Stats

Stars1

Forks0

Last CommitMar 28, 2026

Actions

View Source View Plugin View on GitHub View README

Core Principles

Law of Firebase-First: All architecture decisions constrained to Firebase/Google ecosystem (R-002). [EXPLICIT]

Law of Evidence: Every architectural claim tagged [CODE], [CONFIG], [DOC], [INFERENCE], or [ASSUMPTION]. [EXPLICIT]

Law of Diagrams: Architecture without diagrams is incomplete. Use Mermaid for C4, sequence, flow. [EXPLICIT]

Scenario

Handling

Empty or minimal input

Request clarification before proceeding

Conflicting requirements

Flag conflicts explicitly, propose resolution

Out-of-scope request

Redirect to appropriate skill or escalate

data-flow-architecture {Architecture} (v1.0)

"Architecture is decisions. Document every one."

Purpose

Firebase real-time sync patterns. Firestore triggers to Cloud Functions event chains. Data pipeline design. [EXPLICIT] When to use: When designing or reviewing architecture for Firebase/Google stack projects.

Core Principles

Law of Firebase-First: All architecture decisions constrained to Firebase/Google ecosystem (R-002). [EXPLICIT]
Law of Evidence: Every architectural claim tagged [CODE], [CONFIG], [DOC], [INFERENCE], or [ASSUMPTION]. [EXPLICIT]
Law of Diagrams: Architecture without diagrams is incomplete. Use Mermaid for C4, sequence, flow. [EXPLICIT]

Core Process

Phase 1: Analyze requirements and constraints.

Phase 2: Design architecture with Firebase/Google services.

Phase 3: Document with C4 diagrams, decision records, and evidence tags.

Validation Gate

Architecture designed within Firebase/Google/Hostinger constraints
C4 or sequence diagrams produced (Mermaid)
Evidence tags on all claims
ADR created for significant decisions
No AWS/Azure/Docker references

Usage

Example invocations:

"/data-flow-architecture" — Run the full data flow architecture workflow
"data flow architecture on this project" — Apply to current context

Assumptions & Limits

Assumes access to project artifacts (code, docs, configs) [EXPLICIT]
Requires English-language output unless otherwise specified [EXPLICIT]
Does not replace domain expert judgment for final decisions [EXPLICIT]

Edge Cases

Scenario	Handling
Empty or minimal input	Request clarification before proceeding
Conflicting requirements	Flag conflicts explicitly, propose resolution
Out-of-scope request	Redirect to appropriate skill or escalate