github.com/Eastcoast-Laboratories/Roboyard (link)

commit signals (34)

source signals (8)

• AGENTS.mdvia agents-md

  # Roboyard — Agent Rules
  
  ## Project Shape
  
  - Kotlin Multiplatform project with modules `app` (Android), `shared`, `composeApp` (Compose Multiplatform UI: Desktop/iOS) and `composeAndroidApp` (APK wrapper hosting the Compose UI).
  - The `app` module is the actively developed Android app and the reference implementation — never call it "legacy".
  - Goal: the app must run on Android, iOS, and Desktop. Keep changes platform-independent or resolve platform differences with `expect`/`actual`.
  - The solver code

• .github/copilot-instructions.mdvia github-copilot

  # Roboyard - Android Puzzle Game
  Roboyard is an Android puzzle game inspired by "Ricochet Robots" written in Java. Players control four robots in a maze to guide them to targets. The game features an AI solver, 140 levels, and supports 6 languages.
  
  Always reference these instructions first and fallback to search or bash commands only when you encounter unexpected information that does not match the info here.
  
  ## Working Effectively
  
  ### Critical Build Limitations
  - **NETWORK DEPENDENCY**: Build requires i

• .devin/skills/deploy/SKILL.mdvia unspecified

  ---
  name: deploy
  description: Deployment recipe for the roboyard.z11.de / caveshuttle.z11.de community site
  triggers:
    - user
  ---
  
  # Deploying the Community Site
  
  The production community site is **not** managed by git on the server. It is uploaded with rsync via the deploy-watch script.
  
  - Deploy script: `/var/www/roboyard.z11/deploy-watch.sh`
  - Remote host: `eclabs-vm06`
  - Remote path: `/var/kunden/webs/z11/roboyard.z11.de`
  - The same site also serves `caveshuttle.z11.de` with different deploy paths — 

• .devin/skills/espresso-testing/SKILL.mdvia unspecified

  ---
  name: espresso-testing
  description: Rules and helpers for writing Espresso UI tests in the Roboyard project
  ---
  
  # Espresso Testing in Roboyard
  
  Before writing any new Espresso test, read and analyze `app/src/androidTest/java/roboyard/eclabs/ui/TestHelper.java` to see which reusable methods already exist. Never reinvent existing functionality.
  
  ## Rules
  
  - Always use `TestHelper` static methods in new tests instead of writing inline interactions.
  - For all settings-related UI interactions, create reusab

• .windsurfrulesvia devin

• .devindirectoryvia devin
• .devindirectoryvia devin
• .devindirectoryvia devin

ignorefile signals (0)

none