duc

Use this skill whenever implementing type, field, or schema changes across the duc monorepo. Triggers when the user asks to add a new field, change a type, rename a property, or propagate any data model change across the duc codebase. Also triggers when the user mentions duc.sql, schema migrations, DataState, or any of the cross-language duc type files (ducrs, ducjs, ducpy). Always use this skill before touching duc type files — it tells you exactly which files to edit and in what order.

Retrieves up-to-date documentation, API references, and code examples for any developer technology. Use this skill whenever the user asks about Context7 or a specific library, framework, SDK, CLI tool, or cloud service — even for well-known ones like React, Next.js, Prisma, Express, Tailwind, Django, or Spring Boot. Your training data may not reflect recent API changes or version updates. Always use for: API syntax questions, configuration options, version migration issues, "how do I" questions mentioning a library name, debugging that involves library-specific behavior, setup instructions, and CLI tool usage. Use even when you think you know the answer — do not rely on training data for API details, signatures, or configuration options as they are frequently outdated. Always verify against current docs. Prefer this over web search for library documentation and API details.

Generates technical guides that teach real-world use cases through progressive examples. **Auto-activation:** User asks to write, create, or draft a guide or tutorial. Also use when converting feature documentation, API references, or skill knowledge into step-by-step learning content. **Input sources:** API documentation, existing code examples, or user-provided specifications.

Use when creating git commits, writing commit messages, or when about to run git commit -- enforces structured commit message format with imperative mood, capitalized subjects, 72-char wrapping