Understand and adhere to the project's technology stack including Laravel, PHP, React, PostgreSQL, Pest, Tailwind CSS, and all configured tools and services. Use this skill when making architectural decisions, when choosing libraries or packages, when configuring development tools, when setting up testing frameworks, when implementing authentication, when integrating third-party services, when configuring CI/CD pipelines, when setting up local development environments, or when ensuring consistency with the established tech stack across all parts of the application.
Content & Writing
85 Stars
2 Forks
Updated Jan 19, 2026, 04:39 AM
Why Use This
This skill provides specialized capabilities for aiskillstore's codebase.
Use Cases
Developing new features in the aiskillstore repository
Refactoring existing code to follow aiskillstore standards
Understanding and working with aiskillstore's codebase structure
---
name: global-tech-stack
description: Understand and adhere to the project's technology stack including Laravel, PHP, React, PostgreSQL, Pest, Tailwind CSS, and all configured tools and services. Use this skill when making architectural decisions, when choosing libraries or packages, when configuring development tools, when setting up testing frameworks, when implementing authentication, when integrating third-party services, when configuring CI/CD pipelines, when setting up local development environments, or when ensuring consistency with the established tech stack across all parts of the application.
---
# Global Tech Stack
This Skill provides Claude Code with specific guidance on how to adhere to coding standards as they relate to how it should handle global tech stack.
## When to use this skill
- When making architectural decisions or choosing approaches for new features
- When selecting or evaluating third-party packages or libraries
- When configuring development tools and environments
- When setting up Laravel, PHP, or React project configurations
- When implementing database-related functionality with PostgreSQL and Eloquent
- When writing tests using Pest framework
- When using Laravel-specific tools (Pint, Herd, Telescope, DebugBar, Wayfinder, Fortify)
- When integrating third-party services (Resend for email, Sentry for errors, etc.)
- When configuring CI/CD with GitHub Actions
- When setting up local development with Laravel Herd
- When implementing caching with Redis
- When ensuring consistency with established frameworks and patterns
- When documenting technical decisions or dependencies
## Instructions
For details, refer to the information provided in this file:
[global tech stack](../../../agent-os/standards/global/tech-stack.md)
