Daily workflow

Skill soden46/syarif-laravel-ai-skills/skills/daily-workflow

Practical daily checklist for Laravel projects; bring services up, run migrations, queues, quality gates, and testsFrom its SKILL.md

Install

npx -y skills add soden46/syarif-laravel-ai-skills --skill daily-workflow

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

4 stars4 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

1.9 KB, 343 tokens by cl100k_base, as published. Nobody here has run it

Daily Workflow

Use this skill when a Laravel task involves daily workflow.

This skill is adapted to the personal Laravel standards in this repository. It maps the public daily-workflow topic from jpcaparas/superpowers-laravel into the local daily-workflow 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 automation workflows skills give in 343 tokens

Counted across 813 of the 1,214 authors here whose files we hold, read 2026-09-06

Use conventional commit message formatin 38 of 813, across 34 files
Write tests before implementing codein 26 of 813, across 12 files
Achieve at least 80 percent test coveragein 24 of 813, across 11 files
Mock external dependencies for unit testsin 22 of 813, across 10 files
Read product marketing context before asking questionsin 21 of 813, across 6 files
Implement rollback plans for every deploymentin 21 of 813, across 9 files
Follow the arrange-act-assert patternin 20 of 813, across 9 files
Delete branches after mergingin 20 of 813, across 18 files
Test all edge cases and error scenariosin 20 of 813, across 8 files
Use semantic selectors for UI testsin 19 of 813, across 7 files
Define sequence type and audience contextin 18 of 813, across 5 files
Monitor feature drift and prediction distribution driftin 18 of 813, across 5 files

Said here and by no other author read

Detect Laravel and PHP versions
Identify overlapping local skill sets
Use Laravel native APIs first
Add abstractions only to reduce complexity
Run targeted tests before handoff
Keep controllers focused on HTTP orchestration

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.