Loading...
Loading...
Found 6,268 Skills
Domain-oriented architecture for Laravel without external package dependencies, based on concepts from "Laravel Beyond CRUD" (Spatie). Use this skill when the user wants to structure a Laravel project using DDD, domain-oriented architecture, or organize code by business concepts instead of technical properties. Also activate when the user asks about: Actions, Data Objects (DTOs), lean models, States with enums, ViewModels (Blade or API), HTTP Query builders, application layer, or scaling Laravel projects beyond simple CRUD. Activate for any mention of "domain layer", "application layer", "beyond CRUD", "domain-oriented", or requests to refactor a Laravel project into domain structure. Even if the user asks "how to organize a large Laravel project", this skill is relevant.
Modern Python tooling best practices using uv, ruff, ty, and pytest. Mandates the Trail of Bits Python coding standards for project setup, dependency management, linting, type checking, and testing. Based on patterns from trailofbits/cookiecutter-python.
Query Developer Experience (DX) data via the DX Data MCP server PostgreSQL database. Use this skill when analyzing developer productivity metrics, team performance, PR/code review metrics, deployment frequency, incident data, AI tool adoption, survey responses, DORA metrics, or any engineering analytics. Triggers on questions about DX scores, team comparisons, cycle times, code quality, developer sentiment, AI coding assistant adoption, sprint velocity, or engineering KPIs.
Fetches Andrej Karpathy's curated RSS feed, reads ALL original articles, and generates a themed daily briefing document with citation links. This skill should be used when the user asks to generate a Karpathy RSS daily report, fetch Karpathy's curated RSS updates, or create an AI/tech daily briefing based on Karpathy's sources. Trigger phrases include "Karpathy Daily Report", "Karpathy RSS", "Generate Daily Report", "RSS Briefing", "Karpathy Daily".
Project development lifecycle management with a strict three-phase workflow (investigate -> proposal -> implement), file-based plan tracking in docs/plan/, task tracking in docs/task/, and claim-before-work multi-agent coordination. Use when handling feature development, bug fixes, refactors, planning, progress tracking, or multi-agent execution in an existing codebase. Supports English and Chinese project templates.
Generate technical design documents using a standard template and save them to a group Yuque knowledge base. For group use — stores designs in group repos with review workflow. Requires group Token.
Discover connections between documents, build knowledge networks, and establish bidirectional links across your personal Yuque knowledge base. For personal/individual use — operates on your own docs.
Manage a structured task list using a Markdown file in the workspace. Track progress on complex multi-step tasks. File-based — just Read and Write the todo file.
Integrate Geist fonts in Svelte 4/5 and SvelteKit projects using `geist-svelte`. Use when users ask for Geist Sans, Geist Mono, or Geist Pixel variants, need setup with Tailwind v4 or v3, want CSS variable usage without Tailwind, need import/config troubleshooting, or want migration from manual `@font-face` setup to package-based Geist fonts.
Best practices for developing tools, dashboards and interactive data apps with HoloViz Panel. Create reactive, component-based UIs with widgets, layouts, templates, and real-time updates. Use when developing interactive data exploration tools, dashboards, data apps, or any interactive Python web application. Supports file uploads, streaming data, multi-page apps, and integration with HoloViews, hvPlot, Pandas, Polars, DuckDB and the rest of the HoloViz and PyData ecosystems.
Research CVEs and security advisories for project dependencies. Uses Exa, NVD API, OSV.dev, and GitHub Advisory Database to find known vulnerabilities.
Provides comprehensive code review capability for NestJS applications, analyzing controllers, services, modules, guards, interceptors, pipes, dependency injection, and database integration patterns. Use when reviewing NestJS code changes, before merging pull requests, after implementing new features, or for architecture validation. Triggers on "review NestJS code", "NestJS code review", "check my NestJS controller/service".