Skip to main content

Contribution Guide

Where to contribute​

  • use lucky-plan-fe for current product frontend changes
  • use lucky-plan-be for current product backend changes
  • use the beta monorepo for docs-site and newer infrastructure changes

Contribution expectations​

  • keep docs factual
  • separate simulation language from live trading language
  • avoid guaranteed-profit claims
  • update documentation when architecture, config, or workflow changes
  • prefer small, verifiable changes in execution-critical paths

Good first checks​

  • identify which repo actually owns the behavior
  • inspect existing module or adapter patterns before editing
  • confirm whether a contract, platform, or schema change affects historical correctness