メニュー
Provides architectural guidelines, coding standards, folder structure, and best practices for 13 supported tech stacks. DO NOT use for generating actual code.
Codex または Claude でインストール この Prompt をコピーして Codex、Claude、または他のアシスタントに貼り付けると、Skill ページを確認してインストールできます。
SOC 職業分類に基づく
Use to implement a REST or GraphQL API endpoint from a specification or description, including request validation, error handling, and accompanying tests. Activate for building a new API route, resolver, or handler end-to-end. Do NOT use for API design/contract creation, documentation generation, or frontend API consumption.
Use to implement background job processing with a queue, worker, retry with exponential backoff, dead letter queue, and monitoring. Activate when the request involves offloading work from the request cycle (emails, reports, data processing). Do NOT use for real-time event streaming, webhook handling, or scheduled cron jobs.
Use to scaffold a new project from scratch — generating directory structure, configuration files, entry points, and a README skeleton. Activate when starting a new project, service, or package and needing a production-ready starting point. Do NOT use for adding features to existing projects, generating tests, or CI/CD configuration.
Use to design and implement a caching layer for data that is expensive to compute or fetch. Activate for cache-aside, write-through, or write-behind patterns, TTL strategy, and cache invalidation logic. Do NOT use for database query optimization, CDN configuration, or HTTP response caching headers.
Use to generate a CI/CD pipeline configuration for building, testing, and deploying an application. Activate for GitHub Actions, GitLab CI, CircleCI, or similar pipeline tools for any tech stack. Do NOT use for infrastructure provisioning, Dockerfile creation, or deployment strategy design.
Use to generate production-ready code for a new feature, function, class, or module from a description. Activate for writing new code from scratch with error handling, inline documentation, and a self-review checklist. Do NOT use for refactoring existing code, code review, or test generation.
| name | tech-stack-guidelines |
| description | Provides architectural guidelines, coding standards, folder structure, and best practices for 13 supported tech stacks. DO NOT use for generating actual code. |
| version | 1.1.0 |
| time_saved | Manual: 2–4 hours | With skill: 10–15 minutes |
| license | Proprietary — Personal Use Only |
| category | coding |
| complexity | Intermediate |
| tokens | ~2500 |
| tags | ["tech-stack","architecture","best-practices","coding-standards","folder-structure","guidelines"] |
| author | vheins |
Provide architectural blueprints, folder structures, and standards for any of the 14 supported tech stacks to ensure project alignment.
| Variable | Type | Req | Description |
|---|---|---|---|
tech_stack | string | Yes | Target stack (see list) |
context | string | No | Focus: e.g., "auth", "folder structure" |
laravel (Modular Monolith)laravel-filament (ERP/Admin)vuejs, react, nextjs, nuxtjsflutter (GetX)express, fastapi, golang (Clean Arch)rust (Axum/Actix)spring-boot, dotnet (Clean Arch)odoo (ERP Platform){{context}} if specified.| Case | Strategy |
|---|---|
| Conflicts | Recommend closest compatible alternative; flag the tension. |
| Unfamiliar Stack | Apply general principles; explicitly note it is an untested blueprint. |
| Monolith vs Micro | Default to Monolith for teams <10 or <50k DAU. |
flowchart TD
A([Start: Tech Stack Guidelines]) --> B{Stack in supported list?}
B -- Yes --> C[Load reference guidelines for stack]
B -- No --> D[Apply general principles, note output is not a tested blueprint]
C & D --> E{Context provided?}
E -- Yes --> F[Focus output on relevant area: auth, folder structure, etc.]
E -- No --> G[Provide full guidelines]
F & G --> H[Stack Overview: core tech, versions, architecture pattern]
H --> I[Folder Structure: directory tree + purpose of each dir]
I --> J[Coding Standards: naming, typing, async, error handling, anti-patterns]
J --> K[Key Libraries & Tools: deps, testing framework, linting]
K --> L{Scale requirements conflict with stack?}
L -- Yes --> M[Flag conflict, recommend closest compatible alternative]
L -- No --> N
M & N --> O{Monolith vs microservices ambiguous?}
O -- Yes --> P[Default to monolith if team < 10 or traffic < 50k DAU, explain decision]
O -- No --> Q
P & Q --> R[Implementation Checklist: folder, naming, error handling, tests, anti-patterns]
R --> S{Migration path needed?}
S -- Yes --> T[Document migration path if requirements change]
S -- No --> U
T & U --> V([Output: Stack reference guide with checklist])
@upstash/context7-mcp: Library documentation and examples.@modelcontextprotocol/server-sequential-thinking: Complex reasoning.@modelcontextprotocol/server-memory: Knowledge graph.| Version | Date | Description |
|---|---|---|
| 1.0.0 | 2026-03-20 | Initial release — 14 stacks included |