skills.rest
YuluoY
YuluoYCOMMUNITY
Explore all skills by this author →
GitHub

tech-stack

Document technology choices with rationale, alternatives, and Mermaid diagrams.

1|Updated Apr 8, 2026
Search Tags:#architecture#documentation#mermaid#governance#software-design#tech-stack#tech-decision
One-click install
npx skills add https://github.com/YuluoY/nimis --skill tech-stack-yuluoy
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: tech-stack
Source: https://github.com/YuluoY/nimis/tree/main/skills-en/tech-stack
Command: npx skills add https://github.com/YuluoY/nimis --skill tech-stack-yuluoy

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Consolidates scattered technology decisions into a single, authoritative tech-stack document that teams can review and maintain.

Core Features & Use Cases

  • Document frontend, backend, databases, and infrastructure decisions with clear rationale and alternatives.
  • Include Mermaid diagrams for architecture and ER diagrams where applicable.
  • Use for architecture proposals, tech roadmaps, and ongoing tech-stack governance across projects and monorepos.

Quick Start

Provide your project goals and generate a complete tech-stack doc with rationale, alternatives, and diagrams in specs/tech-stack/.

Frequently Asked Questions about tech-stack

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I document technology choices for a software architecture proposal?▼

To document technology choices, you generate a structured tech-stack directory with rationale, alternatives, and Mermaid diagrams. It consolidates scattered frontend, backend, database, and infrastructure decisions into a single authoritative file for team review.

What is the best way to rationalize a tech stack decision across a monorepo?▼

The best way to rationalize a tech stack decision is using a governance document that outlines alternatives and rationale for each layer. This ensures ongoing tech-stack governance across projects and monorepos by maintaining a centralized technology record.

How do I generate Mermaid diagrams for software design and ER models?▼

You generate Mermaid diagrams for software design by creating a tech-stack specification. The process outputs architecture and ER diagrams automatically within a structured specs directory to visually map frontend, backend, and database components.

Can I use this for ongoing tech-stack governance and technical roadmaps?▼

Yes, you can use this for ongoing tech-stack governance and technical roadmaps. It maintains a structured tech-stack document that teams can review and update continuously, ensuring architecture proposals and stack decisions remain aligned with project goals.

What do I need to provide to generate a complete tech-stack document?▼

You need to provide your project goals to generate a complete tech-stack document. The system then outputs a structured specs/tech-stack directory containing the rationale, alternatives, and Mermaid diagrams without requiring additional dependencies.

Related Skills

Explore More Software Engineering Skills→
syahrilTGRsyahrilTGR
3

brainstorming

Guide structured brainstorming to define software designs and specifications.

Community
Advanced
pradeepmoulipradeepmouli
2

speckit-plan

Convert feature specifications into structured plan.md technical designs.

Community
Advanced
hoodinihoodini
262

mermaid-diagrams

Render Mermaid diagrams from plain-text syntax within Markdown documents.

Community
Basic
Jia-Hong-PengJia-Hong-Peng

speckit-plan

Generate structured implementation plans from spec.md files using spec-kit workflows.

Community
Intermediate