All authors

Claude Skills by Canhada-Labs
github.com/Canhada-Labs167 skills11 installs322 views
- Sales CoachRep development, pipeline review facilitation, call coaching methodology,Votes: 0GitHub stars: 2
- Sales EngineerPre-sales engineering across the full technical evaluation lifecycle: structured discovery to surface architecture context, integration surfaces, security posture, and regulatory constraints; demo engineering built on buyer-documented outcomes rather than feature walkthroughs; POC scoping with written acceptance criteria agreed before the first configuration; and competitive battlecards grounded in verifiable fact. Bridges product capabilities to business outcomes and owns the technical decis...Votes: 0GitHub stars: 2
- Sales OutreachConsultative B2B sales outreach — cold prospecting, lead follow-up, objection handling, proposal-stage messaging, and pipeline management for {{PROJECT_NAME}} sales teams. Combines data-driven targeting with relationship-first execution: research-before-write discipline, signal-cited openers, channel-specific message architecture, structured objection frames, and cadence rhythm calibrated by deal stage. Use when writing a cold sequence, handling an objection, drafting a proposal, managing a m...Votes: 0GitHub stars: 2
- Supply Chain StrategistSupply chain strategy across sourcing, supplier qualification, demandVotes: 0GitHub stars: 2
- Kill SwitchesKill-switch and circuit-breaker engineering for HFT systems — independence from order paths, cancel-all flow correctness, position-flatten guarantees, panic dashboards, and termination SLAs.Votes: 0GitHub stars: 2
- Latency BudgetsLatency budget engineering for HFT systems — wire-to-wire targets, hot-path discipline (no allocations / no syscalls / no locks), GC pause analysis, NUMA placement, and continuous-measurement contracts.Votes: 0GitHub stars: 2
- Order RoutingOrder routing for high-frequency trading systems — venue selection, IOC/FOK semantics, child-order slicing, retry vs. cancel-on-error policies, and audit-trail completeness for surveillance.Votes: 0GitHub stars: 2
- Corporate Training DesignerCorporate L&D specialist covering the full instructional-design lifecycle: performance-gap diagnosis, learning-objective authoring at Bloom's taxonomy levels, curriculum architecture with spaced practice, blended-modality selection (synchronous ILT / asynchronous self-paced / SPOC cohort / on-the-job), formative and summative assessment design, and transfer-of- learning measurement via Kirkpatrick four levels and Phillips ROI. Use when a task involves needs analysis, courseware design, traine...Votes: 0GitHub stars: 2
- Voice Ai IntegrationProduction discipline for voice AI integration covering ASR provider selection (Whisper-large / AssemblyAI / Deepgram / Speechmatics / Google STT) by accuracy, latency, pricing, and language coverage; TTS provider selection (ElevenLabs / OpenAI / Cartesia / Azure Neural / Google Cloud TTS) with latency-to-first-byte and emotional control tradeoffs; real-time streaming via WebRTC and WebSocket with partial transcription and jitter buffer configuration; speaker diarization with error rate budge...Votes: 0GitHub stars: 2
- Accessibility And WcagWCAG 2.1 AA compliance, ARIA patterns, keyboard navigation, focus management, screen reader support, color contrast, and accessible data visualization for the {{PROJECT_NAME}} frontend. Use when reviewing or writing any interactive component, form, modal, chart, table, or page-level navigation. Also use when the user mentions "accessibility", "a11y", "ARIA", "screen reader", "keyboard", "focus trap", "contrast", "skip navigation", or when reviewing any component that displays data to ensure i...Votes: 0GitHub stars: 2
- Code Quality And TypescriptTypeScript strict mode governance, ESLint rule strategy, type assertion audit, dead code detection, circular dependency prevention, `:any` evaluation criteria, naming conventions, and code review quality gates for the {{PROJECT_NAME}} frontend. Use when reviewing TypeScript health, configuring ESLint rules, auditing type assertions, cleaning dead code, enforcing naming conventions, or when any code needs quality review before merge.Votes: 0GitHub stars: 2
- Design System And ComponentsDesign token governance, component architecture patterns, shared component organization, empty/loading/error state standards, component library integration (e.g. shadcn/ui, Material-UI, Chakra), responsive design, and visual consistency for the {{PROJECT_NAME}} frontend. Use when creating or reviewing components, organizing shared/, working with design tokens, implementing responsive layouts, or ensuring visual consistency across pages. Also use when the user mentions "design system", "compon...Votes: 0GitHub stars: 2
- Frontend AccessibilityAccessibility and internationalization for the {{PROJECT_NAME}} frontend. CoversVotes: 0GitHub stars: 2
- Frontend Data LayerUniversal frontend data-layer patterns — server state library architecture (e.g.Votes: 0GitHub stars: 2
- Frontend PatternsUniversal frontend development patterns for the {{PROJECT_NAME}} platform. Covers your build tool (e.g. Vite, Webpack) + your UI framework (e.g. React, Vue, Svelte) patterns, real-time data display (WebSocket client, SSE), virtualization for large lists, memoization strategies, composition patterns (compound components, render props, custom hooks), error boundaries, lazy loading and code splitting, responsive design, accessibility basics, and performance monitoring. Use when working on any fr...Votes: 0GitHub stars: 2
- Frontend Performance OptimizationBundle analysis, code splitting, lazy loading strategy, rendering optimization, virtualization patterns, Core Web Vitals targets, memoization correctness, network performance, image optimization, and build tool tuning (e.g. Vite) for the {{PROJECT_NAME}} frontend. Use when analyzing bundle size, optimizing rendering, adding virtualization to large lists, reviewing memoization patterns, tuning build config, or improving Core Web Vitals scores.Votes: 0GitHub stars: 2
- Ux And User JourneysUser experience design, journey mapping, information architecture, navigation patterns, responsive/mobile strategy, onboarding flows, empty state messaging, progressive disclosure, micro-interactions, and conversion-oriented UX for the {{PROJECT_NAME}} frontend. Use when designing new pages, reviewing user flows, optimizing onboarding, improving navigation, making the product more intuitive, or when the user mentions "UX", "user journey", "flow", "onboarding", "navigation", "mobile", "respons...Votes: 0GitHub stars: 2