Quick Start

Two short paths, four steps each. Pick the one that fits and follow the links for the full details.

You'll need an account

Both paths start with a Code SCE account — sign in with Google or GitHub. First-time users complete a quick onboarding step to set up a unique developer handle and profile.

For Buyers

Buy, customize, and integrate your first module.

Sign in→Find→Buy→Download

1. Sign in & Onboard. Choose Continue with Google or Continue with GitHub. Complete the quick onboarding to claim your username. → Getting Started
2. Find a module. Browse the marketplace, filter by category or search, and open a module to inspect its visual proofs & screenshot gallery, technical README, and configurable options. → Explore Modules
3. Buy. Click Buy, pay with crypto on the hosted invoice (any supported coin; we settle in USDT BEP-20), and wait for on-chain verification — then Buy turns into Download. → How Buying Works
4. Download, configure & message. Grab your watermarked ZIP through a secure link, configure variables via the dynamic form, integrate per the README, or reach out to the author via Messages. → Using a Module · Messages & Chat

Prefer a native companion?

Use the desktop app for a focused, project-oriented workflow — same account, same catalog as the web app.

For Authors

Publish your first module with zero source exposure.

Prepare→Upload→Configure→Publish

1. Prepare your proofs & docs. Capture visual previews (up to 5 UI screenshots, GIFs, or image proofs) and write a comprehensive README.md detailing module architecture and integration instructions. Optionally include an extra standalone HTML demo for sandboxed interactivity. → Create a Module
2. Upload. In Studio, submit your visual proofs, documentation, and metadata — name, category, short description, and price. Your upload is scanned automatically (content checks, policy rules, and image moderation) before anything is stored. → Studio Workflow · Security Scanning
3. Configure. Define your module's config variables (the config_schema) so buyers can customize it through a form instead of editing code. → Dynamic Configuration
4. Publish. Hit Save & Finish. On a clean review it goes live; a borderline result is held as a draft for manual review, and a rejection comes with a reason to fix and re-upload. → Publish a Module · Monetization

Where to go next

• For Buyers → — the complete buyer guide.
• Messages & Chat → — direct developer messaging and collaboration.
• For Authors → — the complete author guide.
• Security → — how your work and purchases are protected.
• Architecture → — how the whole system fits together.