architect_skill

This skill designs scalable, maintainable software architectures, evaluating trade-offs and guiding pattern choices to ensure forward-looking, consistent
  • JavaScript

0

GitHub Stars

1

Bundled Files

2 months ago

Catalog Refreshed

4 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill itou-daiki/easy_stat_edu --skill architect

  • SKILL.md6.1 KB

Overview

This skill is a software architecture specialist focused on designing scalable, maintainable systems and guiding technical decision-making. Use it proactively when planning new features, refactoring large areas, or making trade-offs between performance, cost, and complexity. The skill produces concrete designs, ADRs, and checklists to move from analysis to implementation.

How this skill works

I review the current state, gather functional and non-functional requirements, and produce a high-level design with component responsibilities, data models, and API contracts. For each significant choice I provide trade-off analysis (pros, cons, alternatives, decision and rationale) and produce Architecture Decision Records where appropriate. I deliver actionable next steps: checkpoints for testing, deployment, monitoring, and rollout.

When to use it

  • Planning a new feature or product module
  • Refactoring or modularizing a large codebase
  • Choosing databases, caches, or messaging systems
  • Designing for scale (performance, availability)
  • Preparing architecture review or executive technical summary

Best practices

  • Start with clear functional and non-functional requirements before designing
  • Favor modularity: single responsibility, high cohesion, low coupling
  • Document trade-offs and decisions with ADRs for future traceability
  • Design stateless services and plan horizontal scaling paths early
  • Include testing, monitoring, and rollback plans in the initial design

Example use cases

  • Design an API and data model for a new billing service with scaling targets
  • Refactor a monolith into independently deployable services with migration plan
  • Choose between Redis, PostgreSQL, or a managed vector DB for semantic search with cost/perf analysis
  • Create a component diagram and ADRs for adopting event-driven architecture
  • Assess bottlenecks and propose caching and query optimizations for read-heavy endpoints

FAQ

A current-state summary, requirements mapping, a high-level architecture diagram, component responsibilities, ADRs for key decisions, and a prioritized implementation checklist.

How do you handle trade-offs between speed and cost?

I document pros, cons, and alternatives for each option, estimate operational cost and performance impact, and recommend a decision aligned with your non-functional priorities and growth plan.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational
architect skill by itou-daiki/easy_stat_edu | VeilStrat