Appearance
Agents, Skills & Memory
Skills are domain knowledge modules that Alex loads on demand. Some examples:
- code-review: systematic review for correctness, security, and growth
- testing-strategies: the right test at the right level
- debugging-patterns: reproduce, isolate, hypothesize, fix
- security-review: OWASP Top 10, STRIDE, dependency audit
- api-design: APIs developers love to use
- database-design: schema design, normalization, query optimization
- infrastructure-as-code: Bicep, Terraform, ARM templates
- creative-writing: fiction, narrative structure, character development
- academic-research: thesis writing, literature reviews, scholarly work
- career-development: resumes, interviews, professional growth
- ui-ux-design: accessibility, design systems, user experience
- image-handling: AI image generation via Replicate
- gamma-presentations: slide decks from markdown via the Gamma API
There are over 120 skills spanning software engineering, research, writing, design, business, and more.
Agents. Specialized Modes
Agents are personas that Alex can switch into for specialized work:
| Agent | Purpose |
|---|---|
| Builder | Implementation with optimistic problem-solving |
| Researcher | Deep domain research and knowledge discovery |
| Validator | Adversarial QA with skeptical analysis |
| Documentarian | Documentation accuracy and drift prevention |
| Azure | Azure development guidance with MCP tools |
| M365 | Microsoft 365 and Teams development |
You can invoke them directly: "@Alex /builder build the API endpoint" or Alex routes to the right agent automatically based on your request.
Muscles. Automation
Muscles are Node.js scripts that Alex can run from conversation. Examples:
- md-to-word: convert markdown to professional Word documents
- generate-banner: create project banners via AI image generation
- build-pdf: compile markdown into print-ready PDFs
- sync-to-heir: synchronize architecture files across repositories
Instead of "here's how to do it," Alex just does it.
Memory. Continuity
Alex remembers across sessions through three memory layers:
- User memory: your preferences, patterns, and insights (persists everywhere)
- Session memory: task-specific context for the current conversation
- Repository memory: codebase conventions and verified practices
This means Alex knows your coding style, your project's architecture decisions, and what you worked on last time: without you re-explaining.