Use when the user is deciding, reviewing, or second-guessing a software architecture or tech-stack choice — monolith vs microservices vs serverless vs event-driven, backend language, database type, caching, CQRS/event sourcing, polyglot, or a migration like Strangler Fig. Triggers on "should I use microservices", "which database", "tech stack for", "system design", or "architecture review". For how to deploy, operate, and scale that design (CI/CD, cloud, Kubernetes, IaC), use devops.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
An evidence-based decision framework for software architecture and technology selection. Grounded in practitioner literature, not hype cycles.
Deliver only what the user will actually use. Never leak internal scaffolding into the output:
Apply frameworks silently — name one only when it helps the reader, not to show your work. When context is missing, state your assumption in one line and proceed; don't interrogate.
Apply these as lenses to every architectural decision:
When advising on architecture or tech stack:
Read the relevant reference file based on the user's question:
| Topic | File | When to read |
|---|---|---|
| Architectural styles | references/architectural-styles.md | Monolith vs microservices vs serverless vs event-driven decisions |
| Backend runtimes | references/backend-runtimes.md | Language/runtime selection, polyglot architecture decisions |
| Data layer | references/data-layer.md | Database selection, caching, CQRS, event sourcing |
When giving architectural advice:
아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Use when a B2B SaaS founder needs to choose, prioritize, or rebalance customer acquisition channels — deciding outbound vs inbound, paid vs PLG, where to put marketing budget, or sanity-checking CAC, LTV:CAC, and payback. Also for channel-specific playbooks (cold email, LinkedIn, paid social, community, partnerships) and channel-mix audits. Not for closing tactics (use sales-skill) or copy (use copywriter-skill).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs to write, rewrite, review, or critique commercial copy meant to drive a reader toward action — landing pages, hero sections, headlines, email (cold outreach, nurture, promo, launch), CTAs, microcopy, product descriptions, value propositions, ads, or taglines. Also for copy audits, clarity checks, conversion reviews, or choosing a framework (AIDA, PAS, BAB, FAB, 4U's). Applies even when the user just says "write me an email" or "review this page." Not for channel/budget strategy (use channel-expert) or pricing structure (use pricing).
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs to design, run, or audit product or GTM analytics — metric hierarchies and north stars, funnels, cohort retention, churn, pipeline velocity, forecasting, lead scoring, NRR, A/B tests, or analytical SQL — or uploads a dataset to analyze. Triggers on questions like "why did activation drop", "is this metric meaningful", "review my dashboard", or "what should I measure". For writing the spec that defines a feature's success metrics, use product-spec.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when a non-designer needs to audit a UI, generate a design spec (spacing, type scale, color tokens, grids), or build brand foundations (logo systems, palette and type pairing, brand guidelines). Covers the visual layer, UX/perceptual critique, and brand identity. For implementing the design in code (React/HTML/CSS), use frontend-design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when the user needs to deploy, operate, secure, or scale running infrastructure — cloud architecture (multi-region, VPC, FinOps), CI/CD and deployment strategies, secrets/IAM/supply-chain security, observability and SLO alerting, SRE and incident response, Kubernetes vs ECS and autoscaling, Terraform/Pulumi/CDK, or platform engineering and DORA metrics. Also for generating runbooks, pipeline configs, Terraform modules, or Kubernetes manifests. For choosing the system's architecture or stack before it runs (monolith vs microservices, which database), use software-architect.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Use when planning, auditing, or speccing a video's motion and visual craft: shot lists, storyboards, color scripts, transitions, easing, kinetic typography, pacing, retention, or animation principles. Triggers: 'video plan', 'shot list', 'storyboard', 'color script', 'motion spec', 'fix the pacing', 'explainer/demo/brand video'. For the spoken words themselves, use script-writer-skill; for in-code UI motion, use frontend-design.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.