Prologinator Aider Configuration

This skill configures Aider for the Prologinator project, a Prolog-based game engine. It sets up file context management, disables auto-commits, and configures the development workflow.

What This Skill Does

Instructions

When a user wants to set up Aider for a Prologinator-style Prolog project:

1. **Create the base configuration file** at `.aider.conf.yml` with these key settings:

```yaml

Core editable files

file:

- justfile

- prolog/game.pl

- prolog/perf.pl

- prolog/actions/load.pl

Git settings - disable auto-commit and gitignore management

auto-commits: false

gitignore: false

Keep defaults for other settings

auto-lint: true

auto-test: false

```

2. **Explain the configuration sections**:

- `file:` — Files added as editable context (consumes tokens, use sparingly)

- `read:` — Files added as read-only context (for reference, lower token cost)

- `auto-commits: false` — Prevents automatic git commits, allows manual control

- `gitignore: false` — Prevents Aider from modifying .gitignore

3. **Recommend file organization patterns**:

- Keep core game logic files (`game.pl`, `perf.pl`) in editable context

- Add action modules selectively based on current work

- Use read-only context for documentation and reference files

- Comment out unused files to reduce token consumption

4. **Optional customizations** the user may want:

```yaml

Add lint command for Prolog (if using a linter)

lint-cmd:

- "prolog: swipl -g 'check_syntax' -t halt"

Add test command

test-cmd: "just test"

Enable dark mode

dark-mode: true

Set custom colors

user-input-color: "#00cc00"

assistant-output-color: "#0088ff"

```

5. **Usage guidance**:

- Start Aider: `aider` (uses .aider.conf.yml automatically)

- The justfile and key Prolog files will be in context

- Manually commit changes when ready: `/commit` or use git directly

- Add more files during session: `/add prolog/actions/spawn.pl`

- Add read-only files: `/read aider/QUICK_REFERENCE.md`

6. **Best practices for Prolog projects**:

- Keep module files separate for better organization

- Use read-only context for game definitions and input files

- Only add action modules you're actively working on

- Comment out large documentation files when not needed

- Use justfile for common build/test/run commands

Example Workflow

```bash

1. Create .aider.conf.yml with the configuration

2. Start aider

aider

3. In Aider session - files are already loaded

/add prolog/actions/spawn.pl # Add specific action module

/read games/game1/game.pl # Add game definition as reference

4. Make changes, then manually commit

/commit "Add enemy spawning logic"

```

Constraints

Notes