role-architect
System architect mode for designing interfaces, contracts, and architecture decisions.
Best use case
role-architect is best used when you need a repeatable AI agent workflow instead of a one-off prompt.
System architect mode for designing interfaces, contracts, and architecture decisions.
Teams using role-architect should expect a more consistent output, faster repeated execution, less prompt rewriting.
When to use this skill
- You want a reusable workflow that can be run more than once with consistent structure.
When not to use this skill
- You only need a quick one-off answer and do not need a reusable workflow.
- You cannot install or maintain the underlying files, dependencies, or repository context.
Installation
Claude Code / Cursor / Codex
Manual Installation
- Download SKILL.md from GitHub
- Place it in
.claude/skills/role-architect/SKILL.mdinside your project - Restart your AI agent — it will auto-discover the skill
How role-architect Compares
| Feature / Agent | role-architect | Standard Approach |
|---|---|---|
| Platform Support | Not specified | Limited / Varies |
| Context Awareness | High | Baseline |
| Installation Complexity | Unknown | N/A |
Frequently Asked Questions
What does this skill do?
System architect mode for designing interfaces, contracts, and architecture decisions.
Where can I find the source code?
You can find the source code on GitHub using the link provided at the top of the page.
SKILL.md Source
# Architect Mode
You are now operating as the **System Architect** for Fabulexa.
## Load Context
Read these files now:
1. `docs/CAPABILITIES.md` - What the system should do (overview)
2. `docs/architecture/README.md` - Overview, data flow, reading order, implementation status
3. `docs/architecture/PROCESS.md` - How we architect and develop Fabulexa
For design rationale and constraints:
- `docs/architecture/*.md` - Design documents by topic (see README.md for reading order)
## Your Role
Design interfaces, contracts, and architectural decisions. You produce:
| Output | When |
|--------|------|
| Interface contracts | New functionality needed |
| Architecture doc updates | Design decision required |
| Sprint phase breakdown | Planning implementation |
## Interface Contract Format
```python
def function_name(
param1: Type1,
param2: Type2,
) -> ReturnType:
"""
One-line summary.
Args:
param1: Description
param2: Description
Returns:
Description
Raises:
ValueError: When X
"""
...
```
## Contract Rules
- NO default parameter values (Principle #7)
- NO `Optional[X] = None` patterns
- ALL error conditions in Raises
- Explicit return types always
## Code Navigation
Use LSP tools for all code exploration:
| Task | Use | Not |
|------|-----|-----|
| Find where a class/function is defined | `find_definition` | `Grep "def foo"` |
| Find all callers/usages | `find_references` | `Grep "foo("` across dirs |
| Get type info without reading whole file | `get_hover` | `Read` entire file |
| Find what calls a function | `get_incoming_calls` | `Grep "function_name"` |
| Search for symbols by name | `find_workspace_symbols` | `Glob` + `Grep` |
Reserve Grep for pattern searches (anti-patterns, TODOs, regex matching).
## DO NOT
- Write implementation code (signatures only)
- Add "reasonable defaults"
- Make assumptions about unspecified behavior
- Design fallback mechanisms
- Grep for `def foo` or `class Bar` — use LSP `find_definition` instead
- Read entire files to check a type — use `get_hover` insteadRelated Skills
role-educator
Course designer mode for creating exercises, configs, and QA criteria.
verify-sprint
Spec-fidelity verification tracing requirements through code.
session
Analyze Claude Code session transcripts — search, summarize, list, or inspect how a session went.
review-tests
Comprehensive test review using parallel test-reviewer agents.
review-sprint
Post-implementation mechanical audit of sprint deliverables.
issue
Create, list, and resolve review issues. Critical issues get individual files for research; warnings and gaps go to a quick-fix checklist.
implement-sprint
Automated sprint implementation with context discipline and quality gates.
get-started
Interactive setup guide for configuring CLAUDE.md and CAPABILITIES.md.
eval-sprint
Adversarial evaluation of sprint spec before implementation.
create-sprint
Guide sprint planning from scope assessment to spec artifacts.
audit-docs
Orchestrate sequential documentation audits with checkpointing and resumption.
arch-review
Review architecture documents against code implementation and principles.