design-technical-solutionlisted

Design and baseline a software project's production technology, architecture, data and API boundaries, security, SEO, performance, business and visual component strategy, testing, build, preliminary deployment, and required environment. Use after requirements and experience are accepted, when a major technical direction changes, when deployment assumptions are unclear, or before installing project tooling. Inspect the actual environment only after the solution is accepted, and install nothing without explicit consent.
railgun20001/the-first · ★ 0 · Web & Frontend · score 70

Install: claude install-skill railgun20001/the-first

# Design Technical Solution Choose the minimum production solution that satisfies accepted outcomes and constraints. Do not let familiarity with a framework redefine the product. ## Confirm prerequisites and evidence 1. Read project instructions, `THE-FIRST.md`, accepted requirements, accepted experience decisions, and relevant feedback rules. 2. Confirm requirement and experience gates are accepted or explicitly skipped by the user. Keep discussion-only options unaccepted when gates are still open. 3. Inspect current source, dependencies, lock files, schemas, migrations, interfaces, tests, build, CI, containers, infrastructure, deployment notes, and actual runtime evidence available. 4. Identify existing components and platform capabilities before proposing new dependencies or duplicated abstractions. 5. Separate required quality attributes from speculative scale, premature optimization, and preferences. ## Derive the production shape Resolve the accepted scope's material decisions: ### System and delivery boundaries - Web, app, service, desktop, CLI, plugin, worker, or a justified combination. - Repository and module boundaries. - Client, server, background, third-party, and trust boundaries. - Rendering and delivery model, including SEO only when it is an accepted business need. ### Technology and data - Languages, frameworks, package managers, and supported version ranges. - Data ownership, models, persistence, transactions, migration, backup, retention, and reco