manage-architecture

Automate creation and maintenance of Lucid Composite Architecture documentation.

3|Updated Nov 28, 2025
One-click install
npx skills add https://github.com/rayk/lucid-toolkit --skill manage-architecture
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: manage-architecture
Source: https://github.com/rayk/lucid-toolkit/tree/main/plugins/architect/skills/manage-architecture
Command: npx skills add https://github.com/rayk/lucid-toolkit --skill manage-architecture

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

Create and maintain architecture documentation following Lucid Composite Architecture (LCA) principles.

Core Features & Use Cases

  • ARCHITECTURE.md templates and governance
  • Organize Atoms, Composites, Conduits, and Deployable Units
  • Map data strategy to Schema.org boundaries

Quick Start

Assess current ARCHITECTURE.md, define scope level, and draft or update the architecture sections with navigation headers

Frequently Asked Questions about manage-architecture

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

FAQPage Schema
How do I document architecture following LCA principles?

LCA (Lucid Composite Architecture) documentation organizes systems into Atoms, Composites, Conduits, and Deployable Units with defined boundaries. This Skill automates ARCHITECTURE.md creation and maintenance by applying LCA templates, enforcing structured governance, and mapping data strategy to Schema.org at component boundaries.

What should an ARCHITECTURE.md file contain?

ARCHITECTURE.md should define scope level, describe architecture blocks, document Atoms (smallest units), Composites (grouped components), Conduits (data flows), and Deployable Units with versioned ADRs. This Skill provides templates and enforcement to ensure consistent structure and boundary-aware documentation.

Can I use ADRs to track architecture decisions?

Yes. ADRs (Architecture Decision Records) are versioned and boundary-aware within the LCA framework. This Skill automates their creation and maintenance alongside architecture documentation, integrating them into a defined mapping layer that aligns with your platform, repository, or component scope.

How do I align data strategy with Schema.org in architecture documentation?

This Skill enforces data-strategy alignment with Schema.org at component boundaries. It maps Conduits (data flows) and interfaces to Schema.org standards, ensuring consistent external data contracts and enabling interoperability documentation within your ARCHITECTURE.md.

What's the difference between Composites and Conduits in LCA?

Composites are grouped collections of Atoms (components), while Conduits are versioned data flows and interfaces between them. This Skill documents both within a structured template, treating Conduits as boundary-aware, enabling clear separation of concerns and governed data contracts.

Do I need existing documentation to start using LCA governance?

No. This Skill assesses your current ARCHITECTURE.md, defines scope level (platform, repository, or component), and drafts architecture sections from scratch. It structures Atoms, Composites, Conduits, and Deployable Units with navigation headers and governance templates.