@soulcraft/kits 1.0.0

package/src/kits/youtube-content-plan.ts

@@ -0,0 +1,339 @@
+/**
+ * @module @soulcraft/kits/kits/youtube-content-plan
+ * @description Content calendar, video scripts, and channel strategy for YouTube creators
+ *
+ * Generated from: kits/youtube-content-plan/kit.json
+ * Do not edit this file directly — edit the source kit.json and re-run `bun run build:kits`.
+ */
+
+import type { SoulcraftKitConfig } from '@soulcraft/kit-schema';
+
+/**
+ * YouTube Channel Content Plan kit configuration.
+ *
+ * @description Content calendar, video scripts, and channel strategy for YouTube creators
+ * @see {@link SoulcraftKitConfig}
+ */
+const youtubeContentPlan: SoulcraftKitConfig = {
+	"$schema": "https://soulcraft.com/schemas/kit/v2.json",
+	"id": "youtube-content-plan",
+	"name": "YouTube Channel Content Plan",
+	"description": "Content calendar, video scripts, and channel strategy for YouTube creators",
+	"version": "1.0.0",
+	"author": {
+		"name": "Soulcraft Labs",
+		"email": "kits@soulcraft.com",
+		"url": "https://soulcraft.com"
+	},
+	"status": "released",
+	"icon": "🎥",
+	"longDescription": "Complete YouTube content planning system with video ideas, scripts, SEO optimization, thumbnail concepts, and analytics tracking. Plan your content calendar, organize videos into playlists, and track performance metrics all in one connected workspace.",
+	"tags": [
+		"youtube",
+		"video",
+		"content-creation",
+		"social-media"
+	],
+	"role": "primary",
+	"type": "soulcraft",
+	"variables": [
+		{
+			"key": "projectName",
+			"label": "Channel/Series Name",
+			"description": "The name of your YouTube channel or series",
+			"type": "string",
+			"required": true,
+			"example": "TechTips Weekly"
+		},
+		{
+			"key": "author",
+			"label": "Creator",
+			"description": "Your name as the content creator",
+			"type": "string",
+			"required": false,
+			"example": "Your Name"
+		},
+		{
+			"key": "niche",
+			"label": "Channel Niche",
+			"description": "The primary topic or focus of your channel",
+			"type": "string",
+			"required": false,
+			"example": "Web Development Tutorials"
+		}
+	],
+	"shared": {
+		"industry": "writing-publishing",
+		"category": "creative",
+		"aiExpertise": [
+			"YouTube content strategy",
+			"Video script writing",
+			"SEO title and description optimization",
+			"Thumbnail concept development",
+			"Channel growth strategy"
+		],
+		"dataModelHints": [
+			"document",
+			"collection",
+			"concept",
+			"person"
+		],
+		"suggestions": [
+			{
+				"label": "Plan a video",
+				"prompt": "Help me plan and outline a new YouTube video"
+			},
+			{
+				"label": "Write a script",
+				"prompt": "Help me write a script for my next video"
+			},
+			{
+				"label": "Optimize titles",
+				"prompt": "Help me write compelling titles and descriptions for my videos"
+			},
+			{
+				"label": "Plan a series",
+				"prompt": "Help me plan a multi-video series on a topic"
+			},
+			{
+				"label": "Content strategy",
+				"prompt": "Review my channel content and suggest strategic improvements"
+			},
+			{
+				"label": "View content calendar",
+				"prompt": "Show me my video schedule in the calendar view"
+			}
+		],
+		"dataModel": {
+			"entities": [
+				{
+					"domain": "video",
+					"type": "Document",
+					"description": "A YouTube video with script, title, and SEO metadata",
+					"products": {
+						"workshop": {
+							"view": "board",
+							"icon": "🎥"
+						},
+						"academy": {
+							"mapsTo": "learning-artifact",
+							"assessable": true
+						}
+					}
+				},
+				{
+					"domain": "series",
+					"type": "Concept",
+					"description": "A thematic series or playlist grouping related videos",
+					"products": {
+						"workshop": {
+							"view": "timeline",
+							"icon": "📚"
+						},
+						"academy": {
+							"mapsTo": "knowledge-unit",
+							"assessable": false
+						}
+					}
+				},
+				{
+					"domain": "topic",
+					"type": "Concept",
+					"description": "A content topic or keyword a video targets",
+					"products": {
+						"workshop": {
+							"view": "graph",
+							"icon": "💡"
+						},
+						"academy": {
+							"mapsTo": "knowledge-unit",
+							"assessable": true
+						}
+					}
+				},
+				{
+					"domain": "collaborator",
+					"type": "Person",
+					"description": "A creator or guest featured in a video",
+					"products": {
+						"workshop": {
+							"view": "gallery",
+							"icon": "👤"
+						},
+						"academy": {
+							"mapsTo": "learning-subject",
+							"assessable": false
+						}
+					}
+				}
+			],
+			"relationships": [
+				{
+					"from": "video",
+					"to": "series",
+					"verb": "PartOf",
+					"description": "Video belongs to this series or playlist"
+				},
+				{
+					"from": "video",
+					"to": "topic",
+					"verb": "References",
+					"description": "Video covers this topic or keyword"
+				},
+				{
+					"from": "video",
+					"to": "collaborator",
+					"verb": "Contains",
+					"description": "Video features this collaborator"
+				},
+				{
+					"from": "video",
+					"to": "video",
+					"verb": "RelatedTo",
+					"description": "Related videos for cross-promotion"
+				}
+			]
+		}
+	},
+	"workshop": {
+		"workspaceConfig": {
+			"paradigm": "planner",
+			"defaultTab": "explore",
+			"defaultView": "calendar",
+			"defaultFile": "content/video-ideas.md"
+		},
+		"graphGuidance": {
+			"conceptCreation": {
+				"triggers": [
+					"When user creates a new video idea",
+					"When user defines a series or playlist",
+					"When user identifies a topic or keyword",
+					"When user notes a collaboration"
+				],
+				"typeMapping": {
+					"video": "document",
+					"series": "collection",
+					"playlist": "collection",
+					"topic": "concept",
+					"collaborator": "person"
+				}
+			},
+			"relationshipPatterns": [
+				{
+					"from": "document",
+					"to": "collection",
+					"verb": "partOf",
+					"description": "Video in playlist"
+				},
+				{
+					"from": "document",
+					"to": "concept",
+					"verb": "references",
+					"description": "Video covers topic"
+				},
+				{
+					"from": "document",
+					"to": "person",
+					"verb": "contains",
+					"description": "Video features collaborator"
+				},
+				{
+					"from": "document",
+					"to": "document",
+					"verb": "relatedTo",
+					"description": "Related videos"
+				}
+			],
+			"rules": [
+				"Create document entities for video ideas",
+				"Link videos to their playlists and topics",
+				"Track collaborations and features",
+				"Note content pillars and themes"
+			]
+		},
+		"qualityGates": {
+			"fileChecks": [
+				{
+					"path": "scripts/*.md",
+					"required": [
+						"Title",
+						"Hook",
+						"Script"
+					],
+					"optional": [
+						"B-Roll",
+						"Thumbnail Concept",
+						"Production Notes"
+					]
+				},
+				{
+					"path": "channel-strategy.md",
+					"required": [
+						"Mission Statement",
+						"Content Pillars"
+					],
+					"optional": [
+						"Publishing Schedule",
+						"Growth Strategy"
+					]
+				}
+			],
+			"projectChecks": [
+				"Channel strategy is defined",
+				"Content pillars are identified",
+				"At least one script is complete",
+				"Publishing schedule is set"
+			],
+			"exportReady": [
+				"Scripts have production notes",
+				"Thumbnails are designed",
+				"Metadata is optimized",
+				"Content calendar is current"
+			]
+		},
+		"aiPersona": {
+			"role": "You are a YouTube growth strategist and video content expert helping creators plan, script, and optimize their content for maximum reach and audience engagement.",
+			"expertise": [
+				"YouTube content strategy",
+				"Video script writing",
+				"SEO optimization",
+				"Thumbnail and title strategy",
+				"Channel growth and retention"
+			],
+			"tone": "collaborator"
+		},
+		"exporters": [
+			{
+				"id": "youtube-package",
+				"name": "YouTube Production Package",
+				"description": "Scripts, calendar, and analytics in one bundle",
+				"icon": "📦",
+				"format": "zip",
+				"category": "archive",
+				"handler": "markdown-bundle"
+			}
+		],
+		"difficulty": "intermediate",
+		"templateTier": 4,
+		"templateMetadata": {
+			"identifyByStructure": true
+		}
+	},
+	"academy": {
+		"skillPath": "video-production",
+		"level": "beginner",
+		"learningObjectives": [
+			"Write a video script with a hook that delivers the core value promise within the first 30 seconds",
+			"Optimise a title and description using keyword research and click-through best practices",
+			"Plan a content calendar that batches production and maintains a consistent publishing cadence",
+			"Structure a video series so each episode drives viewers to the next with clear continuity"
+		],
+		"assessmentTypes": [
+			"portfolio",
+			"peer-review"
+		],
+		"certificationSlug": "content-creator"
+	}
+} satisfies SoulcraftKitConfig;
+
+export default youtubeContentPlan;

