Dashboard

Reminder checklistDon’t panic, just small reminders to help you avoid missing anything

• Gameplay & physics

  • Build core gameplay for all N+1 ideasInclude working win or game-over screens, 1 level and simple 2D graphics are enough
  • Cover all five physics features across the gamesUse each at least once, CharacterController, Rigidbody or Rigidbody2D, AddForce or AddTorque, Raycast or SphereCast, Collision or Collision2D and the collided object’s properties

• Project architecture

  • Plan and document the architecture in the READMEInclude run instructions, a class diagram with event senders and listeners, 2–3 choices with alternatives and reasons, which files change for a new enemy or item, and reasons for any singleton or static variable
  • Keep code organized, reusable and configurableUse folders by responsibility, small focused components and clear names, keep tuning values in Inspector fields or ScriptableObjects with no magic numbers
  • Connect gameplay and UI through eventsUse at least 1 event to update UI, keep gameplay independent of UI and unsubscribe in OnDisable for each OnEnable subscription

• Review & publishing

  • Review changes and get a green linter ✓Have another teammate approve major pull requests, ask AI to compare code with the diagram and log differences and reasons, push each project with unchanged linter.yml in .github/workflows/
    Setup instructions
  • Publish and test every Web build on itch.ioAdd playing instructions and working links in both directions between each GitHub repository and its itch.io page