Loading...
Loading...
Found 6,222 Skills
Multi-tenant application architecture patterns. Use when working with multi-tenant systems, tenant isolation, or when user mentions multi-tenancy, tenants, tenant scoping, tenant isolation, multi-tenant.
GitHub AI-powered security and automation features for 2025
Score assistant responses for clarity on a strict 1-5 scale, then return strict JSON only with score, rationale, and improvement suggestions. Use when the user asks to evaluate clarity, grade clarity, or critique clarity quality.
PostgreSQL-specific schema design, types, and DDL patterns.
Create GitHub Pull Request for feature request from specification file using pull_request_template.md template.
Generate high-divergence, out-of-the-box analysis plans and prompts that counter anchoring, mode collapse, and context bias while staying practical. Use when requests ask for unconventional strategies, non-obvious options, radical reframing, MCP-assisted synthesis across prior messages/sources, or "think differently" outputs that still require executable next steps.
Code comment guidelines. Remove redundant comments, add strategic ones explaining WHY not WHAT. Applied automatically when modifying code.
Swift/iOS static analysis CLI. Use `depgraph` to find who calls a function, what breaks if you change a file, track call sites and blast radius before refactoring, and map symbol dependencies across files. Use `ask` to consult Swift/iOS/tvOS/watchOS/macOS documentation and best practices.
Detects .NET intent for any C#, ASP.NET Core, EF Core, Blazor, MAUI, Uno Platform, WPF, WinUI, SignalR, gRPC, xUnit, NuGet, or MSBuild request from prompt keywords and repository signals (.sln, .csproj, global.json, .cs files). First skill to invoke for all .NET work — loads version-specific coding standards and routes to domain skills via [skill:dotnet-advisor] before any planning or implementation. Do not use for clearly non-.NET tasks (Python, JavaScript, Go, Rust, Java).
Command: sync-testing-skill
Generate a "Journey Into [Project]" narrative report analyzing a project's entire development history from claude-mem's timeline. Use when asked for a timeline report, project history analysis, development journey, or full project report.
Persistent markdown files as working memory for complex tasks: plan, track progress, store findings. Use when tasks have 3+ phases, require research, span many tool calls, or risk context drift. Use for "plan", "break down", "track progress", "multi-step", or complex tasks. Do NOT use for simple lookups, single-file edits, or questions answerable in one response.