agentsclimarketplace
Sign in

Performance caching

Skill soden46/syarif-laravel-ai-skills/skills/performance-caching

Laravel guidance to use framework caches and value/query caching to reduce work; add tags, locks, and explicit invalidation strategies for correctnessFrom its SKILL.md

Install
npx -y skills add soden46/syarif-laravel-ai-skills --skill performance-caching

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, 344 tokens by cl100k_base, as published. Nobody here has run it

Performance Caching

Use this skill when a Laravel task involves performance caching.

This skill is adapted to the personal Laravel standards in this repository. It maps the public performance-caching topic from jpcaparas/superpowers-laravel into the local performance-caching 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

  1. Detect the Laravel version, PHP version, runner, package manager, and existing project conventions.
  2. Identify the smallest local skill set that overlaps this topic.
  3. Implement or review the change using Laravel-native APIs first.
  4. Add abstractions only when they reduce real complexity or protect a meaningful boundary.
  5. 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 caching build skills give in 344 tokens

Counted across 103 of the 134 authors here whose files we hold, read 2026-09-06

  • Prefer App Router and server componentsin 12 of 103, across 7 files
  • Stay on a recent Next.js 16.x releasein 12 of 103, across 7 files
  • Use the Bundle Analyzer to trim large dependenciesin 12 of 103, across 7 files
  • Use Turbopack for day-to-day developmentin 11 of 103, across 6 files
  • Fall back to webpack only for Turbopack bugs or webpack-only pluginsin 11 of 103, across 6 files
  • Set a TTL on every cache entryin 10 of 103, across 9 files
  • Check the official docs for your Next.js versionin 9 of 103, across 5 files
  • Ensure the cache is not cleared unnecessarilyin 8 of 103, across 4 files
  • Verify Turbopack is active when dev is slowin 8 of 103, across 4 files
  • Run next dev for local developmentin 7 of 103, across 6 files
  • Run next dev for local development with Turbopackin 6 of 103, across 2 files
  • Append static extensions to dynamic URLs to trigger cachingin 6 of 103, across 3 files

Said here and by no other author read

  • Use framework caches to reduce work
  • Add cache tags, locks, and invalidation strategies
  • Detect Laravel and PHP versions and conventions
  • Use Laravel-native APIs first
  • Follow Laravel conventions before custom abstractions
  • Add abstractions only when they reduce complexity

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.

Keep looking

Skills are one crate of 325,949. Ordering is by how many stacks a row turns up in, so the top of any crate is what has actually been picked rather than what has the most stars.