> ## Documentation Index
> Fetch the complete documentation index at: https://docs.lunarmc.ai/llms.txt
> Use this file to discover all available pages before exploring further.

# AI-Assisted Development

> Using AI coding assistants effectively at LayerFive

## Overview

We use AI coding assistants (Claude Code, GitHub Copilot) to develop faster. This guide covers the basics.

## Quick Start

### Simple Rules

1. **Give credit** - Add co-author to commits with AI code
2. **Be transparent** - Note what AI generated in PRs
3. **Review everything** - You own the code
4. **Use common sense** - Be careful with auth, payments, sensitive data

## Co-Author Attribution

When AI helps write code, add this to your commit:

```bash theme={null}
git commit -m "feat: Add customer export API

Made with Claude

Co-Authored-By: Claude <noreply@anthropic.com>"
```

**Why**: Tracks AI usage in Swarmia.

## PR Template

Include a simple AI section in your PRs:

```markdown theme={null}
## AI Assistance
Used Claude to generate:
- Customer export models and serializers
- Basic tests

Manually added:
- Permission logic
- Complex validation
```

See the full [PR template](https://github.com/Lunar-Mission-Control/ai-development/blob/main/docs/PR-TEMPLATE.md).

## When to Be Careful

**Think twice before using AI for**:

* Authentication/authorization
* Payment processing
* PII/customer data handling
* Production infrastructure

When in doubt, ask a senior developer.

## Guidelines

<AccordionGroup>
  <Accordion title="Security Checklist">
    Always check AI-generated code for:

    * Hard-coded secrets
    * Proper input validation
    * SQL injection prevention
    * Authentication checks
  </Accordion>

  <Accordion title="Code Review Standards">
    You own all code you commit:

    * Read through AI-generated code
    * Understand what it does
    * Test it thoroughly
    * Make sure it follows our patterns
  </Accordion>

  <Accordion title="What AI is Good At">
    Use AI to accelerate:

    * Boilerplate code (models, serializers)
    * Standard CRUD operations
    * Unit tests
    * Documentation
    * Common patterns
  </Accordion>
</AccordionGroup>

## Resources

<CardGroup cols={2}>
  <Card title="Best Practices" icon="shield-check" href="/mission-control/ai-best-practices">
    Code quality and security guidelines
  </Card>

  <Card title="Workflow Guide" icon="diagram-project" href="/mission-control/ai-workflow">
    Daily development workflow with AI
  </Card>

  <Card title="Prompt Templates" icon="wand-magic-sparkles" href="/mission-control/ai-prompts">
    Copy-paste prompts for common tasks
  </Card>

  <Card title="AI Development Repo" icon="github" href="https://github.com/Lunar-Mission-Control/ai-development">
    Agent files and detailed docs
  </Card>
</CardGroup>

## Agent Files

Role-specific AI agent configurations:

* **[Backend Agent](https://github.com/Lunar-Mission-Control/ai-development/blob/main/agents/backend-agent.md)** - Django development
* **[Frontend Agent](https://github.com/Lunar-Mission-Control/ai-development/blob/main/agents/frontend-agent.md)** - Angular development
* **[Debugging Agent](https://github.com/Lunar-Mission-Control/ai-development/blob/main/agents/debugging-agent.md)** - Troubleshooting
* **[Testing Agent](https://github.com/Lunar-Mission-Control/ai-development/blob/main/agents/testing-agent.md)** - Writing tests

## Getting Help

* **Questions?** Ask in team chat
* **Unsure?** Talk to a senior developer
* **Issues?** Create an issue in the [AI development repo](https://github.com/Lunar-Mission-Control/ai-development)

***

**Remember**: We're learning together. Start simple, be transparent, and we'll refine our approach as we go.