How do I install the Architecture Guardrails skill?

Run npx skillmds@latest add itechdev-mx/architecture-guardrails in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Architecture Guardrails safe to use?

This skill has not completed SkillMD's automated safety review yet. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Architecture Guardrails?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Architecture Guardrails free to use?

Yes. Installing skills from SkillMD is free. This skill is licensed under Apache-2.

Who published Architecture Guardrails?

ITECHDEV-MX (@itechdev-mx) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Architecture Guardrails by itechdev-mx

Name: Architecture Guardrails
Author: ITECHDEV-MX

Architecture Guardrails

Architecture guardrails for AriaCore across local store, cloud sync, dashboard, and plugins. Trigger: Any change that affects system boundaries, ownership, state flow, or cross-package responsibilities.

ITECHDEV-MX 3da96d0 1.4 KB Updated Sep 17, 2026

File contents

When to Use

Use this skill when:

Adding a new subsystem or major package
Moving responsibilities between local store, cloud, dashboard, or plugins
Changing sync flow, source-of-truth rules, or persistence boundaries

Core Guardrails

Local SQLite is the source of truth; cloud is replication and shared access.
Keep plugin/adaptor layers thin; real behavior belongs in Go packages.
Prefer explicit boundaries: store, cloudstore, server, dashboard, autosync.
New features must fit the existing local-first mental model before they fit the UI.
Do not hide cross-system coupling inside helpers or templates.

Decision Rules

Local-only concern -> internal/store
Cloud materialization or org-wide control -> internal/cloud/cloudstore
HTTP contract or enforcement -> internal/cloud/cloudserver
Browser rendering and UX -> internal/cloud/dashboard
Background orchestration -> internal/cloud/autosync

Validation

Add regression tests for every boundary change.
Verify local, remote, and dashboard behavior still tell the same product story.
If the change touches sync, test both push and pull paths.

Frequently asked questions