global-tech-stack
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 with my Agent
Copy this request to your Agent. It includes the canonical Skill page and manifest.
Review the Skillstore skill "global-tech-stack" from https://skillstore.io/skills/devanb-global-tech-stack.md and its manifest at https://skillstore.io/api/skills/devanb-global-tech-stack/manifest. Verify the artifact. You may proceed after verification, subject to the environment's own policy.Your Agent should still show its plan and request any confirmation required by the security policy.
Agent-readable resources
Use these links when an AI agent, crawler, or script needs clean context instead of reading the full page.
Test it
Using "global-tech-stack". A developer asks whether to add a new test framework for API tests.
Expected outcome:
The skill recommends Pest first, because the stack already names Pest as the testing framework. It suggests adding feature tests before introducing another tool.
Using "global-tech-stack". A team wants to add email delivery to a Laravel feature.
Expected outcome:
The skill points to Resend as the named email service and asks the team to document the decision, failure handling, and test coverage.
Using "global-tech-stack". A project needs caching for a high-traffic dashboard.
Expected outcome:
The skill recommends evaluating Redis because it is part of the stated stack, then pairing the plan with Laravel cache patterns and monitoring.
Security Audit
SafeConfirmed 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.
Capability review items (1)
These are real local capabilities that may be expected for this skill, so they require review but are not counted as confirmed malicious behavior.
Risk Factors
📁 Filesystem access (1)
Share & cite this report
Share the versioned assessment report, neutral badge, embed card, and citations. Skillstore reports evidence without deciding whether this Skill is safe.
Copy report link
https://skillstore.io/skills/devanb-global-tech-stack/audits/11?utm_source=security_passport&utm_medium=share&utm_campaign=versioned_reportMarkdown badge
[](https://skillstore.io/skills/devanb-global-tech-stack?utm_source=security_passport_badge)HTML badge
<a href="https://skillstore.io/skills/devanb-global-tech-stack?utm_source=security_passport_badge"><img src="https://skillstore.io/badges/skills/devanb-global-tech-stack/security.svg" alt="Skillstore security assessment" loading="lazy"></a>Embed card
<iframe src="https://skillstore.io/embed/skills/devanb-global-tech-stack.html" title="Skillstore Security Assessment" sandbox="allow-popups allow-popups-to-escape-sandbox" loading="lazy" referrerpolicy="no-referrer" width="420" height="180"></iframe>Academic citations (APA · BibTeX · CFF)
APA citation
DevanB. (2026). global-tech-stack security audit report (audit version 11) [Author version unspecified]. Skillstore. https://skillstore.io/skills/devanb-global-tech-stack/audits/11BibTeX citation
@techreport{devanb-devanb-global-tech-stack-2026,
author = {DevanB},
title = {global-tech-stack security audit report (audit version 11)},
institution = {Skillstore},
year = {2026},
number = {11},
url = {https://skillstore.io/skills/devanb-global-tech-stack/audits/11},
note = {Author version unspecified}
}CITATION.cff
cff-version: 1.2.0
message: "If you use this Skill, cite its author and this versioned security audit report."
title: "global-tech-stack security audit report (audit version 11)"
version: "unspecified"
type: report
authors:
- name: "DevanB"
date-released: "2026-07-09"
url: "https://skillstore.io/skills/devanb-global-tech-stack/audits/11"
identifiers:
- type: other
value: "skillstore:devanb-global-tech-stack:audit:11"
description: "Skillstore immutable audit report identifier"
Compare variants
2 installable variantsEach author remains a separate installable skill. The recommended variant is ranked by Skillstore evidence.
Why this variant is first
eis-its-global-tech-stack
2026-08-21
devanb-global-tech-stack
2026-08-21
Skillstore Score
Why this score Evidence Confidence: HighWhat You Can Build
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.
Try These Prompts
Review this proposed feature and explain which parts of the established Laravel, React, PostgreSQL, and Pest stack should guide the implementation.
Create an implementation plan for this feature using the approved stack. Include backend, frontend, database, tests, and service integration decisions.
Evaluate this package choice against the project stack. Explain benefits, risks, alternatives, and whether it fits the existing Laravel and React tooling.
Design a delivery approach for this change using the project stack. Cover testing with Pest, CI with GitHub Actions, error monitoring, and rollback concerns.
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.
Avoid
- 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.