Claude Skills by tools-only

Define types inside the scope of another type. Enumerations are often created to support a specific class or structure's functionality. Similarly, it can be convenient to define utility structures purely for use within the context of a more complex type, and protocols that are normally used in conjunction with a specific type. To accomplish this, Swift enables you to define *nested types*, whereby you nest supporting types like enumerations, structures, and protocols within the definition of ...

- Contract uses `require()` statements for input or state validation - The `require` condition is overly restrictive (rejects valid inputs) or too loose (accepts invalid inputs) - OR: `require()` validates return values from external contracts whose behavior doesn't match assumptions

- Contract uses low-level calls: `.call()`, `.send()`, or `.delegatecall()` - The boolean return value indicating success/failure is not checked - State changes occur after the unchecked call, assuming it succeeded

```bash python scripts/run.py [script].py [args...] ```

> Tier 3 reference. Load on demand when handling complex or ambiguous exceptions that don't resolve through standard workflows. These edge cases represent the scenarios that separate experienced exception management professionals from everyone else. Each one involves competing claims, ambiguous liability, time pressure, and real financial exposure. They are structured to guide resolution when standard playbooks break down. ---

> Tier 3 reference. Load on demand when handling complex or ambiguous return situations that don't resolve through standard workflows. These edge cases represent the scenarios that separate experienced returns operations managers from everyone else. Each involves competing interests, ambiguous liability, policy grey areas, and real financial or regulatory exposure. They are structured to guide resolution when standard playbooks break down. ---

> Tier 3 reference. Load on demand when handling complex or ambiguous production scheduling situations that don't resolve through standard sequencing and dispatching workflows. These edge cases represent the scenarios that separate experienced production schedulers from everyone else. Each one involves competing constraints, imperfect data, time pressure, and real operational exposure. They are structured to guide decision-making when standard scheduling rules break down. ---

> Tier 3 reference. Load on demand when handling complex carrier management situations that don't resolve through standard decision frameworks. These edge cases represent the scenarios that separate experienced transportation managers from everyone else. Each involves competing priorities, incomplete information, relationship dynamics, and real financial exposure. They are structured to guide resolution when standard carrier management playbooks break down. ---

> Tier 3 reference. Load on demand when handling complex or ambiguous trade compliance situations that don't resolve through standard workflows. These edge cases represent the scenarios that separate experienced trade compliance professionals from everyone else. Each one involves competing regulatory frameworks, ambiguous fact patterns, multi-jurisdictional complexity, and real financial exposure. They are structured to guide resolution when standard procedures break down. ---

This reference provides the detailed decision logic, scoring matrices, financial models, and mode-specific resolution workflows for logistics exception management. It is loaded on demand when the agent needs to make or recommend nuanced exception-handling decisions. All thresholds, timelines, and cost assumptions reflect US domestic and international freight operations across LTL, FTL, parcel, intermodal, ocean, and air modes. ---

This reference provides the detailed decision logic, classification methodology, FTA qualification decision trees, customs valuation methods, restricted party screening protocols, and penalty risk assessment frameworks for customs and trade compliance operations. All thresholds, timelines, and regulatory references reflect multi-jurisdictional trade operations covering US, EU, UK, and key Asia-Pacific markets. Regulatory citations are current as of 2024 but must be verified against the latest...

This reference provides the detailed decision logic, scoring matrices, financial models, grading standards, and disposition workflows for returns and reverse logistics operations. It is loaded on demand when the agent needs to make or recommend nuanced return-handling decisions. All thresholds, timelines, and cost assumptions reflect US retail and e-commerce operations with applicability to omnichannel, pure-play e-commerce, and brick-and-mortar environments. ---

The Strands community has built tools and integrations for a variety of use cases. This catalog helps you discover what's available and find packages that solve your specific needs. Browse by category below to find tools, model providers, session managers, and platform integrations built by the community. !!! info "Community maintained" These packages are maintained by their authors, not the Strands team. Review packages before using them in production. Quality and support may vary.

