How do I install the Repo Understanding Repository Architecture skill?

Run npx skillmds add wahidyankf/repo-understanding-repository-architecture in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

Is Repo Understanding Repository Architecture safe to use?

This skill has not completed SkillMD's automated safety review yet. Capability flags: docs only. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Repo Understanding Repository Architecture?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Repo Understanding Repository Architecture free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Repo Understanding Repository Architecture?

wahidyankf (@wahidyankf) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Repo Understanding Repository Architecture by wahidyankf

Name: Repo Understanding Repository Architecture
Rating: 4.2 (5 reviews)
Author: wahidyankf

Repo Understanding Repository Architecture

Six-layer governance hierarchy (Vision → Principles → Conventions → Development → Agents → Workflows). Use when understanding repository structure, tracing rules to foundational values, explaining architectural decisions, or navigating layer relationships.

wahidyankf 2404960 8 files · 16.6 KB Updated Sep 10, 2026

File contents

Repository Architecture - Six-Layer Hierarchy

This Skill provides guidance on the six-layer architecture governing the open-sharia-enterprise repository. Each layer builds on the foundation above, creating complete traceability from vision to workflows.

Purpose

Use this Skill when:

Understanding repository governance structure
Tracing rules back to foundational values
Explaining architectural decisions
Navigating layer relationships
Creating new conventions or practices
Understanding where Skills fit in the architecture

The Six Layers

See The Six Layers Overview for the layer diagram, key relationships, and a quick-reference table (location, purpose, change frequency, and what question each layer answers).

Layer 0-2: Vision, Principles, Conventions

See Layers 0-2 for WHY the project exists, the foundational values that govern conventions/development, and WHAT documentation rules those values imply.

Layer 3-5: Development, AI Agents, Workflows

See Layers 3-5 for HOW software is built, WHO the atomic executors are, and WHEN multi-step orchestration composes agents into processes.

Complete Traceability Example and Where Skills Fit

See Traceability and Skills for a worked Vision→Agents example (Color Accessibility) and why Skills are delivery infrastructure - not a governance layer - across their inline and fork modes.

Best Practices and Common Misconceptions

See Best Practices and Misconceptions for checklists when creating new conventions/practices/agents/workflows, and four common misconceptions about how the layers relate.

References

Repository Architecture - Complete architectural documentation with all traceability examples
Core Principles Index - Foundational principles
Conventions Index - Documentation conventions
Development Index - Development practices
Agents Index - All AI agents and responsibilities
Workflows Index - All orchestrated processes

Related Skills

repo-applying-maker-checker-fixer - Understanding the three-stage quality workflow (fits in L3 Development)
docs-creating-accessible-diagrams - Example of L2 Convention implemented through Skills delivery
repo-practicing-trunk-based-development - Example of L3 Development practice

Note: This Skill provides architectural overview. The authoritative Repository Architecture document contains complete traceability examples, detailed layer characteristics, and usage guidance.

See the reference/ directory in this Skill for detailed layer characteristics and governance relationships.

---name: repo-understanding-repository-architecturedescription: Six-layer governance hierarchy (Vision → Principles → Conventions → Development → Agents → Workflows). Use when understanding repository structure, tracing rules to foundational values, explaining architectural decisions, or navigating layer relationships.---# Repository Architecture - Six-Layer HierarchyThis Skill provides guidance on the six-layer architecture governing the open-sharia-enterprise repository. Each layer builds on the foundation above, creating complete traceability from vision to workflows.## PurposeUse this Skill when:- Understanding repository governance structure- Tracing rules back to foundational values- Explaining architectural decisions- Navigating layer relationships- Creating new conventions or practices- Understanding where Skills fit in the architecture## The Six LayersSee [The Six Layers Overview](./reference/layers-overview.md) for the layer diagram, key relationships, and a quick-reference table (location, purpose, change frequency, and what question each layer answers).## Layer 0-2: Vision, Principles, ConventionsSee [Layers 0-2](./reference/layers-0-2-vision-principles-conventions.md) for WHY the project exists, the foundational values that govern conventions/development, and WHAT documentation rules those values imply.## Layer 3-5: Development, AI Agents, WorkflowsSee [Layers 3-5](./reference/layers-3-5-development-agents-workflows.md) for HOW software is built, WHO the atomic executors are, and WHEN multi-step orchestration composes agents into processes.## Complete Traceability Example and Where Skills FitSee [Traceability and Skills](./reference/traceability-and-skills.md) for a worked Vision→Agents example (Color Accessibility) and why Skills are delivery infrastructure - not a governance layer - across their inline and fork modes.## Best Practices and Common MisconceptionsSee [Best Practices and Misconceptions](./reference/best-practices-and-misconceptions.md) for checklists when creating new conventions/practices/agents/workflows, and four common misconceptions about how the layers relate.## References- **[Repository Architecture](../../../repo-governance/repository-governance-architecture.md)** - Complete architectural documentation with all traceability examples- **[Core Principles Index](../../../repo-governance/principles/README.md)** - Foundational principles- **[Conventions Index](../../../repo-governance/conventions/README.md)** - Documentation conventions- **[Development Index](../../../repo-governance/development/README.md)** - Development practices- **[Agents Index](../../agents/README.md)** - All AI agents and responsibilities- **[Workflows Index](../../../repo-governance/workflows/README.md)** - All orchestrated processes## Related Skills- `repo-applying-maker-checker-fixer` - Understanding the three-stage quality workflow (fits in L3 Development)- `docs-creating-accessible-diagrams` - Example of L2 Convention implemented through Skills delivery- `repo-practicing-trunk-based-development` - Example of L3 Development practice---**Note**: This Skill provides architectural overview. The authoritative Repository Architecture document contains complete traceability examples, detailed layer characteristics, and usage guidance.See the `reference/` directory in this Skill for detailed layer characteristics and governance relationships.

Frequently asked questions