design

Analyze codebases and documentation to produce evidence-based design recommendations.

3|2|Updated Apr 3, 2026
One-click install
npx skills add https://github.com/fluxforgeai/ARTEMIS --skill design-fluxforgeai
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: design
Source: https://github.com/fluxforgeai/ARTEMIS/tree/main/.claude/skills/design
Command: npx skills add https://github.com/fluxforgeai/ARTEMIS --skill design-fluxforgeai

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Architectural decisions are often slowed by scattered information, inconsistent reasoning, and weak alignment among stakeholders. This Skill provides a structured, evidence-based framework to analyze options, compare tradeoffs, and generate actionable design recommendations.

Core Features & Use Cases

  • Codebase analysis: read and synthesize key patterns to ground design advice.
  • Documentation review: synthesize architecture docs and runbooks to validate alignment.
  • External research: gather 2026 sources to inform best practices and benchmark alternatives.
  • Impact & recommendations: produce a concise design recommendation with trade-off analysis and recommended steps.
  • Pattern evaluation & migration planning: evaluate design patterns and plan migrations when needed.

Quick Start

Analyze the current architecture and dependencies to generate a design recommendation.

Frequently Asked Questions about design

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
What is evidence-based design analysis for software architecture?

Evidence-based design analysis evaluates architectural decisions by synthesizing codebase patterns, documentation, and external research to produce validated tradeoff comparisons and actionable design recommendations.

How do I evaluate architectural tradeoffs when planning a system migration?

To evaluate architectural tradeoffs during migration planning, analyze your current codebase patterns, review existing documentation, and benchmark external best practices to generate a structured impact assessment.

Can I use this for codebase analysis to validate my current architecture?

Yes, codebase analysis reads and synthesizes key patterns from your source code to ground design advice and validate whether your current architecture aligns with documented runbooks and requirements.

What's the best way to review architecture documentation for stakeholder alignment?

The best way to review architecture documentation is to synthesize architecture docs and runbooks together, validating alignment across stakeholders through structured exploration and reproducible analysis outputs.

Does design analysis work without external research sources?

Design analysis can function by relying on codebase analysis and documentation review, but incorporating external research sources informs best practices and benchmarks alternatives for more robust tradeoff evaluation.

When should I not use automated design analysis for architectural decisions?

Automated design analysis may not be suitable when scattered information cannot be consolidated into documentation, or when inconsistent reasoning across stakeholders prevents establishing reproducible analysis inputs.