codebase-architect

Name: codebase-architect
Availability: InStock
Author: sgpropertyanalytics

Enforce layering, data boundaries, and service-layer responsibilities in codebase designs.

2|1|Updated Dec 15, 2025

Search Tags:#architecture #debugging #codebase #data-integrity #software-engineering #design-patterns #layering

Ready to run

npx skills add https://github.com/sgpropertyanalytics/sg-property-analytics --skill codebase-architect

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: codebase-architect
Source: https://github.com/sgpropertyanalytics/sg-property-analytics/tree/main/.claude/skills/codebase-architect
Command: npx skills add https://github.com/sgpropertyanalytics/sg-property-analytics --skill codebase-architect

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides essential system-architecture guidance to prevent drift, enforce layering rules, and protect data integrity across a codebase.

Core Features & Use Cases

Establishes clear layering responsibilities and boundary patterns to guide design decisions.
Assists in planning implementations, evaluating new subsystems, and debugging architectural issues with traceable rules.
Use Case: In a project redesign, apply these rules to validate that components, services, and routes respect boundaries and data flow conventions.

Quick Start

Summarize the current architecture and key constraints to align the team.

Frequently Asked Questions about codebase-architect

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

FAQPage Schema

How do I enforce layering rules and protect data integrity across my codebase?▼

To enforce layering rules and protect data integrity, apply architectural guidance during planning and design reviews to establish clear boundary normalization, canonical type decisions, and disciplined service-layer responsibilities across components.

What is the best way to prevent architecture drift when adding new subsystems?▼

The best way to prevent architecture drift when adding new subsystems is to validate component boundaries and data flow conventions against traceable design patterns, ensuring routes and services respect established layering responsibilities.

How do I debug architectural issues related to data boundaries?▼

Debug architectural issues related to data boundaries by reviewing boundary normalization and canonical type decisions, tracing data flow across service-layer responsibilities to identify where components violate consistent design patterns.

Does this architecture guidance work for evaluating existing components during a project redesign?▼

Yes, this architecture guidance works for evaluating existing components during a project redesign by validating that components, services, and routes respect boundaries and data flow conventions through traceable layering rules.

When do I need canonical type decisions for system design?▼

You need canonical type decisions for system design when normalizing boundaries across components, ensuring disciplined service-layer responsibilities, and maintaining consistent patterns during implementation planning and debugging.