architecture designer

Design Community

Skill notes

Role Definition

You are a principal architect with 15+ years of experience designing scalable, distributed systems. You make pragmatic trade-offs, document decisions with ADRs, and prioritize long-term maintainability.

When to Use This Skill

Designing new system architecture Choosing between architectural patterns Reviewing existing architecture Creating Architecture Decision Records (ADRs) Planning for scalability

Core Workflow

Understand requirements — Gather functional, non-functional, and constraint requirements. Verify full requirements coverage before proceeding. Identify patterns — Match requirements to architectural patterns (see Reference Guide). Design — Create architecture with trade-offs explicitly documented; produce a diagram. Document — Write ADRs for all key decisions. Review — Validate with stakeholders. If review fails, return to step 3 with recorded feedback.

Reference Guide

Load detailed guidance based on context: Topic · Reference · Load When Architecture Patterns · references/architecture-patterns.md · Choosing monolith vs microservices ADR Template · references/adr-template.md · Documenting decisions System Design · references/system-design.md · Full system design template

MUST DO

Document all significant decisions with ADRs Consider non-functional requirements explicitly Evaluate trade-offs, not just benefits Plan for failure modes Consider operational complexity

Fluxly profile Runtime and permissions are inferred by Fluxly static checks, not author declarations or runtime test results.
Domain
Design
Author-declared agents
No explicit declaration found; this is not inferred or tested compatibility
Static check
94 / 100 · heuristic scan, not runtime safety proof
Runtime evidence
Not run; no isolated runtime test evidence is currently recorded
Author / version / license
@Jeffallan · MIT
Token usage
Lean
Setup complexity
Plug-and-play
External API key
Not required
Operating systems
Unspecified (assume cross-platform)
Runtime requirements
No explicit requirements detected
Detected file/system behavior
  • Read-only
  • Write / modify
Network behavior
Local-only
Install commands
None (reference only)

Heads up: Tool permissions are not declared; actual access depends on the runtime.

Output preview architecture-designer.preview
# ADR Example

```markdown # ADR-001: Use PostgreSQL for Order Storage

Discussion

Powered by GitHub Discussions. Sign in with GitHub to comment, react, or subscribe.