ElixirScope Development

Development guidelines for ElixirScope, an AI-Powered Execution Cinema Debugger for Elixir/BEAM applications.

What This Skill Does

This skill configures your AI assistant to follow best practices when working with the ElixirScope codebase, including proper testing strategies, code mapping awareness, and mix command usage.

Instructions

When working with the ElixirScope codebase, follow these guidelines:

Testing Strategy

1. **Default to fast tests**: Use `mix test.trace` by default for development and testing workflows

- This command bypasses slow live LLM API tests

- Suitable for most development iterations

2. **Use targeted LLM tests only when needed**: Run `mix test.all` or `mix test.live` only when:

- Specifically testing LLM integrations

- Verifying API connectivity

- Debugging LLM-related functionality

3. **Understand the test suite structure**:

- `mix test.trace` - Fast tests excluding LLM API calls

- `mix test.live` - LLM integration tests only

- `mix test.all` - Complete test suite including LLM tests

Code Organization

1. **Reference code mapping**: Consult `CURSOR_CODE_MAPPING.md` for:

- Module organization

- File structure

- Component relationships

- Architecture overview

2. **Follow implementation guide**: Check `CURSOR_IMPLEMENTATION_GUIDE.md` for:

- Development workflows

- Implementation patterns

- Best practices

- Common tasks

Mix Commands

1. **Use clean output**: Prefer `mixsw` alias over `mix` to:

- Suppress warnings

- Show only errors

- Keep output focused and readable

2. **When to use standard mix**:

- When warnings are specifically needed

- When debugging warning-related issues

- When full compiler output is required

Date Context

Usage Examples

Running tests during development

```bash

Default for most development work

mix test.trace

When testing LLM features specifically

mix test.live

Full suite before commits

mix test.all

```

Using clean mix output

```bash

Clean output for normal operations

mixsw compile

mixsw deps.get

Standard mix when warnings needed

mix compile --warnings-as-errors

```

Navigating the codebase

1. Open `CURSOR_CODE_MAPPING.md` to understand module structure

2. Consult `CURSOR_IMPLEMENTATION_GUIDE.md` for implementation details

3. Follow established patterns in existing modules

Constraints