Skip to content
Back to skills

Tech Stacks Vheins

ASecurity

A skill for managing and applying technology-specific architectural patterns and best practices using predefined templates.

  • 57 stars
  • 0 votes
  • 0 copies
  • 0 views
  • Added October 17, 2026
developmentrustgophpreactvuenextjsexpressfastapispringapi

Works with

  • api

Security analysis

A100/100

Scanned October 17, 2026

npx -y skills add diegosouzapw/awesome-omni-skill --skill tech-stacks-vheins --agent claude-code

Installs into .claude/skills of the current project.

Are you the author of Tech Stacks Vheins?

Add the live security badge to your README. It updates with every re-scan.

Security grade badge for Tech Stacks Vheins
[![Security: A — Skills Directory](https://www.skillsdirectory.com/api/skills/diegosouzapw-tech-stacks-vheins/badge)](https://www.skillsdirectory.com/skills/diegosouzapw-tech-stacks-vheins)

More formats (shields.io, HTML) on the badges page. Keep it an A: scan every change in CI with Pro.

Download with Pro
SKILL.md
---
name: tech-stacks
description: A skill for managing and applying technology-specific architectural patterns and best practices using predefined templates.
---

# Tech Stacks Skill

This skill provides a collection of architectural blueprints and best practices for various technology stacks. It is designed to ensure that new features follow the established patterns of the project's ecosystem.

## Resources

The templates are located in `.agent/skills/tech-stacks/resources/`. Available tech stacks include:

- **PHP**: `laravel.md`, `laravel-filament.md`
- **Frontend**: `vuejs.md`, `react.md`, `nextjs.md`, `nuxtjs.md`, `flutter.md`
- **Backend API**: `express.md`, `fastapi.md`, `golang.md`, `rust.md`, `spring-boot.md`
- **Enterprise**: `dotnet.md`, `odoo.md`

## Usage Instructions

1. **Identify the Stack**: Determine which technology stack is relevant to the task (e.g., if working on the admin dashboard, refer to `laravel-filament.md`).
2. **Review Best Practices**: Read the corresponding template in `resources/` to understand the data structures, directory patterns, and naming conventions.
3. **Apply Patterns**: Implement code, migrations, or services following the specific rules outlined in the template.
4. **Validation**: Ensure that any new code adheres to the architectural rules of the selected stack.

## Best Practices
- **Consistency**: Always prefer project-specific patterns over generic coding styles.
- **Reference**: Link to the relevant tech stack documentation when explaining architectural decisions.
- **Maintenance**: If the project's architecture evolves, update the templates in `resources/` to reflect the new standards.

Attribution

Is this your skill, or is something wrong with this listing? Request removal or report an issue. Author removals are honored within 72 hours.

Comments

Loading comments…

Newsletter

Get the weekly list of safe new skills, and the ones we pulled.