skills.rest
tajemniktv
tajemniktvCOMMUNITY
Explore all skills by this author →
Website𝕏@tajemniktvGitHub

tajsos-compose-screen-system

Enforce ownership boundaries and structural rules for TajsOS Jetpack Compose screens.

3|Updated Mar 18, 2026
Search Tags:#android#jetpack compose#compose#ui scaffolding#ownership boundaries#tajsos#screen architecture
One-click install
npx skills add https://github.com/tajemniktv/TajsOS --skill tajsos-compose-screen-system
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tajsos-compose-screen-system
Source: https://github.com/tajemniktv/TajsOS/tree/main/.agent/skills/tajsos-compose-screen-system
Command: npx skills add https://github.com/tajemniktv/TajsOS --skill tajsos-compose-screen-system

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Inconsistent screen structure and unclear ownership boundaries in TajsOS Compose implementations lead to duplicated scaffolding code, fragmented user experience, and maintenance overhead when updating shared shell behavior.

Core Features & Use Cases

  • Clear Ownership Boundaries: Defines distinct responsibilities for AppShell (persistent chrome, routing), ScreenScaffold (screen-level structure, insets, scrolling), and route content composables (state and block rendering).
  • Consistency Guardrails: Prohibits ad-hoc layout patterns like unnecessary BoxWithConstraints, custom padding, redundant scroll containers, and one-off max-width logic unless explicitly justified.
  • Use Case: When building a new task list screen for TajsOS, use this skill to align with existing ScreenScaffold primitives instead of creating a custom scaffold that duplicates shell behavior.

Quick Start

Follow the ownership and consistency rules outlined in this skill when implementing any new TajsOS Compose screen to ensure alignment with the project's established architecture.

Frequently Asked Questions about tajsos-compose-screen-system

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

FAQPage Schema
How do I standardize Jetpack Compose screen architecture in Android?▼

To standardize Jetpack Compose screen architecture, enforce consistent ownership boundaries by reusing existing AppShell and ScreenScaffold primitives instead of creating custom scaffolding abstractions.

What are the ownership boundaries for Compose screen scaffolding?▼

Ownership boundaries assign persistent chrome and routing to AppShell, screen-level structure and insets to ScreenScaffold, and state and block rendering to route content composables.

How do I avoid duplicating scaffolding code in Jetpack Compose?▼

Avoid duplicating scaffolding code by adhering to consistency guardrails that prohibit ad-hoc layout patterns like custom padding, redundant scroll containers, and one-off max-width logic.

When should I use SplitScreenScaffold instead of a custom layout?▼

Use SplitScreenScaffold for new screen development to align with established project architecture, eliminating ad-hoc layout patterns and duplicated shell behavior unless explicitly justified.

Why does my Compose screen layout break consistency guardrails?▼

Your Compose screen layout breaks consistency guardrails if it uses unnecessary BoxWithConstraints, custom padding, or redundant scroll containers instead of the established ScreenScaffold primitives.

Related Skills

Explore More Software Engineering Skills→
decoutkhanqindevdecoutkhanqindev
8

enforcing-stability-in-ci

Check Jetpack Compose UI stability regressions against a baseline during CI builds.

Community
Advanced
po4ykapo4yka
58

android-compose-patterns

Standardize Jetpack Compose UI architecture with Route/Screen separation and StateFlow.

Community
Intermediate
skeletorfletskeletorflet
7

android-compose

Build Android UIs with Jetpack Compose, ViewModel, StateFlow, and Material 3.

Community
Intermediate
sandeshbagmaresandeshbagmare

mobile-android-design

Design Android app interfaces with Material Design 3 and Jetpack Compose.

Community
Intermediate