project-overview

Summarize Unity URP project architecture, LifetimeScope hierarchy, and module dependencies.

Updated Aug 27, 2026
One-click install
npx skills add https://github.com/punkfuncgames/tetris-clone --skill project-overview-punkfuncgames
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: project-overview
Source: https://github.com/punkfuncgames/tetris-clone/tree/main/.claude/skills/project-overview
Command: npx skills add https://github.com/punkfuncgames/tetris-clone --skill project-overview-punkfuncgames

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill provides a clear, centralized explanation of the repository's architecture, module layout, LifetimeScope hierarchy, and bootstrapping flow so developers and architects can onboard faster, reason about cross-module interactions, and plan changes with reduced risk.

Core Features & Use Cases

  • Architecture Layers: Explains Presentation → Application → Domain → Infrastructure responsibilities and data flow.
  • LifetimeScope Hierarchy: Documents ProjectLifetimeScope, scene-scoped LifetimeScopes (MainMenu, Gameplay), and their registration responsibilities.
  • Module Map & Bootstrapping: Describes UPM package layout, assembly definitions, bootstrap phase ordering, build scene sequence, and module dependency relationships for impact analysis and integration planning.
  • Use Cases: Onboarding new team members, performing architecture reviews, planning refactors, and tracing where services and configuration persist across scenes.

Quick Start

Summarize the repository's architecture layers, LifetimeScope hierarchy, bootstrap phases, and module dependency map in one concise overview.

Frequently Asked Questions about project-overview

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

FAQPage Schema
How do I understand Unity URP modular project architecture and module flow?

To map Unity URP project architecture, you need to trace Presentation, Application, Domain, and Infrastructure layers, alongside LifetimeScope hierarchies and UPM package layouts. This reveals module interactions, bootstrap phase ordering, and assembly mappings for onboarding and design reviews.

How does LifetimeScope hierarchy work in Unity modular UPM projects?

LifetimeScope hierarchy in Unity modular projects organizes dependency injection by defining ProjectLifetimeScope and scene-scoped contexts like MainMenu or Gameplay. This structure clarifies service registration responsibilities and tracks where configurations persist across different scenes.

What is the best way to document bootstrapping phases and assembly definitions in Unity?

Documenting bootstrapping phases and assembly definitions in Unity requires outlining UPM package layouts, build scene sequences, and module dependency relationships. This approach captures phase ordering and inter-module dependencies to support cross-module impact analysis and integration planning.

Can I use a project architecture overview for cross-module impact analysis in Unity?

Yes, a project architecture overview supports cross-module impact analysis in Unity by surfacing layer definitions, module dependency maps, and assembly mappings. This allows developers and architects to reason about interactions and plan changes with reduced risk.

When do I need to trace module dependencies and layer definitions for a Unity project?

You need to trace module dependencies and layer definitions when onboarding new team members, performing architecture reviews, planning refactors, or analyzing cross-module impact. It clarifies service persistence across scenes and bootstrap phase ordering for Unity modular projects.