with one click
carton-case-management
carton-case-management contains 9 collected skills from bitovi, with repository-level occupation coverage and site-owned skill detail pages.
Skills in this repository
Post generated design behavior questions as comments on Figma frames. Takes questions organized by frame (from generate-behavior-questions skill) and posts each question as a comment pinned to the correct Figma frame using the figma-post-comment MCP tool.
Generate frame-specific clarifying questions about ambiguous UI behaviors from a Jira epic and its linked Figma designs, Confluence pages, and Google Docs. Uses iterative content loading, parallel Figma frame analysis, and cross-content synthesis to produce targeted behavior questions organized by Figma frame.
Create new Agent Skills for this project. Use when asked to create a skill, document a workflow, or teach the agent a new capability. Skills are stored in .claude/skills/ and can include instructions, scripts, examples, and resources.
Ensure existing UI components are reused before creating new ones. Use when implementing any UI from Figma designs, tickets, or mockups. Requires a component audit to search the codebase before creating new components. If a component doesn't exist, delegates to figma-implement-component skill.
Manage TypeScript type flow between @carton/shared, @carton/server, and @carton/client packages. Use when adding Prisma models, creating tRPC procedures, importing types in components, or resolving circular dependency issues between packages.
Check a React component against its Figma design source and identify differences. Use when reviewing component implementations, syncing designs, auditing visual accuracy, or updating components to match new Figma designs.
Connect shadcn/ui components to their Figma design system counterparts using Code Connect.
Explore a Figma file to discover all pages, components, and component sets using the Figma REST API. Use when you need to list components in a Figma file, find component node IDs for Code Connect, or understand the structure of a design file.
Validate implementations for runtime errors and proper functionality. Use when reviewing implementations, syncing designs, or auditing before committing code.