No description
Find a file
Ash c2b8449ad7 feat: add event modeling methodology skill, expand EMFlow CLI skill
Skills:
- event-modeling: complete methodology guide — 4 patterns (state-change, state-view,
  automation, translation), 7 workshop steps, specification formats (Given/When/Then,
  Given/Then), spec-to-code translation, quality checklist, common mistakes
- emflow-cli: expanded with full REST API reference, auth setup, EM container
  operations, step-by-step model creation guide, AI agent workflow pattern
2026-02-26 11:58:37 +00:00
claude-code feat: add event modeling methodology skill, expand EMFlow CLI skill 2026-02-26 11:58:37 +00:00
docs feat: initial AI agent configurations for Claude Code and OpenCode 2026-02-16 23:58:04 +00:00
opencode feat: initial AI agent configurations for Claude Code and OpenCode 2026-02-16 23:58:04 +00:00
.gitignore feat: initial AI agent configurations for Claude Code and OpenCode 2026-02-16 23:58:04 +00:00
README.md feat: add event modeling methodology skill, expand EMFlow CLI skill 2026-02-26 11:58:37 +00:00

AI Agents

Reusable agent configurations, skills, and commands for AI-assisted development.

Built around eskit (event sourcing toolkit for Go), screaming architecture, and TigerStyle safety.

Philosophy

  • No quick fixes — every piece of code gets proper validation, error handling, and testing
  • No aggregates — deciders with DCB pattern only
  • Issue-driven — every task gets a git issue before work starts
  • Nothing is done unless it's on main — commits are the source of truth
  • Docs ship with code — every API change updates docs in the same commit

Structure

ai-agents/
├── claude-code/
│   ├── agents/               # Specialized agent definitions
│   │   ├── backend-architect.md    # Backend implementation
│   │   ├── frontend-developer.md   # UI implementation
│   │   ├── code-reviewer.md        # Code review
│   │   ├── test-writer-fixer.md    # Testing
│   │   ├── sprint-prioritizer.md   # Planning
│   │   ├── eskit-migrator.md       # Migration to eskit
│   │   └── domain-modeler.md       # Event model design
│   ├── skills/               # Auto-injected context
│   │   ├── event-modeling/   # Event modeling METHODOLOGY (4 patterns, 7 steps, specs)
│   │   ├── eskit-core/       # eskit API reference (commands, deciders, stores, projections)
│   │   ├── eskit-architecture/  # Screaming architecture patterns and templates
│   │   ├── emflow-cli/       # EMFlow CLI + REST API for event model management
│   │   ├── go-safety/        # TigerStyle Go safety standards
│   │   └── code-review/      # Code review checklist
│   └── commands/             # Slash commands
│       ├── team-feature.md       # Spawn coordinated dev team
│       ├── migrate-to-eskit.md   # Analyze + plan eskit migration
│       ├── new-context.md        # Scaffold bounded context
│       └── new-slice.md          # Create vertical slice
├── opencode/                 # OpenCode configurations (planned)
└── docs/                     # Setup guides

Quick Start

For a new eskit project

# Copy skills into your project
cp -r claude-code/skills/* /path/to/project/.claude/skills/

# Copy agents
cp claude-code/agents/*.md /path/to/project/.claude/agents/

# Copy commands
cp claude-code/commands/*.md /path/to/project/.claude/commands/

For migrating an existing app

  1. Copy all skills + agents + commands into the project
  2. Run /migrate-to-eskit <description of the app>
  3. The agent analyzes the codebase, maps contexts, produces a phased plan
  4. Use /new-context and /new-slice to scaffold each piece

For building from an event model

  1. Design your event model in EMFlow (emflow.tempr.dev)
  2. Use the domain-modeler agent to validate and refine
  3. Use /new-context for each bounded context identified
  4. Use /new-slice for each vertical slice

Stack

Layer Technology
Language Go
Templates Templ (type-safe, compiles to Go)
Frontend Datastar (SSE-driven, 11KB, no custom JS)
CSS Open Props (design tokens, NOT Tailwind)
Event Store eskit (SQLite/Postgres/NATS backends)
Database SQLite (WAL mode) for single-instance
Router Chi
Deployment Single binary, systemd + Caddy

Key Resources