Custom Agents & Rules

Create project-specific AI agents with custom rules, LURUS.md configuration, and persistent memory. Teach the AI your conventions once — it remembers forever.

🤖

Custom Agents (.lurus/agents/)

Project-local agent profiles, roles, system hints, and specializations.

📋

Project Rules (/rules)

Maintain rules via command, consistent standards across repos and teams.

📖

LURUS.md (global+project)

Global and project instructions, the AI learns your context first.

🚀

Project Init (/init)

Scaffold structure and defaults in one step, productive faster.

🧠

SaveMemory (persistent facts)

Remember key facts across sessions, less repetition, more continuity.

🔒

Permission Modes (4 modes)

Four modes to balance tool access and risk, from strict to fluid.

LURUS.md – Project Configuration

Place a LURUS.md file in your project root. The AI reads it at the start of every session and applies your conventions, architecture notes, and preferences automatically.

LURUS.md

# My Project

## Architecture
Monorepo: NestJS backend + Angular frontend. Shared types in /libs.

## Conventions
- TypeScript strict mode everywhere
- All services use dependency injection (NestJS @Injectable)
- Tests live in *.spec.ts next to the source file
- Commits follow Conventional Commits spec

## Build
npm run build # builds all packages
npm test      # runs all tests

Rules System

Rules are Markdown files in .lurus/rules/. Each rule has frontmatter to control when it applies — always, on specific file patterns, or only when activated.

.lurus/rules/security.md

---
description: "Security review rule"
alwaysApply: true
priority: 10
---

# Security Review
Always check for:
- Hardcoded secrets or API keys
- Missing input validation on user data
- SQL queries without parameterization

Custom Commands

Save frequently used prompts as custom commands in .lurus/commands/. Invoke them with /deploy, /audit, or any name you choose.

.lurus/commands/deploy.md

# .lurus/commands/deploy.md

Run the deployment checklist:
1. Run all tests and confirm they pass
2. Build for production
3. Check for any uncommitted changes
4. Create a git tag for this release
5. Generate changelog entry

Ready to code smarter?

Join the waitlist and set up agents, rules, and LURUS.md for your team.

Get started