gtsi-claude-architect

Analyzes and restructures CLAUDE.md files and .claude/rules with approval-gated changes.

Updated May 21, 2026
One-click install
npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-claude-architect-gestaosian
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: gtsi-claude-architect
Source: https://github.com/gestaosian/gtsi-claude-skills/tree/main/plugins/gtsi-ops-plugin/skills/gtsi-claude-architect
Command: npx skills add https://github.com/gestaosian/gtsi-claude-skills --skill gtsi-claude-architect-gestaosian

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve? Repositories accumulate disorganized, duplicated, or contradictory Claude Code instructions across CLAUDE.md, .claude/rules, runbooks, and generated templates, causing lost policies and bloated context. This Skill diagnoses the existing instruction architecture and proposes a modular, traceable reorganization without silently dropping any rule. ## Core Features & Use Cases - Instruction discovery and classification: Finds CLAUDE.md, .claude/rules, commands, and SKILL.md files, detects auto-generated templates, and classifies each rule by scope (global, path-specific, runbook, ADR, wiki). - Approval-gated migration: Produces a diagnostic report with a traceability matrix in .gtsi/reviews/ and applies changes only after explicit user approval, preserving security and governance policies. - Mandatory behavioral baseline: Ensures every restructured CLAUDE.md explicitly contains four working principles (think before changing, prioritize simplicity, surgical changes, verifiable results) and validates their presence. - Use Case: A team whose automation overwrites CLAUDE.md across projects uses this Skill to identify the source template, separate global rules from project-specific ones, and migrate Airflow and dbt rules into scoped .claude/rules files. ## Quick Start Ask the assistant to review and reorganize this repository's CLAUDE.md and .claude/rules, preserving all existing policies and proposing a modular structure before applying any changes.

Frequently Asked Questions about gtsi-claude-architect

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

FAQPage Schema
How do I reorganize a large CLAUDE.md into .claude/rules?▼

The Skill discovers all instruction files, classifies each rule by scope, and proposes moving language- or path-specific rules into .claude/rules files with frontmatter paths. Changes are applied only after you approve the diagnostic report.

How to migrate a project to .claude/rules without losing existing policies?▼

It builds a traceability matrix mapping every original rule to its proposed destination and action, so no mandatory rule disappears silently. Security and governance rules are preserved or their removal is explicitly highlighted.

Can it handle CLAUDE.md files generated by automation templates?▼

Yes. It detects generation markers, identifies the source template and the copying automation, and proposes changes at the source rather than only in the generated file. It also reports which consumer projects would be affected.

Does this Skill modify application code or infrastructure?▼

No. It only touches instruction files, templates, and related documentation such as CLAUDE.md, .claude/rules, and runbooks. It never changes application code, pipelines, DAGs, dbt models, or infrastructure.

What are the limitations of Markdown-based Claude Code rules?▼

Markdown rules guide behavior but are not technical enforcement. The Skill flags critical restrictions like blocking force pushes or destructive SQL and recommends permissions, hooks, CI, or branch protection instead of relying on text alone.