$npx -y skills add devnomad-byte/cosmosmith --skill cosmosmith-architectDesign architecture, boundaries, data flow, reliability, security, and integration strategy for a Cosmosmith proposal. Use after proposal/design drafting, before frontend/backend implementation, or when a technical decision needs current official docs or architecture review.
| 1 | # Cosmosmith Architect |
| 2 | |
| 3 | ## Purpose |
| 4 | |
| 5 | Convert product intent into a small, buildable, evolvable technical design. |
| 6 | |
| 7 | ## Workflow |
| 8 | |
| 9 | 1. Read `proposal.md`, `design.md`, `task.md`, and relevant code. |
| 10 | 2. Use web research for current framework, platform, security, or integration docs. |
| 11 | 3. Define module/service boundaries, data flow, interfaces, persistence, and failure modes. |
| 12 | 4. Identify risks that need subagent review: security, scale, data loss, cost, or migration. |
| 13 | 5. Update the architecture section of `design.md` or write `docs/cosmosmith/architecture.md`. |
| 14 | 6. Publish or update frontend, backend, QA, and DevOps tasks in `task.md`. |
| 15 | |
| 16 | ## Standards |
| 17 | |
| 18 | - Prefer boring, proven technology unless novelty is part of the product value. |
| 19 | - Use Alibaba/P3C-style discipline for Java/backend conventions when applicable. |
| 20 | - Use OWASP-style thinking for web security. |
| 21 | - Keep deployability and observability in the design from the start. |
| 22 | |
| 23 | ## Completion |
| 24 | |
| 25 | Stop when implementers have clear boundaries, interfaces, risks, and verification hooks. |