architecture

Create and maintain system architecture blueprints with project registries and dependencies.

1|Updated May 26, 2026

Search Tags:#architecture #software engineering #system design #dependencies #blueprint #project registry

Ready to run

npx skills add https://github.com/virajp/ai-plugins --skill architecture-virajp

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architecture
Source: https://github.com/virajp/ai-plugins/tree/main/plugins/vwf/skills/architecture
Command: npx skills add https://github.com/virajp/ai-plugins --skill architecture-virajp

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill helps teams create and maintain a complete system architecture document and project registry without losing alignment between product structure, technical decisions, and implementation boundaries.

Core Features & Use Cases

Architecture Documentation: Builds or updates docs/blueprint/architecture.md with system topology, projects, stacks, dependencies, and cross-cutting decisions.
Project Registry Management: Captures machine-readable project metadata, capability mappings, dependency relationships, and documentation units for downstream planning workflows.
Use Case: A product team starting a multi-project application can use this Skill to define services, frontends, packages, infrastructure choices, and shared system decisions before implementation begins.

Quick Start

Ask the architecture skill to create or update the system architecture blueprint for the current workspace.

Frequently Asked Questions about architecture

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

FAQPage Schema

How do I create a system architecture blueprint for a new software project?▼

To create a system architecture blueprint, this Skill applies structured elicitation to define project boundaries, dependencies, and technical decisions. It outputs a structured architecture document and a project registry to align product structure with implementation.

What is a project registry in system design and why do I need one?▼

A project registry in system design is a machine-readable metadata store of capability mappings and dependency relationships. It captures technical decisions and documentation units to maintain alignment between architecture boundaries and downstream planning workflow.

How do I document system topology and cross-cutting technical decisions for multiple services?▼

Documenting system topology and cross-cutting technical decisions is achieved by updating the architecture blueprint. This process captures shared infrastructure choices, service stacks, and dependency relationships to ensure consistency across all application projects.

Can I use this to plan dependencies for a multi-project application before implementation?▼

Yes, you can use this Skill to plan dependencies for a multi-project application before implementation. It validates registry consistency and synchronizes architecture documentation with implementation planning artifacts to define clear project boundaries.

What is the best way to maintain alignment between architecture documentation and implementation planning artifacts?▼

The best way to maintain alignment is through continuous synchronization between architecture documentation and implementation planning artifacts. This Skill validates registry consistency to ensure technical decisions and dependency relationships remain accurate during development.

When should I not use a centralized architecture blueprint for system design?▼

You should avoid a centralized architecture blueprint if your project lacks complex cross-cutting decisions or multiple interdependent services. The structured registry and topology planning are intended for multi-project applications requiring strict boundary and dependency management.