spatie-javascript
Apply Spatie's JavaScript coding standards for any task that creates, edits, reviews, refactors, or formats JavaScript or TypeScript code; use for variable declarations, comparisons, functions, destructuring, and Prettier configuration to align with Spatie's JS conventions.
Works with
--- name: spatie-javascript description: Apply Spatie's JavaScript coding standards for any task that creates, edits, reviews, refactors, or formats JavaScript or TypeScript code; use for variable declarations, comparisons, functions, destructuring, and Prettier configuration to align with Spatie's JS conventions. license: MIT --- # Spatie JavaScript Guidelines ## Overview Apply Spatie's JavaScript coding standards to keep JS/TS code consistent and readable. ## When to Activate - Activate this skill for any JavaScript or TypeScript coding work. - Activate this skill when working on `.js`, `.ts`, `.jsx`, `.tsx`, or `.vue` files. - Activate this skill when configuring Prettier for a project. ## Scope - In scope: JavaScript, TypeScript, Vue single-file components, Prettier configuration. - Out of scope: PHP, Laravel, CSS-only files, server configuration. ## Workflow 1. Identify the JavaScript, TypeScript, Vue, or Prettier artifact being changed. 2. Read `references/spatie-javascript-guidelines.md` and focus on the relevant sections. 3. Apply Prettier configuration first, then the language rules relevant to the change. ## Core Rules (Summary) - Use four-space indentation, a 120-character print width, and single quotes. - Prefer `const`, use `let` only for reassignment, and never use `var`. - Avoid abbreviated variable names except in clear single-line arrow functions. - Always use strict equality and cast values before comparing different types. - Use `function` for declarations and arrow functions for anonymous or terse functions when appropriate. - Keep functions pure, limit `this`, and use shorthand object methods. - Prefer object and array destructuring. ## References - `references/spatie-javascript-guidelines.md`
More Refactoring skills
vercel-react-best-practices
vercel-labs/agent-skills
React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
analyze-project
lllllllama/rigorpilot-skills
Rigor Analyze / Rigor Audit read-only skill for deep learning research repositories. Use when the user wants to read and understand a repository, inspect model structure and training or inference entrypoints, review configs and insertion points, or flag suspicious implementation patterns without modifying code or running heavy jobs. Do not use for active command execution, broad refactoring, speculative code adaptation, or automatic bug fixing.
request-refactor-plan
mattpocock/skills
Create a detailed refactor plan with tiny commits via user interview, then file it as a GitHub issue. Use when user wants to plan a refactor, create a refactoring RFC, or break a refactor into safe incremental steps.

