- Home
- Skills
- Shotaiuchi
- Dotclaude
- Design Futurist
design-futurist_skill
- Shell
0
GitHub Stars
1
Bundled Files
2 months ago
Catalog Refreshed
4 months ago
First Indexed
Readme & install
Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.
Installation
Preview and clipboard use veilstrat where the catalogue uses aiagentskills.
npx veilstrat add skill shotaiuchi/dotclaude --skill design-futurist- SKILL.md2.0 KB
Overview
This skill provides forward-looking design analysis focused on long-term scalability, technology evolution, extensibility, and migration cost. It helps reviewers spot architectural ceilings, emergence risks, and practical migration paths. The output frames findings with concise strength ratings to guide decision-making.
How this skill works
The skill inspects a design proposal against a checklist covering scalability trajectory, technology evolution, extension points, and migration cost. It flags bottlenecks, evaluates vendor and community viability, and verifies whether incremental migration and rollback strategies exist. Findings are summarized with one of four strength ratings: Strong, Moderate, Weak, or Neutral. The report highlights actionable risks and recommended next steps.
When to use it
- Reviewing architecture proposals before major investment or implementation
- Assessing choices of frameworks, platforms, or vendor solutions for longevity
- Planning large migrations, refactors, or multi-year product roadmaps
- Validating that new features can be added without core rewrites
- Evaluating readiness for 10x growth in users, data, or traffic
Best practices
- Map growth scenarios and test degradation patterns under projected load
- Prefer clear abstraction layers and plugin boundaries to enable swaps
- Prioritize incremental migration paths and define rollback points
- Monitor ecosystem health of chosen technologies and plan fallbacks
- Document extension points and expected performance envelopes
Example use cases
- Assessing a cloud-native redesign for expected 10x traffic increase
- Evaluating a move from a monolith to microservices with phased migration
- Choosing between competing frameworks based on community and lifecycle
- Auditing a product roadmap to ensure future features won’t need core rewrites
- Estimating operational and development costs for cross-platform support
FAQ
Strength indicates future readiness: Strong = well-positioned, Moderate = acceptable with risks, Weak = likely to require rework soon, Neutral = insufficient data to judge.
Can this analysis quantify migration cost?
The skill estimates migration cost ranges and identifies high-cost areas, but precise budgeting requires implementation details and resource rates from the organization.