diff --git a/Must-Good-Must Not b/Must-Good-Must Not
index 0fcb1f9..4c35ecf 100644
--- a/Must-Good-Must Not	
+++ b/Must-Good-Must Not	
@@ -1,22 +1,62 @@
-Tapp to build
+# Tapp Building Requirements
 
-Must:
-1. It's designed to be used on Twitter. User A can create a TLink of the Tapp to share on Twitter for other users (like User B) to use.
-2. It provides motivation for both User A and User B.
-3. Less than 3 pages UX for each feature (the page shows in tweet feed, a confirmation checking page after user click a button in tweet feed, a result page after transection is done)
+## Essential Requirements
 
+### Twitter Integration & Social Sharing
+- Must be designed for Twitter usage
+- User A should be able to create and share a Tlink of the tapp on Twitter for User B to access
+- Simple integration with Twitter's feed display format
 
-Good to Have:
-1. It's built for existing tokens/NFTs, allowing for easy branding.
-2. It can be built quickly (delivery in 0.5 day) using existing contracts and backend.
-3. It has the potential to go viral.
-4. It only requires the TokenScript file, with no additional development needed.
-5. Social sharing buttons to make it easier for User A to share their TLink on Twitter and other platforms.
+### User Incentives
+- Must provide clear motivations for both:
+  - User A (the sharer)
+  - User B (the recipient/user)
 
+### Streamlined UX
+Maximum of 3 pages per feature:
+1. Initial view in tweet feed
+2. Confirmation page after tweet feed button click
+3. Result page after transaction completion
 
-Must Not:
-1. More than 3 buttons(cards) in tweet feed.
-2. More than 3 days to build.
+## Preferred Features
 
+### Existing Token Integration
+- Built for existing tokens/NFTs
+- Leverage established branding
+- Utilize existing community
 
+### Rapid Development
+- Development time: 0.5 day target
+- Use existing contracts where possible
+- Utilize existing backend infrastructure
 
+### Viral Potential
+- Design for shareability
+- Include compelling social elements
+- Create engaging user interactions
+
+### Technical Simplicity
+- Require only TokenScript file
+- No additional development needed
+- Leverage existing infrastructure
+
+### Social Sharing Enhancement
+- Include easy-to-use sharing buttons
+- Support multiple social platforms
+- Optimize for Twitter sharing
+
+## Restrictions
+
+### UI Limitations
+- Maximum 3 buttons/cards in tweet feed
+- Keep interface clean and focused
+- Maintain simplicity in user interactions
+
+### Development Timeline
+- Must not exceed 3 days total development time
+- Include testing and deployment
+- Ready for production use quickly
+
+---
+
+*Note: This document serves as a guideline for building effective tapps that prioritize user engagement, rapid deployment, and social sharing capabilities.*