package/src/registry.ts

@@ -0,0 +1,60 @@
+/**
+ * @module @soulcraft/kits/registry
+ * @description Central kit registry keyed by kit ID.
+ *
+ * The registry provides O(1) lookup by kit ID, used by platform product loaders
+ * (Venue's deployment service, Workshop's kit browser) to resolve a kit by its
+ * string identifier.
+ *
+ * @example
+ * ```ts
+ * import { kitRegistry } from '@soulcraft/kits/registry';
+ *
+ * const kit = kitRegistry['wicks-and-whiskers'];
+ * if (!kit) throw new Error('Kit not found');
+ * console.log(kit.venue?.features.animals); // true
+ * ```
+ */
+
+import type { SoulcraftKitConfig } from '@soulcraft/kit-schema';
+import * as kits from './kits/index.js';
+
+/**
+ * All Soulcraft kits indexed by their unique kit ID.
+ *
+ * @description Each value is a fully typed and Zod-validated `SoulcraftKitConfig`.
+ * The registry is populated at module load time from the static kit exports.
+ *
+ * @example
+ * ```ts
+ * const kit = kitRegistry['axe-house'];
+ * kit?.venue?.experienceTypes.forEach(t => console.log(t.name));
+ * ```
+ */
+export const kitRegistry: Record<string, SoulcraftKitConfig> = Object.fromEntries(
+	Object.values(kits).map((kit) => [kit.id, kit])
+);
+
+/**
+ * Retrieve a kit by ID, throwing if it does not exist.
+ *
+ * @description Convenience wrapper around `kitRegistry` for cases where a missing
+ * kit is a programming error (e.g. loading a kit that should always be present).
+ *
+ * @param id - The kit ID to look up. @example "wicks-and-whiskers"
+ * @returns The resolved `SoulcraftKitConfig`.
+ * @throws {Error} If no kit with the given ID exists in the registry.
+ *
+ * @example
+ * ```ts
+ * const kit = requireKit('wicks-and-whiskers');
+ * console.log(kit.name); // 'Wicks & Whiskers'
+ * ```
+ */
+export function requireKit(id: string): SoulcraftKitConfig {
+	const kit = kitRegistry[id];
+	if (!kit) {
+		throw new Error(`Kit not found in registry: "${id}". Available kits: ${Object.keys(kitRegistry).join(', ')}`);
+	}
+	return kit;
+}

