Kksrules

• Any new feature must conceptually represent karyana store operations, such as:

  • Grocery items (rice, flour, oil, pulses, snacks, beverages, etc.)
  • Inventory and stock levels
  • Supplier purchases
  • Retail pricing and discounts
  • Daily sales and customer orders

• Even if a UI element visually looks like it belongs to a mattress website, it must be mapped logically to a karyana store concept.

Content Mapping Rule

• Visual elements remain unchanged.
• Only the meaning and text of the content adapts to the karyana store domain.

Scope

This rule applies to:

• Frontend text and content
• Backend logic and APIs
• Database schema
• Documentation and examples

Any implementation that changes the UI design or introduces non-karyana business logic is considered incorrect.