From architect
Compare architectural or technical options with a structured pros/cons/recommendation analysis
npx claudepluginhub silviaare95/xari-plugins --plugin architectThis skill uses the workspace's default tool permissions.
Provides UI/UX resources: 50+ styles, color palettes, font pairings, guidelines, charts for web/mobile across React, Next.js, Vue, Svelte, Tailwind, React Native, Flutter. Aids planning, building, reviewing interfaces.
Fetches up-to-date documentation from Context7 for libraries and frameworks like React, Next.js, Prisma. Use for setup questions, API references, and code examples.
Calculates TAM/SAM/SOM using top-down, bottom-up, and value theory methodologies for market sizing, revenue estimation, and startup validation.
Analyze the tradeoffs between: $ARGUMENTS
Frame the decision — What exactly is being decided? What are the constraints (timeline, team size, existing tech, budget)?
Define evaluation criteria — Pick 4-6 criteria relevant to the decision. Common ones:
Evaluate each option — For each criterion, rate and explain. Be specific — "faster" isn't useful, "~50ms p99 vs ~200ms p99" is.
Identify hidden costs — What will bite you in 6 months? Migration difficulty, operational burden, hiring constraints.
Recommend — Pick one. State the conditions under which you'd pick the other.
## Tradeoff Analysis: <Option A> vs <Option B>
### Context
<What's being decided and why>
### Criteria Matrix
| Criteria | <Option A> | <Option B> |
|-------------|--------------------|--------------------|
| Complexity | <rating + detail> | <rating + detail> |
| Performance | <rating + detail> | <rating + detail> |
| ... | ... | ... |
### Hidden Costs
- **<Option A>**: <what'll hurt later>
- **<Option B>**: <what'll hurt later>
### Recommendation
**Go with <Option X>** because <primary reason>.
Choose <Option Y> instead if: <conditions>.