Loading...
Loading...
Found 955 Skills
Audit Lightning Web Components for SLDS compliance and produce a scored quality report. Runs the SLDS linter, analyzes CSS for theming hook usage and pairing, checks HTML for accessibility attributes, and scores findings across categories into an overall grade. Use when asked to "score my component", "SLDS scorecard", "quality report", "audit SLDS compliance", "how good is my SLDS", "check component quality", "rate my component", "evaluate my component", "is this component ready to ship?", "look at my LWC for issues", "audit this before I submit", "review my component before code review", or any time a user wants a quality assessment or production-readiness check on an LWC or SLDS component. Not for fixing violations (use uplifting-components-to-slds2) or building new components (use applying-slds).
Pre-flight before creating a pull request: run `greptile review` on the committed branch, VERIFY the review actually matches this branch's diff, triage its findings, apply safe fixes (propose risky ones), and only then `gh pr create`. Runs in repos where greptile is configured. Trigger ONLY on explicit PR-creation intent: "crea el PR", "create the PR", "abrí el PR", "open a PR", or immediately before a `gh pr create`. Do NOT fire on a bare commit.
Best practices for working with Cursor. Use when learning how to effectively use Cursor features or optimizing your workflow.
Run a comprehensive code review
Use when preparing branches, commits, or PRs for Python changes — scoping work, running validation gates, and ensuring merge readiness. Also use when debugging CI gate failures, resolving lockfile conflicts, or uncertain what checks to run before opening a PR.
Systematic debugging that identifies root causes rather than treating symptoms. Uses sequential thinking for complex analysis, web search for research, and structured investigation to avoid circular reasoning and whack-a-mole fixes.
This skill guides systematic code refactoring following the DRY (Don't Repeat Yourself) principle. Use it when users request to eliminate code duplication, refactor repetitive code, apply the DRY principle, or mention code smells like copy-paste code, magic numbers, or repeated logic. It implements a 4-step workflow from identifying repetition to verified refactoring.
L3 Worker. Analyzes single pattern implementation, calculates 4 scores (compliance, completeness, quality, implementation), identifies gaps and issues. Usually invoked by ln-640, can also analyze a specific pattern on user request.
Comprehensive pre-merge validation checklist for Python/React pull requests. Use before approving or merging any PR. Covers code quality checks (linting, formatting, type checking), test coverage requirements, documentation updates, migration safety, API contract compatibility, accessibility compliance, bundle size impact, and deployment readiness. Provides a systematic checklist that ensures nothing is missed before merge. Does NOT cover security review depth (use code-review-security).
Socratic code review using probing questions instead of direct critique. Based on Feynman's principle that teaching reveals gaps in understanding. Helps developers articulate reasoning, surface hidden assumptions, and discover issues themselves.
Systematic 4-phase debugging with root cause investigation. Use when fixing bugs to prevent random fixes.
Test-Driven Development with Iron Laws enforcement. Use when writing any production code to ensure tests are written first. Includes testing-expert capabilities.