[← Back to Main README](../README.md) *965 skills in this domain* [](https://github.com/Chat2AnyLLM/awesome-claude-skills) [](https://github.com/Chat2AnyLLM/awesome-claude-agents) [](https://github.com/Chat2AnyLLM/awesome-claude-plugins) ...

[← Back to Main README](../README.md) *1238 skills in this domain* [](https://github.com/Chat2AnyLLM/awesome-claude-skills) [](https://github.com/Chat2AnyLLM/awesome-claude-agents) [](https://github.com/Chat2AnyLLM/awesome-claude-plugins)...

**Total Skills:** 61

**Total Skills:** 4

**Total Skills:** 13

**Total Skills:** 74

Effective treatment goals are the cornerstone of successful patient care. This reference provides comprehensive guidance on creating SMART goals, patient-centered outcome selection, and shared decision-making processes for treatment planning across all medical specialties.

**REPO OWNER**: Do you want Customer Service & Support (CSS) support for this product/project? - **No CSS support:** Fill out this template with information about how to file issues and get help. - **Yes CSS support:** Fill out an intake form at [aka.ms/onboardsupport](https://aka.ms/onboardsupport). CSS will work with/help you to determine next steps. - **Not sure?** Fill out an intake as though the answer were "Yes". CSS will help you decide. *Then remove this first heading from this SUPPOR...

Software architecture specialist for Next.js/Supabase SaaS systems. Use PROACTIVELY when planning new features, designing database schemas, evaluating multi-tenant patterns, or making architectural decisions. Key capabilities: trade-off analysis, route/service/component design, multi-tenant data modeling, package boundary evaluation. Trigger phrases: 'design the schema', 'evaluate this architecture', 'plan the data model', 'what's the best approach for'. Do NOT use for implementation — use bu...

FIRE framework for infrastructure diagnosis and DevOps workflows with Claude Code

**Date**: 2026-02-19 **Evaluator**: Claude Sonnet 4.6 **Source Type**: LinkedIn post (promotional, personal testimonial) **URL**: https://www.linkedin.com/posts/activity-7428930570451083264-I3Pa **Author**: Unknown (LinkedIn member, anonymous for evaluation purposes) **Verdict**: MARGINAL (Score: 2/5) ---

Extracts transferable visual DNA (palette/material cues) from selected images.

**Date**: 2026-02-07 **Source**: LinkedIn Post **URL**: https://www.linkedin.com/posts/mathieugrenier_anthropic-llm-automation-activity-7292595622816829440-Bvsd **Author**: Mathieu Grenier (Staff Eng + Growth @ MosaicML/Databricks, ex-Shopify) **Type**: LinkedIn post (short-form critique) **Evaluator**: Claude Sonnet 4.5 (via SuperClaude framework) **Score**: 3/5 (Moderate Value - Integrate when time available) ---

Extracts emotional/style signature tokens from selected images.

Test-Driven Development workflow with explicit prompting for red-green-refactor cycles

Updated: 2026-02-26T00:00:00Z | IaC: Terraform | Branch: tf-dev

   <details open> <summary><strong>📑 Requirements Overview</strong></summary> - [🎯 Project Overview](#-project-overview) - [🚀 Functional Requirements](#-functional-requirements) - [⚡ Non-Functional Requirements (NFRs)](#-non-functional-requirements-nfrs)...

   > Generated by design agent | 2026-02-26 <details open> <summary><strong>📑 Decision Contents</strong></summary> - [🔍 Context](#-context) - [✅ Decision](#-decision) - [🔄 Alternatives Considered](#-alternatives-considered) - [⚖️ Consequences](#%EF%B8%8F-consequences) ...

   <details open> <summary><strong>📑 As-Built Cost Contents</strong></summary> - [💵 Cost At-a-Glance](#-cost-at-a-glance) - [✅ Decision Summary](#-decision-summary) - [🔁 Requirements → Cost Mapping](#-requirements--cost-mapping) - [📊 Top 5 Cost Drivers](#-top-5-c...

Transform meeting transcripts and notes into structured, actionable insights that connect to existing project context. ---

The directory layout that works for product manager projects. ---

We are proud to announce **Lár v1.1**, the "Metacognition Update". This release introduces Level 4 Agency capabilities, allowing agents to modify their own execution logic at runtime while maintaining strict "Glass Box" compliance.

**Status**: ✅ Completed **Created**: 2025-12-09 **Completed**: 2025-12-09 **Target Version**: v4.7.0

**For existing Navigator users running v3.3.1 or earlier** ---

**From**: v3.x **To**: v4.0.0 **Compatibility**: Fully backward compatible - zero breaking changes ---

Detailed configuration options and advanced patterns for using the Express adapter with AWS Lambda.

Better Auth supports passkey authentication through the `@better-auth/passkey` plugin. Passkeys provide passwordless authentication using biometrics (fingerprint, face recognition), device PIN, or physical security keys.

| File | Descrizione | |------|-------------| | `page.tsx` | Pagina pubblica accessibile tramite URL | | `layout.tsx` | Layout condiviso che wrappa i page | | `loading.tsx` | UI di caricamento durante fetch dati | | `error.tsx` | UI per gestione errori | | `not-found.tsx` | UI per 404 | | `template.tsx` | Layout re-mounted su navigazione | | `default.tsx` | Fallback per parallel routes | | `route.ts` | API Route Handler |

Next.js offre multiple strategie di caching: - **Request Memoization**: Deduplica fetch nello stesso render - **Data Cache**: Cache persistente tra request - **Full Route Cache**: Cache delle pagine statiche - **Router Cache**: Cache client-side delle route

Server Components eseguono sul server: - Zero JavaScript bundle size - Accesso diretto a database/API - Riduzione del tempo di hydration - Accesso a risorse server-side

This guide walks you through upgrading from ContextForge v0.6.0 to v0.7.0 that implements comprehensive multi-tenancy, team management, and RBAC.

This guide helps you to set up your local environment for contributing to the Model Context Protocol (MCP) Gateway. It provides detailed instructions for tooling requirements, OS-specific notes, common pitfalls, and commit signing practices.

This guide helps troubleshoot OAuth 2.0 authentication problems when registering MCP servers, particularly the "Invalid or expired state parameter" error. ---

ContextForge supports multiple database backends with full feature parity across all supported systems.

!!! warning "Experimental Feature" gRPC support is an **experimental opt-in feature** that is disabled by default. It requires additional dependencies and explicit enablement. ContextForge supports automatic translation of gRPC services into MCP tools via the gRPC Server Reflection Protocol. This enables seamless integration of gRPC microservices into your MCP ecosystem without manual schema definition.

!!! warning "Security Warning" Query parameter authentication is **inherently insecure** (CWE-598). API keys in URLs may appear in proxy logs, browser history, and server access logs. Only use this authentication method when the upstream MCP server **requires** it (e.g., Tavily MCP).

> **Back to [Style Guide](../mermaid_style_guide.md)** — Read the style guide first for emoji, color, and accessibility rules. **Syntax keyword:** `stateDiagram-v2` **Best for:** State machines, lifecycle flows, status transitions, object lifecycles **When NOT to use:** Sequential processes with many steps (use [Flowchart](flowchart.md)), timing-critical interactions (use [Sequence](sequence.md)) ---