Futures
Access hundreds of perpetual contracts
TradFi
Gold
One platform for global traditional assets
Options
Hot
Trade European-style vanilla options
Unified Account
Maximize your capital efficiency
Demo Trading
Introduction to Futures Trading
Learn the basics of futures trading
Futures Events
Join events to earn rewards
Demo Trading
Use virtual funds to practice risk-free trading
Launch
CandyDrop
Collect candies to earn airdrops
Launchpool
Quick staking, earn potential new tokens
HODLer Airdrop
Hold GT and get massive airdrops for free
Launchpad
Be early to the next big token project
Alpha Points
Trade on-chain assets and earn airdrops
Futures Points
Earn futures points and claim airdrop rewards
More
YC CEO Garry Tan open-sourced his Claude Code workflow, hitting 4K+ stars on GitHub in 24 hours.
8 slash commands, each corresponding to a specific role: CEO reviews product direction, Engineering Manager reviews architecture, Staff Engineer identifies production incidents, Release Manager handles one-click deployment, QA auto-captures screenshots to test bugs.
The core idea in one sentence: don't treat AI as an all-purpose assistant—assign it specific roles.
What hits hardest is /plan-ceo-review. You say "add image upload," and it doesn't rush to write code. Instead, it asks back: is this really what you need? Maybe the actual requirement is helping sellers auto-generate product descriptions that actually sell. It pulls "how to do it" back to "what to do."
/review is brutal too—it actively anticipates production disasters: N+1 queries? Race conditions? Failed uploads leaving orphaned files? Think through all the pitfalls before bugs blow up production.
The underlying logic: mixing AI use cases is inferior to specializing each one.