# Align Projects With a Laravel React Stack

Teams can drift from established stack choices when building features. This skill guides architecture, tooling, and implementation decisions for a Laravel, React, PostgreSQL, and Pest application.

## Install

```bash
npx skillstore add devanb/global-tech-stack
```

## Metadata

- Status: approved
- Slug: devanb-global-tech-stack
- Skillstore revision: r1
- Version status: missing
- Tree hash: f8d5d117ccbf2ead45467d15bd520b7c6358cb935670d9da54f936b0b6d03f93
- Author: DevanB
- GitHub username: DevanB
- License: MIT
- Repository: https://github.com/DevanB/lucidlog/tree/master/.claude/skills/global-tech-stack
- Ref: 0519034dad657fb1f7706e0550e962beeda73fdf
- Supported tools: Claude, Codex, Claude Code
- Audit status: complete
- Agent install advisory: allowed
- Manual install advisory: allowed
- Artifact signature: available
- Audit attestation: unavailable
- Human verification: not\_verified
- Risk factors: filesystem
- Quality score: 78
- Quality tier: bronze
- Public page: https://skillstore.pages.dev/skills/devanb-global-tech-stack
- Manifest: https://skillstore.pages.dev/api/skills/devanb-global-tech-stack/manifest

## Capabilities

- Guides decisions for Laravel, PHP, React, PostgreSQL, Pest, Tailwind CSS, and Redis.
- Supports package and library selection against the established technology stack.
- Covers Laravel tools including Pint, Herd, Telescope, DebugBar, Wayfinder, and Fortify.
- Frames testing work around the Pest framework.
- Supports integration choices for Resend, Sentry, and GitHub Actions.
- Encourages documentation of technical decisions and dependencies.

## Use Cases

- Plan a New Feature: Use the skill to choose framework patterns, storage, tests, and services before implementation starts.
- Review Dependency Choices: Use the skill to compare proposed packages with the approved stack and existing Laravel tools.
- Standardize Project Setup: Use the skill to align local tooling, testing, CI, caching, and monitoring decisions.

## Prompt Templates

### Check Stack Fit

```
Review this proposed feature and explain which parts of the established Laravel, React, PostgreSQL, and Pest stack should guide the implementation.
```

### Plan an Implementation

```
Create an implementation plan for this feature using the approved stack. Include backend, frontend, database, tests, and service integration decisions.
```

### Evaluate a Package

```
Evaluate this package choice against the project stack. Explain benefits, risks, alternatives, and whether it fits the existing Laravel and React tooling.
```

### Design a Release Path

```
Design a delivery approach for this change using the project stack. Cover testing with Pest, CI with GitHub Actions, error monitoring, and rollback concerns.
```

## Limitations

- The detailed stack guidance is referenced through an external relative link.
- It does not verify installed package versions or project configuration.
- It does not provide complete implementation code for each framework.
- It is focused on one Laravel and React stack, not broad stack comparison.

## Best Practices

- Start with the approved stack before introducing a new package or service.
- Document technical decisions when a choice affects architecture or dependencies.
- Include testing, CI, and operational concerns in implementation plans.

## Anti Patterns

- Adding duplicate tools when the stack already names a supported option.
- Choosing libraries without checking Laravel, React, and PostgreSQL compatibility.
- Treating local development, testing, and deployment as separate decisions.

## Security Audit

- Audited at: 2026-07-09T11:21:17.004\+00:00
- Summary: Confirmed the static path traversal finding because SKILL.md instructs the agent to follow a ../../../ link outside the reviewed skill package. No separate prompt injection, exfiltration, network, or command execution intent was found in SKILL.md.

## Stats

- Views: 221
- Downloads: 8
- Favorites: 0
- Popularity score: 0