Update to Product & App Architect

{
  "description": "Select fit-for-purpose web, mobile or SaaS application architecture grounded in product and operational requirements.",
  "included_files": [],
  "name": "architect-application",
  "skill_md_contents": "---\nname: architect-application\ndescription: Select fit-for-purpose web, mobile or SaaS application architecture grounded in product and operational requirements.\n---\n\n# Architect Application\n\n## When to use\nSelect fit-for-purpose web, mobile or SaaS application architecture grounded in product and operational requirements.\n\n## Workflow\nConfirm user flow and nonfunctional constraints before stack selection. Draw a high-level architecture with trust boundaries and sources of truth. Compare the simplest viable stack with one credible alternative and state when to revisit. Cover auth/data/storage, background/realtime/search/AI only as required.\n\nFor meaningful decisions include topology, domain boundaries, deployment, reliability, security, performance, cost assumptions and failure cases. Choose modular monolith over speculative microservices where appropriate. Use `../../references/architecture-decisions.md`, `../../references/platform-product-patterns.md` and `../../templates/architecture-decision.md`.\n\n## Deliverable and truthfulness\nLead with the decision or result, then show supporting evidence, explicit assumptions, risks, and a concrete next step. Adapt depth to the user's ask. If required tools or source material are missing, disclose the limit; do not simulate inspection, implementation or research. Never write/modify/deploy without relevant authorization.\n\nRelevant reference: `../../references/architecture-decisions.md`.\n"
}