architect

Validate proposed solutions against module structure and API contracts.

Updated Mar 13, 2026

Search Tags:#architecture #code review #system design #compliance #technical debt

Ready to run

npx skills add https://github.com/ylazakovich/car-service-platform --skill architect-ylazakovich

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: architect
Source: https://github.com/ylazakovich/car-service-platform/tree/main/.agents/architect
Command: npx skills add https://github.com/ylazakovich/car-service-platform --skill architect-ylazakovich

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes references (resource) components.

What problem does it solve?

This Skill verifies that proposed solutions are consistent with the project's architecture, preventing the introduction of hidden technical debt.

Core Features & Use Cases

Architecture Conformance: Checks if new features or changes adhere to established architectural guidelines.
Technical Debt Prevention: Identifies potential long-term issues arising from architectural misalignment.
Use Case: Before implementing a new microservice, use this Skill to review its design against the existing system's module structure and API contracts.

Quick Start

Review the provided plan against the current module structure and API contracts.

Frequently Asked Questions about architect

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

FAQPage Schema

How do I validate that a proposed solution aligns with existing architecture?▼

To validate architecture conformance, review the proposed plan against existing module structures and API contracts. This ensures new features align with established architectural guidelines and do not introduce hidden technical debt.

What is architecture conformance checking and when do I need it?▼

Architecture conformance checking verifies that proposed solutions match established module boundaries and data contracts. You need it before implementing new features or microservices to prevent long-term compatibility issues and hidden technical debt.

Does architecture review prevent hidden technical debt in new microservices?▼

Yes, architecture review prevents hidden technical debt by analyzing proposed plans against existing module structures and API contracts. It identifies architectural misalignment before implementation, avoiding potential long-term compatibility and migration issues.

What's the best way to check module boundaries and API compatibility before implementation?▼

The best way to check module boundaries is analyzing the implementation plan against current API and data contracts. Focus on architectural compatibility and necessary migrations while deliberately avoiding micro-optimizations during the review process.

Why does my new feature design introduce technical debt despite passing code review?▼

New feature designs introduce technical debt when they violate architectural guidelines. Standard code review often focuses on micro-optimizations, missing deeper structural issues like broken module boundaries, incompatible data contracts, or forced migrations.