package/src/skills/api-documentation/index.ts

@@ -0,0 +1,47 @@
+/**
+ * @module @soulcraft/kits/skills/api-documentation
+ * @description Raw SKILL.md content for the api-documentation kit's AI skills.
+ *
+ * Generated from: kits/api-documentation/skills/{skillId}/SKILL.md
+ * Do not edit directly — edit the source SKILL.md files and re-run `bun run build:skills`.
+ */
+
+/** Raw SKILL.md content for the `document-auth` skill. */
+export const documentAuth = "---\nname: Document Authentication\ndescription: Create comprehensive authentication documentation\ntype: invocable\nversion: \"1.0.0\"\nparameters: [authMethod]\n---\n\n## Document Authentication\n\nCreate comprehensive authentication documentation\n\n### Steps\n\n1. Identify the authentication method(s) supported\n2. Document how to obtain credentials (API keys, OAuth tokens)\n3. Show how to include credentials in requests (headers, query params)\n4. Document token refresh flows if applicable\n5. Add examples for each authentication method\n6. Document scopes and permissions if using OAuth\n7. Add security best practices section\n\n### Inputs Required\n\n- **authMethod** (required): Primary authentication method (API key, OAuth 2.0, Basic)\n\n### Expected Outputs\n\n- Authentication documentation\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"authentication\"\n- \"auth\"\n- \"security\"\n- \"login\"\n- \"oauth\"\n- \"api key\"\n";
+
+/** Raw SKILL.md content for the `define-resource` skill. */
+export const defineResource = "---\nname: Define API Resource\ndescription: Create documentation for a new API resource type\ntype: invocable\nversion: \"1.0.0\"\nparameters: [resourceName, description]\n---\n\n## Define API Resource\n\nCreate documentation for a new API resource type\n\n### Steps\n\n1. Define the resource name and description\n2. Create the resource schema with all properties and types\n3. Identify required vs optional properties\n4. Document relationships to other resources\n5. Create standard CRUD endpoints for the resource\n6. Add example resource objects\n7. Update the resource index\n\n### Inputs Required\n\n- **resourceName** (required): Name of the resource (singular form)\n- **description** (required): Brief description of what this resource represents\n\n### Expected Outputs\n\n- Resource documentation\n- CRUD endpoint stubs\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"new resource\"\n- \"add resource\"\n- \"define resource\"\n- \"create resource\"\n";
+
+/** Raw SKILL.md content for the `document-endpoint` skill. */
+export const documentEndpoint = "---\nname: Document API Endpoint\ndescription: Create comprehensive documentation for a new API endpoint\ntype: invocable\nversion: \"1.0.0\"\nparameters: [resource, action]\n---\n\n## Document API Endpoint\n\nCreate comprehensive documentation for a new API endpoint\n\n### Steps\n\n1. Determine the HTTP method and URL path for the endpoint\n2. Define path parameters, query parameters, and request body schema\n3. Specify required and optional headers including authentication\n4. Document the success response format with status code and body schema\n5. Document all possible error responses with codes and messages\n6. Create realistic request and response examples\n7. Add curl or SDK code examples for quick testing\n8. Update the endpoints index with the new endpoint\n\n### Inputs Required\n\n- **resource** (required): The resource type (e.g., users, orders)\n- **action** (required): The action (list, get, create, update, delete, custom)\n\n### Expected Outputs\n\n- Endpoint documentation file\n- Updated endpoints index\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"new endpoint\"\n- \"document endpoint\"\n- \"add endpoint\"\n- \"api endpoint\"\n";
+
+/** Raw SKILL.md content for the `api-versioning` skill. */
+export const apiVersioning = "---\nname: api-versioning\ndescription: Background expertise in API versioning strategies and deprecation best practices\ntype: background\nversion: \"1.0.0\"\n---\n\n## API Versioning Expertise\n\nYou have expertise in API versioning strategies and managing API evolution. Apply these principles when helping users design and document APIs.\n\n### Versioning Strategies\n\n**URL Path Versioning**\n```\nhttps://api.example.com/v1/users\nhttps://api.example.com/v2/users\n```\n- Pros: Clear, visible, easy caching\n- Cons: Changes URLs, client updates needed\n- Best for: Major version changes\n\n**Query Parameter Versioning**\n```\nhttps://api.example.com/users?version=1\nhttps://api.example.com/users?version=2\n```\n- Pros: Same URL, easy testing\n- Cons: Can be missed, caching complications\n- Best for: Optional versioning\n\n**Header Versioning**\n```\nAccept: application/vnd.example.v1+json\nX-API-Version: 1\n```\n- Pros: Clean URLs, RESTful\n- Cons: Less visible, harder to test\n- Best for: Sophisticated clients\n\n**Content Negotiation**\n```\nAccept: application/vnd.example+json; version=1\n```\n- Pros: Most RESTful approach\n- Cons: Complex, tooling challenges\n- Best for: API purists\n\n### When to Version\n\n**Major Version (v1 → v2)**\n- Breaking changes to response structure\n- Removed endpoints or fields\n- Changed authentication\n- Fundamental behavior changes\n\n**No Version Needed**\n- Adding new optional fields\n- Adding new endpoints\n- Bug fixes\n- Performance improvements\n\n### Deprecation Strategy\n\n**Timeline**\n1. Announce deprecation (6+ months notice)\n2. Add deprecation headers\n3. Update documentation\n4. Monitor usage\n5. Final sunset\n\n**Deprecation Headers**\n```\nDeprecation: true\nSunset: Sat, 31 Dec 2024 23:59:59 GMT\nLink: <https://api.example.com/v2/users>; rel=\"successor-version\"\n```\n\n**Documentation**\n- Mark deprecated in OpenAPI spec\n- Add migration guide\n- List breaking changes\n- Provide upgrade path\n\n### Breaking vs Non-Breaking Changes\n\n**Breaking Changes (Require New Version)**\n- Removing fields/endpoints\n- Changing field types\n- Changing required fields\n- Renaming fields\n- Changing error formats\n- Removing enum values\n\n**Non-Breaking Changes (Safe to Add)**\n- New optional fields\n- New endpoints\n- New optional parameters\n- New enum values (usually)\n- Relaxing validation\n- Adding headers\n\n### Migration Best Practices\n\n**For API Providers**\n- Run versions in parallel\n- Provide migration tools/scripts\n- Monitor old version usage\n- Communicate clearly and early\n- Offer migration support\n\n**Documentation for Migrations**\n```markdown\n## Migrating from v1 to v2\n\n### Breaking Changes\n| v1 | v2 | Migration |\n|----|----|----|\n| `username` | `email` | Rename field |\n| `GET /user` | `GET /users/{id}` | Update endpoint |\n\n### New Features in v2\n- Field X added\n- Endpoint Y improved\n\n### Timeline\n- v2 available: January 1, 2024\n- v1 deprecated: July 1, 2024\n- v1 sunset: January 1, 2025\n```\n\n### API Evolution Patterns\n\n**Expand-Contract Pattern**\n1. Add new field alongside old (expand)\n2. Migrate clients to new field\n3. Remove old field (contract)\n\n**Feature Flags**\n- Enable new behavior for opt-in clients\n- Gradually migrate\n- Flip default, then remove flag\n\n**API Gateway Versioning**\n- Route different versions to different backends\n- Transform requests/responses at gateway\n- Simplifies backend code\n\n### Common Mistakes\n\n- No versioning strategy from start\n- Breaking changes without version bump\n- Inconsistent versioning across endpoints\n- No deprecation warnings\n- Sunset without migration path\n- Keeping old versions forever\n";
+
+/** Raw SKILL.md content for the `openapi-spec` skill. */
+export const openapiSpec = "---\nname: openapi-spec\ndescription: Write clear, complete OpenAPI/Swagger specifications for REST APIs\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## OpenAPI Specification Skill\n\nWhen the user invokes `/openapi`, help them write or improve OpenAPI (Swagger) specifications for their APIs.\n\n### Invocation Patterns\n\n- `/openapi` - Generate spec from existing code/docs\n- `/openapi validate` - Validate and improve existing spec\n- `/openapi endpoint [method] [path]` - Document specific endpoint\n\n### OpenAPI 3.0+ Structure\n\n```yaml\nopenapi: 3.0.3\ninfo:\n  title: API Title\n  description: API description\n  version: 1.0.0\nservers:\n  - url: https://api.example.com/v1\npaths:\n  /resource:\n    get:\n      # endpoint definition\ncomponents:\n  schemas:\n    # reusable schemas\n  securitySchemes:\n    # authentication methods\n```\n\n### Path Documentation\n\n```yaml\n/users/{userId}:\n  get:\n    summary: Get user by ID\n    description: |\n      Retrieves a single user by their unique identifier.\n      Returns 404 if user doesn't exist.\n    operationId: getUserById\n    tags:\n      - Users\n    parameters:\n      - name: userId\n        in: path\n        required: true\n        description: Unique user identifier\n        schema:\n          type: string\n          format: uuid\n    responses:\n      '200':\n        description: Successful response\n        content:\n          application/json:\n            schema:\n              $ref: '#/components/schemas/User'\n      '404':\n        description: User not found\n        content:\n          application/json:\n            schema:\n              $ref: '#/components/schemas/Error'\n```\n\n### Schema Best Practices\n\n**Use Descriptive Schemas**\n```yaml\ncomponents:\n  schemas:\n    User:\n      type: object\n      required:\n        - id\n        - email\n      properties:\n        id:\n          type: string\n          format: uuid\n          description: Unique identifier\n          example: \"123e4567-e89b-12d3-a456-426614174000\"\n        email:\n          type: string\n          format: email\n          description: User's email address\n          example: \"user@example.com\"\n        createdAt:\n          type: string\n          format: date-time\n          description: Account creation timestamp\n```\n\n**Common Formats**\n- `format: uuid` - UUIDs\n- `format: email` - Email addresses\n- `format: date-time` - ISO 8601 timestamps\n- `format: uri` - URLs\n- `format: int32/int64` - Integer sizes\n\n### Output Format\n\n```markdown\n## OpenAPI Specification\n\n### Endpoint: [Method] [Path]\n\n```yaml\n[Complete OpenAPI YAML for endpoint]\n```\n\n### Schema Definitions\n\n```yaml\n[Related component schemas]\n```\n\n### Documentation Checklist\n- [ ] Summary is concise (< 120 chars)\n- [ ] Description explains behavior\n- [ ] All parameters documented\n- [ ] All responses defined\n- [ ] Examples provided\n- [ ] Error responses included\n- [ ] Authentication specified\n```\n\n### Security Schemes\n\n```yaml\ncomponents:\n  securitySchemes:\n    bearerAuth:\n      type: http\n      scheme: bearer\n      bearerFormat: JWT\n    apiKey:\n      type: apiKey\n      in: header\n      name: X-API-Key\n```\n\n### Response Patterns\n\n**Success Responses**\n- 200: OK (GET, PUT, PATCH)\n- 201: Created (POST)\n- 204: No Content (DELETE)\n\n**Error Responses**\n- 400: Bad Request (validation errors)\n- 401: Unauthorized (missing auth)\n- 403: Forbidden (insufficient permissions)\n- 404: Not Found\n- 422: Unprocessable Entity (business logic error)\n- 500: Internal Server Error\n\n### Quality Checklist\n\n- Every endpoint has summary + description\n- All parameters have descriptions\n- All schemas have examples\n- Error responses are documented\n- Authentication requirements specified\n- Consistent naming conventions\n- No broken $refs\n";
+
+/** Raw SKILL.md content for the `api-review` skill. */
+export const apiReview = "---\nname: Review API Documentation\ndescription: Comprehensive review of API documentation for completeness and quality\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## Review API Documentation\n\nComprehensive review of API documentation for completeness and quality\n\n### Steps\n\n1. Check that all endpoints are documented with method, path, and description\n2. Verify authentication requirements are clear for each endpoint\n3. Ensure all request parameters are documented with types and requirements\n4. Verify all response formats are documented including error responses\n5. Check for consistent naming conventions across endpoints\n6. Verify examples are complete and use realistic data\n7. Check that rate limits and pagination are documented\n8. Identify any gaps or inconsistencies\n9. Provide prioritized improvement recommendations\n\n### Expected Outputs\n\n- Documentation review report\n- Improvement recommendations\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"review\"\n- \"check documentation\"\n- \"audit\"\n- \"completeness\"\n";
+
+/** Raw SKILL.md content for the `kit-expertise` skill. */
+export const kitExpertise = "---\nname: kit-expertise\ndescription: Domain expertise for API Documentation - applied automatically when working in this kit\ntype: background\nversion: \"1.0.0\"\n---\n\n## Your Role\n\nAPI Documentation Specialist helping you create clear, developer-friendly API documentation\n\n## Your Expertise\n\n- API documentation best practices\n- OpenAPI/Swagger specification\n- Endpoint design and naming\n- Request/response documentation\n- Authentication documentation\n- Error handling documentation\n- Code examples and SDKs\n- Developer experience optimization\n\n## Your Approach\n\nAssist the user with their requests efficiently\n\n## Things to Avoid\n\n- Incomplete endpoint documentation\n- Missing error codes\n- Outdated examples\n- Inconsistent formatting\n\n## Domain Knowledge\n\n### Key Terms\n\n**endpoint**\nURL path for accessing a specific resource\n\n**HTTP method**\nGET, POST, PUT, PATCH, DELETE operations\n\n**request body**\nData sent to the API\n\n**response body**\nData returned by the API\n\n**query parameter**\nOptional URL parameter\n\n**path parameter**\nVariable in the URL path\n\n**authentication**\nMethod to verify API caller identity\n\n**rate limiting**\nRestrictions on API call frequency\n\n### Best Practices\n\n- Document all endpoints completely\n- Include request and response examples\n- List all possible error codes\n- Show authentication requirements\n- Provide code examples in multiple languages\n- Keep documentation in sync with API\n\n### Common Mistakes to Avoid\n\n- Outdated documentation\n- Missing error scenarios\n- No code examples\n- Inconsistent naming\n- Undocumented parameters\n- No versioning information\n";
+
+/** Raw SKILL.md content for the `api-examples` skill. */
+export const apiExamples = "---\nname: api-examples\ndescription: Generate code examples for API endpoints in multiple programming languages\ntype: invocable\nversion: \"1.0.0\"\n---\n\n## API Examples Skill\n\nWhen the user invokes `/examples`, generate clear, working code examples for API endpoints in multiple programming languages.\n\n### Invocation Patterns\n\n- `/examples` - Generate examples for current endpoint\n- `/examples [language]` - Generate for specific language\n- `/examples all` - Generate for all common languages\n\n### Supported Languages\n\n- cURL (universal baseline)\n- JavaScript (fetch, axios)\n- Python (requests)\n- Ruby\n- PHP\n- Go\n- Java\n- C# (.NET)\n\n### Example Templates\n\n**cURL**\n```bash\ncurl -X POST 'https://api.example.com/v1/users' \\\n  -H 'Authorization: Bearer YOUR_TOKEN' \\\n  -H 'Content-Type: application/json' \\\n  -d '{\n    \"email\": \"user@example.com\",\n    \"name\": \"John Doe\"\n  }'\n```\n\n**JavaScript (fetch)**\n```javascript\nconst response = await fetch('https://api.example.com/v1/users', {\n  method: 'POST',\n  headers: {\n    'Authorization': 'Bearer YOUR_TOKEN',\n    'Content-Type': 'application/json',\n  },\n  body: JSON.stringify({\n    email: 'user@example.com',\n    name: 'John Doe',\n  }),\n});\n\nconst data = await response.json();\n```\n\n**Python (requests)**\n```python\nimport requests\n\nresponse = requests.post(\n    'https://api.example.com/v1/users',\n    headers={\n        'Authorization': 'Bearer YOUR_TOKEN',\n    },\n    json={\n        'email': 'user@example.com',\n        'name': 'John Doe',\n    }\n)\n\ndata = response.json()\n```\n\n**Go**\n```go\npackage main\n\nimport (\n    \"bytes\"\n    \"encoding/json\"\n    \"net/http\"\n)\n\nfunc main() {\n    payload := map[string]string{\n        \"email\": \"user@example.com\",\n        \"name\":  \"John Doe\",\n    }\n    body, _ := json.Marshal(payload)\n\n    req, _ := http.NewRequest(\"POST\", \"https://api.example.com/v1/users\", bytes.NewBuffer(body))\n    req.Header.Set(\"Authorization\", \"Bearer YOUR_TOKEN\")\n    req.Header.Set(\"Content-Type\", \"application/json\")\n\n    client := &http.Client{}\n    resp, _ := client.Do(req)\n    defer resp.Body.Close()\n}\n```\n\n### Output Format\n\n```markdown\n## API Examples: [Endpoint Name]\n\n### Request\n- **Method**: POST\n- **URL**: `https://api.example.com/v1/users`\n- **Authentication**: Bearer token\n\n### cURL\n```bash\n[cURL example]\n```\n\n### JavaScript\n```javascript\n[JavaScript example]\n```\n\n### Python\n```python\n[Python example]\n```\n\n### Response Example\n```json\n{\n  \"id\": \"123e4567-e89b-12d3-a456-426614174000\",\n  \"email\": \"user@example.com\",\n  \"name\": \"John Doe\",\n  \"createdAt\": \"2024-01-15T10:30:00Z\"\n}\n```\n```\n\n### Best Practices\n\n**Code Quality**\n- Use realistic placeholder values\n- Include error handling in complex examples\n- Show response handling\n- Use idiomatic code for each language\n\n**Completeness**\n- Include all required headers\n- Show authentication\n- Include request body for POST/PUT\n- Show expected response\n\n**Clarity**\n- Use syntax highlighting\n- Add comments for complex steps\n- Keep examples minimal but complete\n- Use consistent formatting\n\n### Common Patterns\n\n**Authentication Examples**\n- Bearer token\n- API key (header vs query param)\n- Basic auth\n- OAuth flow\n\n**Request Body Patterns**\n- JSON (most common)\n- Form data\n- Multipart (file uploads)\n\n**Response Handling**\n- Success parsing\n- Error handling\n- Pagination\n";
+
+/** Raw SKILL.md content for the `create-code-examples` skill. */
+export const createCodeExamples = "---\nname: Generate Code Examples\ndescription: Create SDK/language-specific code examples for endpoints\ntype: invocable\nversion: \"1.0.0\"\nparameters: [language, endpoint]\n---\n\n## Generate Code Examples\n\nCreate SDK/language-specific code examples for endpoints\n\n### Steps\n\n1. Identify the target programming language(s)\n2. Review the endpoint documentation for request/response format\n3. Create a code example showing authentication setup\n4. Create the API call with proper error handling\n5. Show how to parse and use the response\n6. Add inline comments explaining each step\n7. Test or validate the example logic\n\n### Inputs Required\n\n- **language** (required): Target language (JavaScript, Python, Ruby, curl)\n- **endpoint** (required): Which endpoint to create examples for\n\n### Expected Outputs\n\n- Code examples in specified language\n\n### When to Use\n\nThis workflow is helpful when the user mentions:\n- \"code example\"\n- \"sdk example\"\n- \"how to call\"\n- \"sample code\"\n\n### Execution Mode\n\nThis workflow can be executed automatically when triggered. Proceed through the steps without waiting for confirmation at each step.\n";
+
+/** All skills for the api-documentation kit, keyed by skill ID. */
+export const allSkills: Record<string, string> = {
+	'document-auth': documentAuth,
+	'define-resource': defineResource,
+	'document-endpoint': documentEndpoint,
+	'api-versioning': apiVersioning,
+	'openapi-spec': openapiSpec,
+	'api-review': apiReview,
+	'kit-expertise': kitExpertise,
+	'api-examples': apiExamples,
+	'create-code-examples': createCodeExamples
+};