future-aware-architecture
Future-Aware Architecture
Design architecture decisions with a reusable method instead of stack-specific prescriptions.
This skill is technology-agnostic at its core. It helps the user decide what problem the architecture must solve, how to shape the system, what to select, why that choice fits now, how uncertain the recommendation still is, and how much option value it preserves for the future. When the decision depends on fast-moving domains such as AI models, platform capabilities, cloud offerings, or framework ecosystems, gather fresh evidence before locking the recommendation.
The core pattern is:
- define the problem before the solution
- classify the decision and its risk
- generate real options plus a baseline
- gather specialist evidence only where needed
More from liqiongyu/my-agents
brainstorming
Manual-first brainstorming workflow for turning ambiguous ideas or competing directions into an approved decision before planning or implementation. Activate when the user explicitly asks to brainstorm, explore options, compare approaches, or pressure-test a direction. Do not activate for clarification, review, detailed planning, or straightforward execution once a direction is already chosen.
10deep-research
Use when the user explicitly asks for comprehensive, citation-backed research such as a deep dive, due diligence, market analysis, or a multi-source comparison/report. Do not activate for quick factual lookups, ordinary coding tasks, or routine content generation unless the user first asks for research or source verification.
7project-documentation
>
6readme-craftsman
Create, update, or review a repository README when the user explicitly asks for README work. Use it to draft a new README, refresh an existing README after project changes, or audit a README against the current repository. Do not use it for general documentation, API docs, architecture docs, or documentation tasks that do not specifically target a README file.
5prompt-engineering
>
5review
>
4