[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"skill:01M7DPSFZXWNCRYGRBNJ325FH8":3,"skill-same:01M7DPSFZXWNCRYGRBNJ325FH8":57},{"skillNo":4,"name":5,"nameZh":6,"description":7,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":16,"categories":17,"keywords":18,"publishedAt":19,"linkOnly":20,"markdownContent":21,"markdownBody":22,"frontMatter":23,"refName":30,"commitSha":31,"skillDirectory":32,"forksCount":33,"repositoryHtmlUrl":34,"repositoryHomepageUrl":6,"ownerHtmlUrl":35,"ownerBlogUrl":6,"ownerDescription":6,"updatedAt":36,"install":37,"resources":50},"01M7DPSFZXWNCRYGRBNJ325FH8","sdk-dx",null,"Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: \"SDK design\",...","Hazek-dc\u002FPresensiGuru_FaceNet_EMAR","Hazek-dc","https:\u002F\u002Favatars.githubusercontent.com\u002Fu\u002F75208960?v=4","01M7DEQV5B4YGS86A81DYH81DR","Hazek","01M7DEQV5XP4TM0C6NTHXCXCHR",1,"MIT","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdk-dx\u002FSKILL.md",[],[],"2026-11-15 14:19:17",false,"---\nname: sdk-dx\ndescription: 'Design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: \"SDK design\",...'\nrisk: unknown\nsource: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsdk-dx\nsource_repo: jonathimer\u002Fdevmarketing-skills\nsource_type: community\ndate_added: 2026-07-01\nlicense: MIT\nlicense_source: https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE\n---\n\n# SDK Design and Developer Experience\n## When to Use\n\nUse this skill when you need design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: \"SDK design\",...\n\n\nThe best SDK marketing is an SDK that developers can't stop talking about. When your SDK makes developers feel productive and competent, they become your advocates. When it frustrates them, no amount of marketing will save you.\n\n## Overview\n\nSDK developer experience (DX) encompasses everything a developer feels when using your library:\n- **Discovery**: How easily can they find and install it?\n- **Learning**: How quickly can they understand how to use it?\n- **Using**: How productive are they day-to-day?\n- **Debugging**: How easily can they fix problems?\n- **Upgrading**: How painlessly can they adopt new versions?\n\nGreat SDK DX is a competitive advantage. Developers choose tools that make them feel smart.\n\n## Before You Start\n\nReview the **developer-audience-context** skill to understand:\n- What languages and frameworks do your target developers use?\n- What IDE\u002Feditor setups are most common?\n- What's their experience level with your problem domain?\n- What competing SDKs have they used? What do they like\u002Fdislike?\n\nSDK design decisions should flow from deep understanding of your users.\n\n## API Design Principles\n\n### Principle 1: Optimize for the Common Case\n\nThe most frequent use case should require the least code.\n\n**Good Design:**\n```python\n# Common case: send a simple message\nclient.messages.send(\"Hello world\", to=\"+1234567890\")\n\n# Full control when needed\nclient.messages.send(\n    body=\"Hello world\",\n    to=\"+1234567890\",\n    from_=\"+0987654321\",\n    status_callback=\"https:\u002F\u002F...\",\n    media_urls=[\"https:\u002F\u002F...\"]\n)\n```\n\n**Bad Design:**\n```python\n# Every call requires full configuration\nmessage = Message(\n    body=\"Hello world\",\n    to=PhoneNumber(\"+1234567890\"),\n    from_=PhoneNumber(config.get_default_from()),\n    options=MessageOptions(\n        status_callback=None,\n        media_urls=[]\n    )\n)\nclient.messages.send(message)\n```\n\n### Principle 2: Progressive Disclosure\n\nStart simple, reveal complexity as needed.\n\n```javascript\n\u002F\u002F Level 1: Simplest possible usage\nconst result = await client.analyze(\"Hello world\");\n\n\u002F\u002F Level 2: Common options\nconst result = await client.analyze(\"Hello world\", {\n  language: \"en\",\n  features: [\"sentiment\", \"entities\"]\n});\n\n\u002F\u002F Level 3: Full control\nconst result = await client.analyze(\"Hello world\", {\n  language: \"en\",\n  features: [\"sentiment\", \"entities\"],\n  model: \"v2-large\",\n  timeout: 30000,\n  retries: { max: 3, backoff: \"exponential\" }\n});\n```\n\n### Principle 3: Fail Fast and Clearly\n\nCatch errors as early as possible, with actionable messages.\n\n**Good:**\n```python\n# Validation at construction time\nclient = MyClient(api_key=\"\")\n# Raises immediately: ValueError: API key cannot be empty.\n# Get your API key at https:\u002F\u002Fdashboard.example.com\u002Fkeys\n\n# Clear error at runtime\nclient.users.get(\"invalid-id\")\n# Raises: NotFoundError: User 'invalid-id' not found.\n# Use client.users.list() to see available users.\n```\n\n**Bad:**\n```python\nclient = MyClient(api_key=\"\")  # No validation\nresult = client.users.get(\"invalid-id\")\n# Returns: None (is this an error? empty result? who knows?)\n# Or worse: raises generic Exception with stack trace\n```\n\n### Principle 4: Sensible Defaults\n\nDefault values should work for most cases without configuration.\n\n```javascript\n\u002F\u002F This should just work without configuration\nconst client = new MyClient({ apiKey: process.env.MY_API_KEY });\n\n\u002F\u002F Sensible defaults:\n\u002F\u002F - Automatic retries with exponential backoff\n\u002F\u002F - Reasonable timeouts\n\u002F\u002F - JSON content type\n\u002F\u002F - Standard auth headers\n\u002F\u002F - Connection pooling\n```\n\n## Error Messages That Guide\n\nError messages are documentation. Make them helpful.\n\n### The Error Message Framework\n\nEvery error message should answer:\n1. **What** happened?\n2. **Why** did it happen?\n3. **How** do I fix it?\n\n### Good vs. Bad Error Messages\n\n**Good:**\n```\nAuthenticationError: Invalid API key provided.\n\nThe API key 'sk_test_abc...' (test key) cannot be used for\nproduction requests.\n\nTo fix this:\n1. Go to https:\u002F\u002Fdashboard.example.com\u002Fkeys\n2. Copy your production API key (starts with 'sk_live_')\n3. Update your environment variable: MY_API_KEY=sk_live_...\n\nDocs: https:\u002F\u002Fdocs.example.com\u002Fauthentication\n```\n\n**Bad:**\n```\nError: 401 Unauthorized\n```\n\n### Error Types to Distinguish\n\nCreate specific error types that developers can catch:\n\n```python\nfrom myapi.errors import (\n    AuthenticationError,  # Invalid\u002Fmissing credentials\n    AuthorizationError,   # Valid creds, insufficient permissions\n    ValidationError,      # Invalid input data\n    NotFoundError,        # Resource doesn't exist\n    RateLimitError,       # Too many requests\n    ServerError,          # Our fault, retry might help\n)\n\ntry:\n    client.users.get(user_id)\nexcept NotFoundError as e:\n    # Handle missing user specifically\nexcept AuthenticationError as e:\n    # Handle auth issues specifically\nexcept MyAPIError as e:\n    # Catch-all for other API errors\n```\n\n### Include Context in Errors\n\n```javascript\n\u002F\u002F Bad: generic error\nthrow new Error(\"Invalid parameter\");\n\n\u002F\u002F Good: contextual error\nthrow new ValidationError({\n  message: \"Invalid phone number format\",\n  field: \"to\",\n  value: \"+1abc\",\n  expected: \"E.164 format (e.g., +14155551234)\",\n  docs: \"https:\u002F\u002Fdocs.example.com\u002Fphone-numbers\"\n});\n```\n\n## Type Safety\n\nType safety is documentation that never goes stale.\n\n### TypeScript Best Practices\n\n```typescript\n\u002F\u002F Define explicit types for all inputs and outputs\ninterface User {\n  id: string;\n  email: string;\n  name: string;\n  createdAt: Date;\n  metadata?: Record\u003Cstring, unknown>;\n}\n\ninterface CreateUserInput {\n  email: string;\n  name: string;\n  metadata?: Record\u003Cstring, unknown>;\n}\n\n\u002F\u002F Return types are explicit\nasync function createUser(input: CreateUserInput): Promise\u003CUser> {\n  \u002F\u002F ...\n}\n\n\u002F\u002F Use discriminated unions for responses\ntype ApiResponse\u003CT> =\n  | { success: true; data: T }\n  | { success: false; error: ApiError };\n```\n\n### Autocomplete-Driven Design\n\nDesign for IDE autocomplete:\n\n```typescript\n\u002F\u002F Good: autocomplete shows all options\nclient.messages.create({\n  to: \"+1...\",     \u002F\u002F IDE shows: (property) to: string\n  body: \"...\",    \u002F\u002F IDE shows: (property) body: string\n  \u002F\u002F User types 'me' and sees 'mediaUrls' autocomplete\n});\n\n\u002F\u002F Bad: requires memorization\nclient.send(\"messages\", { \u002F* what goes here? *\u002F });\n```\n\n### Enum and Literal Types\n\n```typescript\n\u002F\u002F Good: constrained values with autocomplete\ntype MessageStatus = \"queued\" | \"sending\" | \"sent\" | \"failed\";\n\ninterface Message {\n  status: MessageStatus;  \u002F\u002F IDE shows valid values\n}\n\n\u002F\u002F Bad: any string accepted\ninterface Message {\n  status: string;  \u002F\u002F No guidance, errors at runtime\n}\n```\n\n## IDE Integration\n\n### Make Discovery Easy\n\nStructure your SDK so IDE features help developers:\n\n```typescript\n\u002F\u002F Namespace methods logically\nclient.users.get(id)\nclient.users.list()\nclient.users.create(data)\nclient.users.update(id, data)\nclient.users.delete(id)\n\n\u002F\u002F After typing 'client.users.' the IDE shows all user operations\n```\n\n### JSDoc\u002FDocstrings Everywhere\n\n```typescript\n\u002F**\n * Creates a new user in your organization.\n *\n * @param input - The user details\n * @param input.email - Must be a valid email address\n * @param input.name - Display name (max 100 characters)\n * @returns The created user with generated ID\n * @throws {ValidationError} If email format is invalid\n * @throws {ConflictError} If email already exists\n *\n * @example\n * const user = await client.users.create({\n *   email: \"jane@example.com\",\n *   name: \"Jane Developer\"\n * });\n *\u002F\nasync createUser(input: CreateUserInput): Promise\u003CUser>\n```\n\n### Inline Examples\n\n```python\ndef send_message(self, body: str, to: str, **kwargs) -> Message:\n    \"\"\"\n    Send an SMS message.\n\n    Args:\n        body: The message content (max 1600 characters)\n        to: Recipient phone number in E.164 format\n\n    Returns:\n        Message object with ID and status\n\n    Example:\n        >>> message = client.messages.send(\n        ...     body=\"Hello from Python!\",\n        ...     to=\"+14155551234\"\n        ... )\n        >>> print(message.status)\n        'queued'\n    \"\"\"\n```\n\n## Versioning Strategy\n\n### Semantic Versioning\n\nFollow semver strictly:\n- **MAJOR**: Breaking changes (removal, signature changes)\n- **MINOR**: New features (backward compatible)\n- **PATCH**: Bug fixes (backward compatible)\n\n### What Constitutes a Breaking Change\n\n**Breaking changes (require major version bump):**\n- Removing a public method or property\n- Changing method signatures\n- Changing return types\n- Changing default behavior\n- Removing support for a language\u002Fruntime version\n\n**Not breaking (minor or patch):**\n- Adding new methods\n- Adding optional parameters\n- Deprecating (but not removing) features\n- Bug fixes that change incorrect behavior\n\n### Deprecation Process\n\n```python\nimport warnings\n\ndef old_method(self):\n    \"\"\"\n    .. deprecated:: 2.3.0\n       Use :meth:`new_method` instead. Will be removed in 3.0.0.\n    \"\"\"\n    warnings.warn(\n        \"old_method() is deprecated, use new_method() instead. \"\n        \"See migration guide: https:\u002F\u002Fdocs.example.com\u002Fmigrate-v3\",\n        DeprecationWarning,\n        stacklevel=2\n    )\n    return self.new_method()\n```\n\n## Migration Guides\n\n### Migration Guide Structure\n\n```markdown\n# Migrating from v2 to v3\n\n## Overview\nVersion 3 introduces [major change] and removes [deprecated feature].\nMigration typically takes [time estimate].\n\n## Breaking Changes\n\n### 1. Client Initialization\n**Before (v2):**\n```python\nclient = MyClient(key=\"...\")\n```\n\n**After (v3):**\n```python\nclient = MyClient(api_key=\"...\")\n```\n\n**Why**: Consistency with other SDK parameters.\n\n### 2. [Next breaking change]\n...\n\n## Deprecated Features Removed\n- `client.old_method()` - Use `client.new_method()` instead\n- `LegacyClass` - Use `ModernClass` instead\n\n## New Features\n- [Feature that makes migration worthwhile]\n\n## Need Help?\n- [Migration support channel]\n- [Office hours for migration questions]\n```\n\n### Codemods and Automation\n\nWhen possible, provide automated migration:\n\n```bash\n# Provide migration scripts\nnpx @myapi\u002Fmigrate-v3\n\n# Or codemods\nnpx jscodeshift -t @myapi\u002Fcodemods\u002Fv2-to-v3 src\u002F\n```\n\n## Making SDKs Feel Native\n\n### Language Idioms\n\n**Python**: Use snake_case, context managers, generators\n```python\n# Pythonic\nwith client.batch() as batch:\n    for user in client.users.list():\n        batch.add(user.send_notification(\"Hello\"))\n\n# Not Pythonic\nusers = client.getUsers()\nbatch = client.createBatch()\nfor i in range(len(users)):\n    batch.addOperation(users[i].sendNotification(\"Hello\"))\nbatch.execute()\n```\n\n**JavaScript**: Use Promises, async\u002Fawait, destructuring\n```javascript\n\u002F\u002F Idiomatic JS\nconst { data, error } = await client.users.get(id);\n\n\u002F\u002F Not idiomatic\nclient.users.get(id, function(err, result) {\n    if (err) { \u002F* callback hell *\u002F }\n});\n```\n\n**Go**: Use error returns, interfaces, channels\n```go\n\u002F\u002F Idiomatic Go\nuser, err := client.Users.Get(ctx, userID)\nif err != nil {\n    return fmt.Errorf(\"getting user: %w\", err)\n}\n\n\u002F\u002F Not idiomatic\nuser := client.Users.Get(userID)  \u002F\u002F panics on error\n```\n\n### Match Ecosystem Conventions\n\n- Use the package manager developers expect (npm, pip, gem, go get)\n- Follow naming conventions of popular libraries in that language\n- Integrate with popular frameworks (Express, Django, Rails)\n- Support popular testing patterns\n\n## SDK Quality Checklist\n\n### Before Release\n\n- [ ] All public APIs have documentation\n- [ ] All public APIs have types (where language supports)\n- [ ] Error messages include remediation steps\n- [ ] Code examples in docs are tested automatically\n- [ ] Changelog is updated with all changes\n- [ ] Migration guide for breaking changes\n- [ ] Deprecation warnings for removed features\n\n### For Great DX\n\n- [ ] Quickstart achieves success in \u003C 5 minutes\n- [ ] IDE autocomplete works for all operations\n- [ ] Errors are catchable by specific type\n- [ ] Retry logic handles transient failures\n- [ ] Logging is configurable and useful\n- [ ] Debug mode shows request\u002Fresponse details\n\n## Tools\n\n### SDK Generation\n- **OpenAPI Generator**: Generate SDKs from OpenAPI specs\n- **Swagger Codegen**: Alternative generator\n- **Speakeasy**: Modern SDK generation platform\n- **Fern**: Type-safe SDK generation\n\n### Testing\n- **VCR\u002FBetamax**: Record and replay HTTP interactions\n- **WireMock**: Mock HTTP services\n- **Pact**: Contract testing\n\n### Documentation\n- **TypeDoc**: TypeScript documentation\n- **Sphinx**: Python documentation\n- **GoDoc**: Go documentation\n- **YARD**: Ruby documentation\n\n## Related Skills\n\n- **docs-as-marketing**: Documentation that showcases SDK capabilities\n- **api-onboarding**: First experience with your SDK\n- **changelog-updates**: Communicating SDK changes effectively\n- **developer-sandbox**: Try SDK without installing\n- **developer-audience-context**: Understanding SDK users\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n","# SDK Design and Developer Experience\n## When to Use\n\nUse this skill when you need design SDKs that developers love to use—APIs that feel native, error messages that guide, and experiences that reduce friction. This skill covers creating SDKs that drive adoption through exceptional developer experience rather than aggressive marketing. Trigger phrases: \"SDK design\",...\n\n\nThe best SDK marketing is an SDK that developers can't stop talking about. When your SDK makes developers feel productive and competent, they become your advocates. When it frustrates them, no amount of marketing will save you.\n\n## Overview\n\nSDK developer experience (DX) encompasses everything a developer feels when using your library:\n- **Discovery**: How easily can they find and install it?\n- **Learning**: How quickly can they understand how to use it?\n- **Using**: How productive are they day-to-day?\n- **Debugging**: How easily can they fix problems?\n- **Upgrading**: How painlessly can they adopt new versions?\n\nGreat SDK DX is a competitive advantage. Developers choose tools that make them feel smart.\n\n## Before You Start\n\nReview the **developer-audience-context** skill to understand:\n- What languages and frameworks do your target developers use?\n- What IDE\u002Feditor setups are most common?\n- What's their experience level with your problem domain?\n- What competing SDKs have they used? What do they like\u002Fdislike?\n\nSDK design decisions should flow from deep understanding of your users.\n\n## API Design Principles\n\n### Principle 1: Optimize for the Common Case\n\nThe most frequent use case should require the least code.\n\n**Good Design:**\n```python\n# Common case: send a simple message\nclient.messages.send(\"Hello world\", to=\"+1234567890\")\n\n# Full control when needed\nclient.messages.send(\n    body=\"Hello world\",\n    to=\"+1234567890\",\n    from_=\"+0987654321\",\n    status_callback=\"https:\u002F\u002F...\",\n    media_urls=[\"https:\u002F\u002F...\"]\n)\n```\n\n**Bad Design:**\n```python\n# Every call requires full configuration\nmessage = Message(\n    body=\"Hello world\",\n    to=PhoneNumber(\"+1234567890\"),\n    from_=PhoneNumber(config.get_default_from()),\n    options=MessageOptions(\n        status_callback=None,\n        media_urls=[]\n    )\n)\nclient.messages.send(message)\n```\n\n### Principle 2: Progressive Disclosure\n\nStart simple, reveal complexity as needed.\n\n```javascript\n\u002F\u002F Level 1: Simplest possible usage\nconst result = await client.analyze(\"Hello world\");\n\n\u002F\u002F Level 2: Common options\nconst result = await client.analyze(\"Hello world\", {\n  language: \"en\",\n  features: [\"sentiment\", \"entities\"]\n});\n\n\u002F\u002F Level 3: Full control\nconst result = await client.analyze(\"Hello world\", {\n  language: \"en\",\n  features: [\"sentiment\", \"entities\"],\n  model: \"v2-large\",\n  timeout: 30000,\n  retries: { max: 3, backoff: \"exponential\" }\n});\n```\n\n### Principle 3: Fail Fast and Clearly\n\nCatch errors as early as possible, with actionable messages.\n\n**Good:**\n```python\n# Validation at construction time\nclient = MyClient(api_key=\"\")\n# Raises immediately: ValueError: API key cannot be empty.\n# Get your API key at https:\u002F\u002Fdashboard.example.com\u002Fkeys\n\n# Clear error at runtime\nclient.users.get(\"invalid-id\")\n# Raises: NotFoundError: User 'invalid-id' not found.\n# Use client.users.list() to see available users.\n```\n\n**Bad:**\n```python\nclient = MyClient(api_key=\"\")  # No validation\nresult = client.users.get(\"invalid-id\")\n# Returns: None (is this an error? empty result? who knows?)\n# Or worse: raises generic Exception with stack trace\n```\n\n### Principle 4: Sensible Defaults\n\nDefault values should work for most cases without configuration.\n\n```javascript\n\u002F\u002F This should just work without configuration\nconst client = new MyClient({ apiKey: process.env.MY_API_KEY });\n\n\u002F\u002F Sensible defaults:\n\u002F\u002F - Automatic retries with exponential backoff\n\u002F\u002F - Reasonable timeouts\n\u002F\u002F - JSON content type\n\u002F\u002F - Standard auth headers\n\u002F\u002F - Connection pooling\n```\n\n## Error Messages That Guide\n\nError messages are documentation. Make them helpful.\n\n### The Error Message Framework\n\nEvery error message should answer:\n1. **What** happened?\n2. **Why** did it happen?\n3. **How** do I fix it?\n\n### Good vs. Bad Error Messages\n\n**Good:**\n```\nAuthenticationError: Invalid API key provided.\n\nThe API key 'sk_test_abc...' (test key) cannot be used for\nproduction requests.\n\nTo fix this:\n1. Go to https:\u002F\u002Fdashboard.example.com\u002Fkeys\n2. Copy your production API key (starts with 'sk_live_')\n3. Update your environment variable: MY_API_KEY=sk_live_...\n\nDocs: https:\u002F\u002Fdocs.example.com\u002Fauthentication\n```\n\n**Bad:**\n```\nError: 401 Unauthorized\n```\n\n### Error Types to Distinguish\n\nCreate specific error types that developers can catch:\n\n```python\nfrom myapi.errors import (\n    AuthenticationError,  # Invalid\u002Fmissing credentials\n    AuthorizationError,   # Valid creds, insufficient permissions\n    ValidationError,      # Invalid input data\n    NotFoundError,        # Resource doesn't exist\n    RateLimitError,       # Too many requests\n    ServerError,          # Our fault, retry might help\n)\n\ntry:\n    client.users.get(user_id)\nexcept NotFoundError as e:\n    # Handle missing user specifically\nexcept AuthenticationError as e:\n    # Handle auth issues specifically\nexcept MyAPIError as e:\n    # Catch-all for other API errors\n```\n\n### Include Context in Errors\n\n```javascript\n\u002F\u002F Bad: generic error\nthrow new Error(\"Invalid parameter\");\n\n\u002F\u002F Good: contextual error\nthrow new ValidationError({\n  message: \"Invalid phone number format\",\n  field: \"to\",\n  value: \"+1abc\",\n  expected: \"E.164 format (e.g., +14155551234)\",\n  docs: \"https:\u002F\u002Fdocs.example.com\u002Fphone-numbers\"\n});\n```\n\n## Type Safety\n\nType safety is documentation that never goes stale.\n\n### TypeScript Best Practices\n\n```typescript\n\u002F\u002F Define explicit types for all inputs and outputs\ninterface User {\n  id: string;\n  email: string;\n  name: string;\n  createdAt: Date;\n  metadata?: Record\u003Cstring, unknown>;\n}\n\ninterface CreateUserInput {\n  email: string;\n  name: string;\n  metadata?: Record\u003Cstring, unknown>;\n}\n\n\u002F\u002F Return types are explicit\nasync function createUser(input: CreateUserInput): Promise\u003CUser> {\n  \u002F\u002F ...\n}\n\n\u002F\u002F Use discriminated unions for responses\ntype ApiResponse\u003CT> =\n  | { success: true; data: T }\n  | { success: false; error: ApiError };\n```\n\n### Autocomplete-Driven Design\n\nDesign for IDE autocomplete:\n\n```typescript\n\u002F\u002F Good: autocomplete shows all options\nclient.messages.create({\n  to: \"+1...\",     \u002F\u002F IDE shows: (property) to: string\n  body: \"...\",    \u002F\u002F IDE shows: (property) body: string\n  \u002F\u002F User types 'me' and sees 'mediaUrls' autocomplete\n});\n\n\u002F\u002F Bad: requires memorization\nclient.send(\"messages\", { \u002F* what goes here? *\u002F });\n```\n\n### Enum and Literal Types\n\n```typescript\n\u002F\u002F Good: constrained values with autocomplete\ntype MessageStatus = \"queued\" | \"sending\" | \"sent\" | \"failed\";\n\ninterface Message {\n  status: MessageStatus;  \u002F\u002F IDE shows valid values\n}\n\n\u002F\u002F Bad: any string accepted\ninterface Message {\n  status: string;  \u002F\u002F No guidance, errors at runtime\n}\n```\n\n## IDE Integration\n\n### Make Discovery Easy\n\nStructure your SDK so IDE features help developers:\n\n```typescript\n\u002F\u002F Namespace methods logically\nclient.users.get(id)\nclient.users.list()\nclient.users.create(data)\nclient.users.update(id, data)\nclient.users.delete(id)\n\n\u002F\u002F After typing 'client.users.' the IDE shows all user operations\n```\n\n### JSDoc\u002FDocstrings Everywhere\n\n```typescript\n\u002F**\n * Creates a new user in your organization.\n *\n * @param input - The user details\n * @param input.email - Must be a valid email address\n * @param input.name - Display name (max 100 characters)\n * @returns The created user with generated ID\n * @throws {ValidationError} If email format is invalid\n * @throws {ConflictError} If email already exists\n *\n * @example\n * const user = await client.users.create({\n *   email: \"jane@example.com\",\n *   name: \"Jane Developer\"\n * });\n *\u002F\nasync createUser(input: CreateUserInput): Promise\u003CUser>\n```\n\n### Inline Examples\n\n```python\ndef send_message(self, body: str, to: str, **kwargs) -> Message:\n    \"\"\"\n    Send an SMS message.\n\n    Args:\n        body: The message content (max 1600 characters)\n        to: Recipient phone number in E.164 format\n\n    Returns:\n        Message object with ID and status\n\n    Example:\n        >>> message = client.messages.send(\n        ...     body=\"Hello from Python!\",\n        ...     to=\"+14155551234\"\n        ... )\n        >>> print(message.status)\n        'queued'\n    \"\"\"\n```\n\n## Versioning Strategy\n\n### Semantic Versioning\n\nFollow semver strictly:\n- **MAJOR**: Breaking changes (removal, signature changes)\n- **MINOR**: New features (backward compatible)\n- **PATCH**: Bug fixes (backward compatible)\n\n### What Constitutes a Breaking Change\n\n**Breaking changes (require major version bump):**\n- Removing a public method or property\n- Changing method signatures\n- Changing return types\n- Changing default behavior\n- Removing support for a language\u002Fruntime version\n\n**Not breaking (minor or patch):**\n- Adding new methods\n- Adding optional parameters\n- Deprecating (but not removing) features\n- Bug fixes that change incorrect behavior\n\n### Deprecation Process\n\n```python\nimport warnings\n\ndef old_method(self):\n    \"\"\"\n    .. deprecated:: 2.3.0\n       Use :meth:`new_method` instead. Will be removed in 3.0.0.\n    \"\"\"\n    warnings.warn(\n        \"old_method() is deprecated, use new_method() instead. \"\n        \"See migration guide: https:\u002F\u002Fdocs.example.com\u002Fmigrate-v3\",\n        DeprecationWarning,\n        stacklevel=2\n    )\n    return self.new_method()\n```\n\n## Migration Guides\n\n### Migration Guide Structure\n\n```markdown\n# Migrating from v2 to v3\n\n## Overview\nVersion 3 introduces [major change] and removes [deprecated feature].\nMigration typically takes [time estimate].\n\n## Breaking Changes\n\n### 1. Client Initialization\n**Before (v2):**\n```python\nclient = MyClient(key=\"...\")\n```\n\n**After (v3):**\n```python\nclient = MyClient(api_key=\"...\")\n```\n\n**Why**: Consistency with other SDK parameters.\n\n### 2. [Next breaking change]\n...\n\n## Deprecated Features Removed\n- `client.old_method()` - Use `client.new_method()` instead\n- `LegacyClass` - Use `ModernClass` instead\n\n## New Features\n- [Feature that makes migration worthwhile]\n\n## Need Help?\n- [Migration support channel]\n- [Office hours for migration questions]\n```\n\n### Codemods and Automation\n\nWhen possible, provide automated migration:\n\n```bash\n# Provide migration scripts\nnpx @myapi\u002Fmigrate-v3\n\n# Or codemods\nnpx jscodeshift -t @myapi\u002Fcodemods\u002Fv2-to-v3 src\u002F\n```\n\n## Making SDKs Feel Native\n\n### Language Idioms\n\n**Python**: Use snake_case, context managers, generators\n```python\n# Pythonic\nwith client.batch() as batch:\n    for user in client.users.list():\n        batch.add(user.send_notification(\"Hello\"))\n\n# Not Pythonic\nusers = client.getUsers()\nbatch = client.createBatch()\nfor i in range(len(users)):\n    batch.addOperation(users[i].sendNotification(\"Hello\"))\nbatch.execute()\n```\n\n**JavaScript**: Use Promises, async\u002Fawait, destructuring\n```javascript\n\u002F\u002F Idiomatic JS\nconst { data, error } = await client.users.get(id);\n\n\u002F\u002F Not idiomatic\nclient.users.get(id, function(err, result) {\n    if (err) { \u002F* callback hell *\u002F }\n});\n```\n\n**Go**: Use error returns, interfaces, channels\n```go\n\u002F\u002F Idiomatic Go\nuser, err := client.Users.Get(ctx, userID)\nif err != nil {\n    return fmt.Errorf(\"getting user: %w\", err)\n}\n\n\u002F\u002F Not idiomatic\nuser := client.Users.Get(userID)  \u002F\u002F panics on error\n```\n\n### Match Ecosystem Conventions\n\n- Use the package manager developers expect (npm, pip, gem, go get)\n- Follow naming conventions of popular libraries in that language\n- Integrate with popular frameworks (Express, Django, Rails)\n- Support popular testing patterns\n\n## SDK Quality Checklist\n\n### Before Release\n\n- [ ] All public APIs have documentation\n- [ ] All public APIs have types (where language supports)\n- [ ] Error messages include remediation steps\n- [ ] Code examples in docs are tested automatically\n- [ ] Changelog is updated with all changes\n- [ ] Migration guide for breaking changes\n- [ ] Deprecation warnings for removed features\n\n### For Great DX\n\n- [ ] Quickstart achieves success in \u003C 5 minutes\n- [ ] IDE autocomplete works for all operations\n- [ ] Errors are catchable by specific type\n- [ ] Retry logic handles transient failures\n- [ ] Logging is configurable and useful\n- [ ] Debug mode shows request\u002Fresponse details\n\n## Tools\n\n### SDK Generation\n- **OpenAPI Generator**: Generate SDKs from OpenAPI specs\n- **Swagger Codegen**: Alternative generator\n- **Speakeasy**: Modern SDK generation platform\n- **Fern**: Type-safe SDK generation\n\n### Testing\n- **VCR\u002FBetamax**: Record and replay HTTP interactions\n- **WireMock**: Mock HTTP services\n- **Pact**: Contract testing\n\n### Documentation\n- **TypeDoc**: TypeScript documentation\n- **Sphinx**: Python documentation\n- **GoDoc**: Go documentation\n- **YARD**: Ruby documentation\n\n## Related Skills\n\n- **docs-as-marketing**: Documentation that showcases SDK capabilities\n- **api-onboarding**: First experience with your SDK\n- **changelog-updates**: Communicating SDK changes effectively\n- **developer-sandbox**: Try SDK without installing\n- **developer-audience-context**: Understanding SDK users\n\n## Limitations\n\n- Use this skill only when the task clearly matches its upstream source and local project context.\n- Verify commands, generated code, dependencies, credentials, and external service behavior before applying changes.\n- Do not treat examples as a substitute for environment-specific tests, security review, or user approval for destructive or costly actions.\n",{"name":5,"risk":24,"source":25,"license":15,"date_added":26,"description":7,"source_repo":27,"source_type":28,"license_source":29},"unknown","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Ftree\u002Fmain\u002Fskills\u002Fsdk-dx",1782864000000,"jonathimer\u002Fdevmarketing-skills","community","https:\u002F\u002Fgithub.com\u002Fjonathimer\u002Fdevmarketing-skills\u002Fblob\u002Fmain\u002FLICENSE","main","b1e4ffadb4f933bbbcaa03a83f8b9929171ac28b",".agents\u002Fskills\u002Fsdk-dx",0,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR","https:\u002F\u002Fgithub.com\u002FHazek-dc","2026-10-22 08:36:44",{"source":8,"skillName":5,"commands":38,"prompt":48,"zipAvailable":49},[39,42,45],{"tool":40,"command":41},"npx","npx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sdk-dx",{"tool":43,"command":44},"bunx","bunx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sdk-dx",{"tool":46,"command":47},"pnpm","pnpm dlx skills add Hazek-dc\u002FPresensiGuru_FaceNet_EMAR --skill sdk-dx","安装技能，技能地址：https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdk-dx\u002FSKILL.md",true,[51],{"path":52,"resourceType":53,"resourceTypeDesc":54,"sizeBytes":55,"sourceHtmlUrl":56},"README.md","REFERENCE","参考文档",1480,"https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002F.agents\u002Fskills\u002Fsdk-dx\u002FREADME.md",[58,65,72,79,86,93],{"skillNo":59,"name":60,"nameZh":6,"description":61,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":62,"categories":63,"keywords":64,"publishedAt":19},"01M7DS6GGYRZAYD33PFPS8Z2T3","testing-best-practices","Laravel test design and review. Use when selecting coverage, naming or structuring tests, choosing assertions or test data, isolating dependencies, testing HTTP or security boundaries, improving suite performance, or reviewing test value. Use framework guidance or search-docs for Pest and PHPUnit syntax.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftesting-best-practices\u002FSKILL.md",[],[],{"skillNo":66,"name":67,"nameZh":6,"description":68,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":69,"categories":70,"keywords":71,"publishedAt":19},"01M7DS6BC3AW7HTPRHE2TTVKWM","tailwindcss-development","Always invoke when the user's message includes 'tailwind' in any form. Also invoke for: building responsive grid layouts (multi-column card grids, product grids), flex\u002Fgrid page structures (dashboards with sidebars, fixed topbars, mobile-toggle navs), styling UI components (cards, tables, navbars, pricing sections, forms, inputs, badges), adding dark mode variants, fixing spacing or typography, and Tailwind v3\u002Fv4 work. The core use case: writing or fixing Tailwind utility classes in HTML templates (Blade, JSX, Vue). Skip for backend PHP logic, database queries, API routes, JavaScript with no HTML\u002FCSS component, CSS file audits, build tool configuration, and vanilla CSS.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Ftailwindcss-development\u002FSKILL.md",[],[],{"skillNo":73,"name":74,"nameZh":6,"description":75,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":76,"categories":77,"keywords":78,"publishedAt":19},"01M7DS66GE6B11MYJDVC74HXM4","laravel-best-practices","Apply this skill whenever writing, reviewing, or refactoring Laravel PHP code. This includes creating or modifying controllers, models, migrations, form requests, policies, jobs, scheduled commands, service classes, and Eloquent queries. Triggers for N+1 and query performance issues, caching strategies, authorization and security patterns, validation, error handling, queue and job configuration, route definitions, and architectural decisions. Also use for Laravel code reviews and refactoring existing Laravel code to follow best practices. Covers any task involving Laravel backend PHP code patterns.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Flaravel-best-practices\u002FSKILL.md",[],[],{"skillNo":80,"name":81,"nameZh":6,"description":82,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":83,"categories":84,"keywords":85,"publishedAt":19},"01M7DS5ZW717DMS6P1E90AQCKV","infer-conventions","Use this skill to analyze how a Laravel application is actually written and record its conventions as shared rules. Trigger when the user wants to detect, infer, document, or standardize project conventions or coding style, set up or grow `.ai\u002Frules`, resolve mixed or conflicting patterns (e.g. \"are we using Form Requests or inline validation?\"), or onboard agents and teammates to \"how we do things here\". Covers: a systematic sweep of ~49 Laravel convention dimensions (validation, models, architecture, testing, frontend, database, console), open-ended house-pattern discovery, conflict reporting, and recording rules scoped to the right paths via the Boost `record-rule` MCP tool. Only run this skill when the user explicitly asks for it; never start a sweep as part of another task. Do not use for one-off code review, enforcing formatting a linter already handles, or editing `.ai\u002Frules` files by hand.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finfer-conventions\u002FSKILL.md",[],[],{"skillNo":87,"name":88,"nameZh":6,"description":89,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":90,"categories":91,"keywords":92,"publishedAt":19},"01M7DS5W12RGCVJTFQJ1N0GB8E","inertia-react-development","Develops Inertia.js v2 React client-side applications. Activates when creating React pages, forms, or navigation; using \u003CLink>, \u003CForm>, useForm, or router; working with deferred props, prefetching, or polling; or when user mentions React with Inertia, React pages, React forms, or React navigation.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Finertia-react-development\u002FSKILL.md",[],[],{"skillNo":94,"name":95,"nameZh":6,"description":96,"descriptionZh":6,"repositoryFullName":8,"ownerLogin":9,"ownerAvatarUrl":10,"ownerAccountNo":11,"ownerDisplayName":12,"repositoryNo":13,"starsCount":14,"licenseSpdxId":15,"licenseFileUrl":6,"sourceHtmlUrl":97,"categories":98,"keywords":99,"publishedAt":19},"01M7DS5PVDPMPCWSK2RXPDC9BB","deploying-to-cloud","Deploys and manages Laravel applications on Laravel Cloud using the `cloud` CLI. Use when the user wants to deploy an app, ship to Cloud, create or manage applications, environments, databases, caches, object storage, queues, domains, instances, background processes, secrets, compute, scheduled tasks, or Laravel Cloud infrastructure; or check billing, usage, or spend. Triggers on deployment, shipping, Cloud management, environment setup, database provisioning, billing or usage queries, the `cloud` CLI, and Laravel Cloud deployment troubleshooting.","https:\u002F\u002Fgithub.com\u002FHazek-dc\u002FPresensiGuru_FaceNet_EMAR\u002Fblob\u002Fmain\u002Fattendance-web\u002F.claude\u002Fskills\u002Fdeploying-to-cloud\u002FSKILL.md",[],[]]