tajsos-product-ux

Enforce TajsOS LifeOS product and UX principles for feature decisions.

3|Updated Mar 18, 2026
One-click install
npx skills add https://github.com/tajemniktv/TajsOS --skill tajsos-product-ux
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tajsos-product-ux
Source: https://github.com/tajemniktv/TajsOS/tree/main/.agent/skills/tajsos-product-ux
Command: npx skills add https://github.com/tajemniktv/TajsOS --skill tajsos-product-ux

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This Skill eliminates inconsistent product framing, naming drift, and disjointed UX choices that would break TajsOS's cohesive LifeOS-first design, ensuring all product and experience decisions align with the project's core principles.

Core Features & Use Cases

  • Product Framing Guidance: Enforces TajsOS's LifeOS-first positioning over generic second-brain app framing to maintain clear product identity.
  • Feature Prioritization: Keeps MVP scope centered on core life objects (dashboard, notes, tasks) to avoid feature sprawl and isolated functionality silos.
  • UX Coherence Enforcement: Ensures consistent interaction patterns, theme usage, and naming conventions across all TajsOS screens and surfaces.
  • Use Case: When evaluating a new feature request for TajsOS, use this Skill to assess if the feature aligns with shared life-object flows and does not introduce unnecessary complexity.

Quick Start

Use the tajsos-product-ux skill to evaluate the proposed new calendar integration feature for alignment with TajsOS's core product and UX principles.

Frequently Asked Questions about tajsos-product-ux

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

FAQPage Schema
How do I maintain UX coherence across multiple LifeOS application screens?

Maintain UX coherence by enforcing consistent interaction patterns, theme usage, and naming conventions across all LifeOS application surfaces. This prevents disjointed UX choices and ensures a cohesive product architecture throughout development and design workflows.

How do I evaluate new feature requests against core product framing principles?

Evaluate new feature requests by assessing their alignment with LifeOS-first positioning and shared life-object flows. This product framing guidance prevents generic second-brain app drift and ensures features support a clear, cohesive product identity without unnecessary complexity.

What is the best way to prioritize MVP features for a LifeOS application?

Prioritize MVP features by keeping the scope centered on core life objects like dashboards, notes, and tasks. This feature prioritization approach avoids feature sprawl and prevents the creation of isolated functionality silos within the application.

Why does naming drift break LifeOS-first product architecture?

Naming drift breaks LifeOS-first product architecture by introducing inconsistent product framing and disjointed UX choices. Enforcing strict naming conventions preserves a cohesive product identity and maintains aligned feature scope across the entire application.

Can I use product management principles to prevent feature sprawl in a second-brain app?

Apply product management principles to prevent feature sprawl by enforcing core experience principles during feature prioritization. This keeps the MVP scope focused on core life objects and ensures new functionality integrates with existing shared flows.

When should I not add a new calendar integration to my LifeOS application?

Avoid adding a new calendar integration if the feature introduces unnecessary complexity or fails to align with shared life-object flows. Features must be evaluated against core UX coherence and LifeOS-first principles to prevent isolated functionality silos.