Config env storage

Skill soden46/syarif-laravel-ai-skills/skills/config-env-storage

Laravel guidance to portable storage configuration across S3/R2/MinIO with optional CDN-env toggles, path-style endpoints, and URL generationFrom its SKILL.md

Install

npx -y skills add soden46/syarif-laravel-ai-skills --skill config-env-storage

Assembled from the repository path, not quoted from the project. Check it against their README if it does not work.

One thing to look at

3 stars3 stars. Stars are a popularity signal and not a quality one, but at this level it is likely that nobody has read this closely except its author, and you would be relying on your own review.

SKILL.md

2.0 KB, 345 tokens by cl100k_base, as published. Nobody here has run it

Config Env Storage

Use this skill when a Laravel task involves config env storage.

This skill is adapted to the personal Laravel standards in this repository. It maps the public config-env-storage topic from jpcaparas/superpowers-laravel into the local config-env-storage catalog without copying third-party skill body text.

Syarif Defaults

Follow Laravel conventions before introducing custom abstractions.
Prefer project-local patterns when they are explicit and tested.
Keep controllers focused on HTTP orchestration.
Put validation, authorization, transactions, side effects, and integrations at clear boundaries.
Keep client names, credentials, internal URLs, provider secrets, and project-specific business rules out of reusable standards.
Verify important behavior with the smallest meaningful tests and quality checks.

Workflow

Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
Identify the smallest local skill set that overlaps this topic.
Implement or review the change using Laravel-native APIs first.
Add abstractions only when they reduce real complexity or protect a meaningful boundary.
Run targeted tests and available quality checks before handoff.

Checkpoints

Authorization and validation boundaries are explicit.
Query shape, transactions, queues, cache, files, and external calls are intentional when touched.
User-facing behavior has feature, unit, browser, or integration tests at the right level.
Logs and errors are useful without exposing secrets or unnecessary personal data.
Documentation or proposals avoid importing source-project names or one-off business rules.

Related Skills

using-laravel-standards
architecture
testing
security

What ships with it

Read from the repository

Just SKILL.md. No reference files, no scripts.

Gives 0 of the 12 instructions most project setup skills give in 345 tokens

Counted across 1,553 of the 3,091 authors here whose files we hold, read 2026-09-06

Write the configuration filein 36 of 1553
Create the directory structurein 35 of 1553, across 33 files
Verify the setupin 31 of 1553, across 28 files
Run the setup scriptin 30 of 1553, across 29 files
Pre-determine the required sample sizein 29 of 1553, across 12 files
Check if the configuration already existsin 29 of 1553
Document every testin 26 of 1553, across 10 files
Start with a hypothesisin 26 of 1553, across 11 files
Ask one question at a timein 22 of 1553
Test a single variable per testin 21 of 1553, across 9 files
Read product marketing context before asking questionsin 19 of 1553, across 8 files
Do not peek and stop earlyin 18 of 1553, across 7 files

Said here and by no other author read

Follow Laravel conventions before introducing custom abstractions
Keep controllers focused on HTTP orchestration
Detect the Laravel version and PHP version
Implement the change using Laravel-native APIs first
Run targeted tests before handoff
Prefer project-local patterns when explicit and tested

Grouped from the skills themselves: near-identical wordings counted once, and counted by distinct author, so one author publishing three of these counts once. Length counted with cl100k_base; the agent that loads this file may tokenize it differently.