agentleFS
lbednerlbedner/aegis-stack/llms.txt

aegis-stack

llms.txt144 starsChanged 15 months agoMITView on GitHub

Aegis Stack is a CLI-driven framework for creating production-ready Python applications with composable components. Build exactly what you need by selecting components during project creation: - Core (always included): FastAPI backend + Flet frontend + CLI management - Scheduler: APScheduler for background tasks and cron jobs (available) - Database: PostgreSQL + SQLAlchemy + Alembic (coming soon) - Cache: Redis caching and sessions (coming soon) Three pillars: 1. Speed: CLI-driven generation, async-first, minimal setup 2. Simplicity: Clear patterns, explicit dependencies, no…

  • Reads credentials
  • Installs packages

We split this llms.txt into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Scalable: Start simple, scale to distributed systems

    line 41

≈ “Common” is an estimate: at least 1 in 5 of the 3,225 llms.txt files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
llms.txt
# Aegis Stack

Aegis Stack is a CLI-driven framework for creating production-ready Python applications with composable components.

## Core Concept

Build exactly what you need by selecting components during project creation:
- **Core (always included)**: FastAPI backend + Flet frontend + CLI management
- **Scheduler**: APScheduler for background tasks and cron jobs (available)
- **Database**: PostgreSQL + SQLAlchemy + Alembic (coming soon)
- **Cache**: Redis caching and sessions (coming soon)

## Key Commands

```bash
# Install
pip install aegis-stack

# Create simple API
aegis init my-api

# Create with background processing
aegis init task-processor --components scheduler

# Create with all components (future)
aegis init webapp --components scheduler,database,cache

# Project status
aegis status

# CLI help
aegis --help
```

## Architecture

- **Async-first**: Built with asyncio for high-concurrency
- **Component-based**: Select only needed capabilities
- **Container-native**: Each component runs in separate Docker containers
- **Explicit integration**: Services in `app/services/`, import where needed
- **Scalable**: Start simple, scale to distributed systems

## Generated Project Structure

```
project/
├── app/
│   ├── components/          # Capabilities (backend, frontend, scheduler)
│   ├── services/           # Business logic (explicit imports)
│   ├── core/              # Framework utilities
│   └── integrations/      # App composition
├── tests/                 # Test suite
├── pyproject.toml         # Dependencies based on selected components
├── Dockerfile             # Container definition
└── docker-compose.yml     # Multi-service orchestration
```

## Development Workflow

```bash
cd my-project
uv sync                    # Install dependencies
cp .env.example .env       # Configure environment
make serve             # Start development server (Docker)
make run-dev               # Start without Docker
make test                  # Run test suite
make check                 # Lint + typecheck + test
```

## Key Features

- **Health dashboard**: Built-in Flet frontend with real-time monitoring
- **Structured logging**: Production-ready with structlog
- **Type safety**: Full mypy support
- **Quality checks**: Ruff linting, mypy type checking, pytest
- **Documentation**: Auto-generated with MkDocs

## Philosophy

Three pillars:
1. **Speed**: CLI-driven generation, async-first, minimal setup
2. **Simplicity**: Clear patterns, explicit dependencies, no magic
3. **Scalability**: Container-native, component separation, evolution path

## Technology Stack

- **Backend**: FastAPI (async web framework)
- **Frontend**: Flet (Python-native cross-platform UI)
- **CLI**: Typer (command-line interface)
- **Dependencies**: UV (fast Python package manager)
- **Scheduling**: APScheduler (background tasks)
- **Testing**: pytest with async support
- **Linting**: Ruff (fast Python linter)
- **Type checking**: mypy (static type checker)

## Links

- Documentation: https://github.com/lbedner/aegis-stack/docs
- Repository: https://github.com/lbedner/aegis-stack
- CLI Reference: docs/cli-reference.md
- Component Guide: docs/components/index.md
- Philosophy: docs/philosophy.md

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.