architecture-guardian

Category: Development & Coding | Uploader: meta-secret | Downloads: 0 | Version: v1.0（Latest）

Preserve Rust workspace architecture and boundaries before coding; align with ARCHITECTURE.md.

Changelog: Source: GitHub https://github.com/meta-secret/meta-secret-core

Directory Structure

Current level: tree/main/.claude/skills/architecture-guardian/

📄 SKILL.md 1.3 KB

SKILL.md

---
name: architecture-guardian
description: Preserve Rust workspace architecture and boundaries before coding; align with ARCHITECTURE.md.
---

# Architecture Guardian (meta-secret-core)

You protect the **Rust workspace** layout: crates, crypto core, server/CLI/WASM/mobile adapters.

## Job

1. Identify the correct **crate** and module for a change.
2. Preserve boundaries in [ARCHITECTURE.md](../../../ARCHITECTURE.md).
3. Prefer minimal, composable designs over broad refactors.
4. Flag **FFI/UniFFI** impact early (consumer repo: meta-secret-compose).

## Hard rules

- Do not put crypto/protocol logic in unrelated crates “for convenience.”
- Do not expand public APIs without considering stability and mobile consumers.
- Do not add dependencies to `meta-secret-core` without justification.
- Do not log or expose secret material (see [SECURITY.md](../../../SECURITY.md)).

## Read first

- [ARCHITECTURE.md](../../../ARCHITECTURE.md)
- [PROJECT_CONTEXT.md](../../../PROJECT_CONTEXT.md)
- [SECURITY.md](../../../SECURITY.md)

## Placement checklist

Before writing code:

- Which **crate** owns this behavior?
- Does **`meta-secret-core`** already expose a hook or type?
- Does this affect **FFI** exports (mobile targets)?
- What is the **smallest** test surface (`cargo test -p …`)?

Comments 0

Latest | Hot

Please login before commenting.

No comments yet. Be the first one!

architecture-guardian

Directory Structure

SKILL.md

Report

Notice