[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7EVWFHP138FVTAPQKJEY2ZQ":3,"skill-same:01M7EVWFHP138FVTAPQKJEY2ZQ":45},{"skillNo":4,"name":5,"nameZh":6,"description":6,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":15,"categories":16,"keywords":17,"publishedAt":18,"linkOnly":19,"markdownContent":20,"markdownBody":21,"frontMatter":22,"refName":23,"commitSha":24,"skillDirectory":25,"forksCount":26,"repositoryHtmlUrl":27,"repositoryHomepageUrl":6,"ownerHtmlUrl":28,"ownerBlogUrl":29,"ownerDescription":6,"updatedAt":30,"install":31,"resources":44},"01M7EVWFHP138FVTAPQKJEY2ZQ","ams-senior-architect",null,"TanNhatCMS\u002Fjarvis","TanNhatCMS","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F113796420?v=4","01M753MV17KG5CD3152G3WQEQY","KietNT","01M7EKEDYVYQ6PWVJJMZ911VMX",0,"MIT","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-senior-architect\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: senior-architect\ndescription: Software architect perspective: system decomposition, integration patterns, ADRs, and long-horizon trade-offs. Use when designing systems, evaluating technical direction, or documenting architecture decisions.\ncategory: development\n---\n\n# Senior Architect\n\n## Overview\n\nAn architect's job is not to draw boxes — it's to make the **expensive decisions cheap to revisit**\nand the **cheap decisions fast to make**. This skill captures the architect's toolkit: decomposing\nsystems along the right seams, choosing integration patterns deliberately, documenting decisions so\nfuture teams understand the *why*, and keeping architecture aligned with team structure and business\nrisk rather than with fashion.\n\nThe through-line: architecture is risk management with diagrams.\n\n## When to use\n\n- Starting a new system or a major rewrite: choosing structure and boundaries.\n- Evaluating build-vs-buy, framework, or platform decisions.\n- Resolving conflicting technical directions between teams.\n- Documenting why the system looks the way it does (ADRs, RFCs).\n- Reviewing whether a design will survive 10x growth or a team doubling.\n\n## Core concepts\n\n- **Seams over layers.** Decompose along axes of independent change: things that change for different\n  reasons, at different rates, or by different teams belong apart. \"Microservices\" is an org-scaling\n  answer, not a code-quality answer — a modular monolith with clean seams beats premature distribution.\n- **Integration patterns, chosen deliberately:**\n  - Sync request\u002Fresponse (REST\u002FRPC) — simple, coupled in time; fine within a trust\u002Flatency boundary.\n  - Async events — decoupled in time, eventual consistency; needs idempotent consumers and schema\n    discipline.\n  - Shared database — fastest to start, hardest to split later; treat as tech debt with a plan.\n  - Pick per boundary, not per fashion. Most systems need all three somewhere.\n- **ADRs (Architecture Decision Records).** One short document per significant decision: context,\n  options considered, decision, consequences. Future you — or your successor — will otherwise\n  re-litigate every choice. Store them in the repo, next to the code they govern.\n- **Quality attributes drive design.** Name the top 3 non-functionals (e.g., \"p99 \u003C 300ms\",\n  \"survive AZ failure\", \"onboard a dev in a day\") and let them arbitrate every trade-off. Vague\n  \"scalability\" justifies anything; quantified attributes justify the right thing.\n- **Conway's law is a tool.** Design team boundaries and system boundaries together — or accept that\n  the org chart will design your system for you. If two teams must coordinate to ship, the seam is\n  in the wrong place.\n- **Evolutionary architecture.** Fitness functions (automated checks on what matters: dependency\n  rules, performance budgets, security invariants) keep architecture from decaying silently.\n\n## Practical workflow\n\n1. **Frame the problem.** Write the one-paragraph problem statement, the top-3 quality attributes\n   with numbers, and the constraints (team size, timeline, compliance, existing systems).\n2. **Explore options divergently.** Sketch 2–3 candidate architectures (e.g., modular monolith vs\n   services vs serverless). For each: what it optimizes, what it sacrifices, what kills it.\n3. **Decide with an ADR.** Record context, options, decision, and consequences — including what\n   would make you revisit it (revisit triggers are the most valuable line in an ADR).\n4. **Define the seams contractually.** Module\u002Fservice APIs, event schemas with versioning policy,\n   data ownership (every datum has exactly one writer). Ambiguous ownership is where coupling hides.\n5. **De-risk the unknowns with spikes.** Time-boxed prototypes for the riskiest 1–2 assumptions\n   (throughput, a vendor's actual behavior, a tricky integration). Throw the spike away; keep the learning.\n6. **Install fitness functions.** Automated guards for the invariants you care about: no circular\n   module deps, API latency budgets in CI, dependency-license checks.\n\nADR template (keep it to one page):\n\n```markdown\n# ADR-014: Event-driven order fulfillment\n\n## Status: Accepted (2026-09-26)\n## Context\nOrder volume is spiking 10x during sales; fulfillment steps (payment, warehouse,\nemail) fail independently and shouldn't block each other.\n## Decision\nPublish `order.placed` events; each fulfillment step consumes independently with\nidempotent handlers. Order service owns order state; steps own their own state.\n## Consequences\n+ Steps deploy and scale independently; partial failures don't block checkout.\n- Eventual consistency: order may show \"processing\" briefly; consumers must be idempotent.\n- Need schema registry + dead-letter queues (ops cost).\n## Revisit if\nVolume stays flat for 4 quarters, or exactly-once semantics become a hard requirement.\n```\n\n## Common pitfalls\n\n- **Resume-driven architecture.** Choosing Kafka\u002FKubernetes\u002Fmicroservices because they're\n  prestigious, not because the problem demands them. Complexity is a cost; spend it on the problem.\n- **Big-bang rewrites.** \"We'll rewrite it properly this time\" fails because the old system's\n  value is in its bug fixes. Strangler-fig migration — replace piece by piece behind the seam.\n- **Undocumented decisions.** Six months later nobody remembers why the cache TTL is 90 seconds.\n  ADRs are cheap; archaeology is expensive.\n- **Designing for 100x while at 1x.** Solve today's bottleneck with room to evolve; don't build\n  the 100x system before product-market fit. Premature distribution is the costliest form.\n- **Ignoring the human architecture.** A design requiring five teams to coordinate weekly will\n  decay into whatever five teams can ship without talking. Align seams with team ownership.\n- **Analysis paralysis.** Architecture is reversible in degrees — reversible decisions should be\n  made fast and revisited; only one-way doors deserve long deliberation. Most doors are two-way.\n- **Diagrams without decisions.** Beautiful C4 diagrams that nobody references. The diagram is a\n  communication aid; the ADR is the artifact.\n","# Senior Architect\n\n## Overview\n\nAn architect's job is not to draw boxes — it's to make the **expensive decisions cheap to revisit**\nand the **cheap decisions fast to make**. This skill captures the architect's toolkit: decomposing\nsystems along the right seams, choosing integration patterns deliberately, documenting decisions so\nfuture teams understand the *why*, and keeping architecture aligned with team structure and business\nrisk rather than with fashion.\n\nThe through-line: architecture is risk management with diagrams.\n\n## When to use\n\n- Starting a new system or a major rewrite: choosing structure and boundaries.\n- Evaluating build-vs-buy, framework, or platform decisions.\n- Resolving conflicting technical directions between teams.\n- Documenting why the system looks the way it does (ADRs, RFCs).\n- Reviewing whether a design will survive 10x growth or a team doubling.\n\n## Core concepts\n\n- **Seams over layers.** Decompose along axes of independent change: things that change for different\n  reasons, at different rates, or by different teams belong apart. \"Microservices\" is an org-scaling\n  answer, not a code-quality answer — a modular monolith with clean seams beats premature distribution.\n- **Integration patterns, chosen deliberately:**\n  - Sync request\u002Fresponse (REST\u002FRPC) — simple, coupled in time; fine within a trust\u002Flatency boundary.\n  - Async events — decoupled in time, eventual consistency; needs idempotent consumers and schema\n    discipline.\n  - Shared database — fastest to start, hardest to split later; treat as tech debt with a plan.\n  - Pick per boundary, not per fashion. Most systems need all three somewhere.\n- **ADRs (Architecture Decision Records).** One short document per significant decision: context,\n  options considered, decision, consequences. Future you — or your successor — will otherwise\n  re-litigate every choice. Store them in the repo, next to the code they govern.\n- **Quality attributes drive design.** Name the top 3 non-functionals (e.g., \"p99 \u003C 300ms\",\n  \"survive AZ failure\", \"onboard a dev in a day\") and let them arbitrate every trade-off. Vague\n  \"scalability\" justifies anything; quantified attributes justify the right thing.\n- **Conway's law is a tool.** Design team boundaries and system boundaries together — or accept that\n  the org chart will design your system for you. If two teams must coordinate to ship, the seam is\n  in the wrong place.\n- **Evolutionary architecture.** Fitness functions (automated checks on what matters: dependency\n  rules, performance budgets, security invariants) keep architecture from decaying silently.\n\n## Practical workflow\n\n1. **Frame the problem.** Write the one-paragraph problem statement, the top-3 quality attributes\n   with numbers, and the constraints (team size, timeline, compliance, existing systems).\n2. **Explore options divergently.** Sketch 2–3 candidate architectures (e.g., modular monolith vs\n   services vs serverless). For each: what it optimizes, what it sacrifices, what kills it.\n3. **Decide with an ADR.** Record context, options, decision, and consequences — including what\n   would make you revisit it (revisit triggers are the most valuable line in an ADR).\n4. **Define the seams contractually.** Module\u002Fservice APIs, event schemas with versioning policy,\n   data ownership (every datum has exactly one writer). Ambiguous ownership is where coupling hides.\n5. **De-risk the unknowns with spikes.** Time-boxed prototypes for the riskiest 1–2 assumptions\n   (throughput, a vendor's actual behavior, a tricky integration). Throw the spike away; keep the learning.\n6. **Install fitness functions.** Automated guards for the invariants you care about: no circular\n   module deps, API latency budgets in CI, dependency-license checks.\n\nADR template (keep it to one page):\n\n```markdown\n# ADR-014: Event-driven order fulfillment\n\n## Status: Accepted (2026-09-26)\n## Context\nOrder volume is spiking 10x during sales; fulfillment steps (payment, warehouse,\nemail) fail independently and shouldn't block each other.\n## Decision\nPublish `order.placed` events; each fulfillment step consumes independently with\nidempotent handlers. Order service owns order state; steps own their own state.\n## Consequences\n+ Steps deploy and scale independently; partial failures don't block checkout.\n- Eventual consistency: order may show \"processing\" briefly; consumers must be idempotent.\n- Need schema registry + dead-letter queues (ops cost).\n## Revisit if\nVolume stays flat for 4 quarters, or exactly-once semantics become a hard requirement.\n```\n\n## Common pitfalls\n\n- **Resume-driven architecture.** Choosing Kafka\u002FKubernetes\u002Fmicroservices because they're\n  prestigious, not because the problem demands them. Complexity is a cost; spend it on the problem.\n- **Big-bang rewrites.** \"We'll rewrite it properly this time\" fails because the old system's\n  value is in its bug fixes. Strangler-fig migration — replace piece by piece behind the seam.\n- **Undocumented decisions.** Six months later nobody remembers why the cache TTL is 90 seconds.\n  ADRs are cheap; archaeology is expensive.\n- **Designing for 100x while at 1x.** Solve today's bottleneck with room to evolve; don't build\n  the 100x system before product-market fit. Premature distribution is the costliest form.\n- **Ignoring the human architecture.** A design requiring five teams to coordinate weekly will\n  decay into whatever five teams can ship without talking. Align seams with team ownership.\n- **Analysis paralysis.** Architecture is reversible in degrees — reversible decisions should be\n  made fast and revisited; only one-way doors deserve long deliberation. Most doors are two-way.\n- **Diagrams without decisions.** Beautiful C4 diagrams that nobody references. The diagram is a\n  communication aid; the ADR is the artifact.\n",{},"main","af388a77c2fe5e0b4fd879cca4300a0ffa9a6579","skills\u002Fams-senior-architect",1,"https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis","https:\u002F\u002Fgithub.com\u002FTanNhatCMS","https:\u002F\u002Fmrkiet.name.vn","2026-11-07 14:23:08",{"source":7,"skillName":5,"commands":32,"prompt":42,"zipAvailable":43},[33,36,39],{"tool":34,"command":35},"npx","npx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-architect",{"tool":37,"command":38},"bunx","bunx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-architect",{"tool":40,"command":41},"pnpm","pnpm dlx skills add TanNhatCMS\u002Fjarvis --skill ams-senior-architect","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fams-senior-architect\u002FSKILL.md",true,[],[46,53,61,68,75,82],{"skillNo":47,"name":48,"nameZh":6,"description":49,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":50,"categories":51,"keywords":52,"publishedAt":18},"01M7EWYJR0J8DARY7E59Z6Y9MV","web-scrape","Turn web pages into LLM-ready markdown via the Firecrawl API (renders JS, anti-bot handling). Use when browser_open\u002Ffetch fails on JS-heavy pages, or when you need clean markdown\u002Fstructured extraction from a site. Requires FIRECRAWL_API_KEY.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fweb-scrape\u002FSKILL.md",[],[],{"skillNo":54,"name":55,"nameZh":6,"description":56,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":57,"sourceHtmlUrl":58,"categories":59,"keywords":60,"publishedAt":18},"01M7EWYBN5P6F2AJG3FR24T9BP","design-taste-frontend","tasteskill v2, the anti-slop frontend skill. Art direction for websites, distilled from a study of 247 curated gallery sites (One Page Love, Awwwards Sites of the Day). Deals researched directions (idea, composition, type, palette, photographs, section blueprints) from a library, enforces a strict no-slop house style with a real-browser inspector, and runs a look-and-fix loop on screenshots. Use this whenever you build, design, redesign, restyle, polish or review a landing page, marketing site, portfolio, product page, one-pager, hero or any public-facing web page, in any stack (HTML\u002FCSS, React, Next.js, Vue, Svelte, Astro, Tailwind) — also when the user says a page looks generic, templated, \"AI-made\", sloppy, or asks to make it look designed, premium, award-level or less like every other site. Not for dashboards or app screens.","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FLICENSE","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Ftaste-design\u002FSKILL.md",[],[],{"skillNo":62,"name":63,"nameZh":6,"description":64,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":65,"categories":66,"keywords":67,"publishedAt":18},"01M7EWY8FQFNQ2GB7NZZWGSSDX","test-driven-development","Use when implementing any feature or bugfix, before writing implementation code","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-tdd\u002FSKILL.md",[],[],{"skillNo":69,"name":70,"nameZh":6,"description":71,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":72,"categories":73,"keywords":74,"publishedAt":18},"01M7EWY5SHBFRH1HDHVWM9K7TV","systematic-debugging","Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-debugging\u002FSKILL.md",[],[],{"skillNo":76,"name":77,"nameZh":6,"description":78,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":79,"categories":80,"keywords":81,"publishedAt":18},"01M7EWY3NM0Z0JAKS7HDZ24K66","requesting-code-review","Use when completing tasks, implementing major features, or before merging to verify work meets requirements","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-code-review\u002FSKILL.md",[],[],{"skillNo":83,"name":84,"nameZh":6,"description":85,"descriptionZh":6,"repositoryFullName":7,"ownerLogin":8,"ownerAvatarUrl":9,"ownerAccountNo":10,"ownerDisplayName":11,"repositoryNo":12,"starsCount":13,"licenseSpdxId":14,"licenseFileUrl":6,"sourceHtmlUrl":86,"categories":87,"keywords":88,"publishedAt":18},"01M7EWY0WRMWX4M9ZFY0WKC593","brainstorming","You MUST use this before any creative work - creating features, building components, adding functionality, modifying behavior, or planning anything new, in software or out of it (a talk, a business, a renovation).","https:\u002F\u002Fgithub.com\u002FTanNhatCMS\u002Fjarvis\u002Fblob\u002Fmain\u002Fskills\u002Fsuperpowers-brainstorming\u002FSKILL.md",[],[]]