Claude Skills by peterbamuhigire

Use when building, reviewing, modernising, or debugging C# and .NET applications, including ASP.NET Core, EF Core, background services, concurrency, .NET MAUI, testing, packaging, and AI integration.

Use when writing or reviewing modern JavaScript for browser or PHP-backed SaaS applications, including modules, asynchronous flows, error handling, language features, and performance.

Use when creating Node.js backend services, APIs, routing, workers, CLI tools, streams, asynchronous or real-time workflows, production logging, tests, scaling, and deployment; use online-multiplayer-and-game-backend for authoritative game servers.

Use when writing or reviewing PHP 8+ applications, object-oriented domain code, Laravel services, PSR-compliant packages, secure request handling, tests, or performance-sensitive PHP.

Use when computing complex analytics, KPIs, cohort/funnel/retention metrics, financial math (IRR/NPV/amortization), statistical tests, anomaly detection, or geospatial analytics in Python — for cases where SQL alone gets unwieldy.

Use when building ETL jobs, document intelligence pipelines, OCR, PDF/Excel ingestion, image/media processing, or external-API sync pipelines in Python — idempotent scheduled jobs with validation, dead-letter queues, and multi-tenant isolation.

Use when adding forecasting, classification, regression, or anomaly detection to a SaaS feature — demand/sales/cash-flow forecasting, churn and risk scoring, anomaly detection — with scikit-learn, Prophet, and statsmodels. Covers data prep, model serving, monitoring, and explainability.

Use when writing, reviewing, or distributing Python applications, including PyInstaller, auto-py-to-exe, Nuitka, frozen desktop executables, multi-tool suites, installers, and CI release builds. Defines the Python baseline and routes executable packaging to its desktop-distribution automation.

Use when writing production TypeScript — clean code idioms, effective-TS items, strict tsconfig, migration from JS, build performance, testing, and anti-patterns. Load references/typescript-mastery.md for type-system depth and references/typescript-design-patterns.md for GoF patterns.

Use when building end-to-end TypeScript applications — Node backend (Fastify), React/Next frontend, shared types via tRPC or Zod, monorepo with turborepo/nx, Prisma/Drizzle data layer, end-to-end type safety.

Use when sharing Kotlin business logic across Android and iOS with Kotlin Multiplatform while retaining deliberate platform boundaries; use native development skills for platform UI and release work.

Use when coordinating Android/iOS testing, signing, store assets, TestFlight, Xcode Cloud, App Store/Play review, staged release, rollback, RBAC operations, and cross-platform release evidence.

Use when building offline-first Progressive Web Apps — Service Worker lifecycle, Workbox caching strategies, IndexedDB via Dexie.js, Background Sync for queued writes, Web Push notifications, Lighthouse gates, and Next.js PWA integration. Default for apps that must work on EDGE/2G or intermittent connectivity.

Use when specifying application intake, eligibility screening, selection scoring, beneficiary registers, diagnostics tracking, expert deployment, monitoring dashboards, RBAC, audit trails, and donor reporting for BDS programmes.

Use when coordinating multi-workstream consulting bids or delivery programmes with deadlines, owners, RACI, RAID, deliverables registers, decision logs, quality gates, and client/donor reporting cadence.

Use when writing or reviewing blog posts, long-form articles, website copy, headlines, ledes, persuasive content, readability, or scannable editorial structure; use ux-content-strategy for interface microcopy and product states.

Use when handling service recovery, escalations, complaints, apology language, frontline empowerment, CX measurement, or prevention loops.

Use when checking whether this machine can generate, open, render, and validate promised Word/DOCX, PDF, Excel/XLSX, workbook, scoring register, budget, report, or dashboard files before committing to delivery.

Use when generating or validating professional Excel workbooks, formulas, imports, charts, formatting, macros, or spreadsheet deliverables.

Use when planning, drafting, reviewing, or strengthening an IT proposal, win strategy, decision basis, pricing narrative, or persuasive structure.

Use when designing, pricing, packaging, building, or reviewing premium software for executive, enterprise, affluent, or high-ticket buyers.

Use when testing whether a product, feature, or workflow deserves investment through risk framing, prototypes, research, and build-pivot-kill decisions.

Use when designing PLG motions for a SaaS product — freemium tiers, PQL definition, activation flows with time-to-value targets, in-app upgrade prompts, viral loops, NPS surveys, feature flags for gradual rollout, and PostHog-based product analytics for funnel and cohort tracking.

Use when defining product vision, strategic choices, product principles, OKRs, outcome roadmaps, or an innovation-of-meaning direction.

Use when generating or validating a professionally structured and visually intentional Microsoft Word DOCX document.

Use when selecting or reviewing a software product, service, hybrid, platform, subscription, perpetual, open-source, or transition business model.

Use when designing or reviewing software pricing, packaging, value metrics, tiers, freemium, discounts, negotiation, or willingness-to-pay tests.

Use when populating, refreshing, replaying, resetting, or verifying a realistic synthetic SaaS demo tenant across procurement, inventory, production, sales, finance, reporting, UI/API/application boundaries, isolation, reconciliation, and idempotency.

Use when designing tenant-selectable SaaS modules, dependency contracts, module toggles, lifecycle hooks, or safe enable and disable behaviour.

Use when designing tenant isolation, panel boundaries, zero-trust authorization, audit trails, or tenant permission overrides.

Use when designing double-entry accounting inside SaaS, including automated postings, ledgers, controls, reconciliations, and reports.

Use when designing audited SaaS back-office impersonation, tenant lifecycle, billing overrides, bulk actions, or audit controls.

Use when architecting or evaluating a cloud SaaS product — including choosing multi-tenant patterns, mapping deployment to IaaS, planning scaling and blast-radius isolation, aligning architecture to business capabilities, and reconciling multi-enterprise consumption requirements with operating-model constraints.

Use when defining or reviewing SaaS revenue, growth, retention, engagement, satisfaction, unit economics, or Rule-of-40 metrics.

Use when gating which SaaS plan or AI model tier unlocks seats, API calls, generations, context, tools, or quotas, including tenant overrides, denial behaviour, upgrade discovery, and runtime permission resolution.

Use when designing configurable SaaS or ERP platforms with multi-step business workflows, domain modules, approvals, auditability, pricing and entitlements, operational reporting, and tenant-specific variation. Covers domain boundaries, workflow states, extension points, and control design.

Use when deriving SaaS lifecycle email decisions from user state, product events, consent, channel pressure, suppression, and measurable outcomes; use the design engine for each message's visual composition and the writing route for its words.

Use when implementing or reviewing Super Admin or tenant-scoped managed visual assets—background image pools, light/dark logos, or favicons—with secure upload, preview, ordering, activation, replacement, quotas, and audit evidence.

Use when designing per-tenant rate limits, quota algorithms, enforcement points, plan caps, fair queueing, or usage reporting.

Use when designing or scaling a SaaS sales organisation — sales motions, roles (SDR/BDR/AE/CSM/SE), pipeline stages, lead-to-cash, territory design, quota/commission, sales ops fundamentals, onboarding/ramp, and hiring rubrics. Sourced from "Blueprints for a SaaS Sales Organization" (van der Kooij, Pizarro).

Use when bootstrapping a multi-tenant SaaS Seeder Template, including environment, database, super admin, panel verification, recurring demo activity refreshes, and demo-login shortcuts.

Use when implementing tenant-scoped SAML or OIDC SSO, SCIM provisioning, custom domains, IP allowlists, or enterprise auth migration.

Use when designing verified tenant data export, retention, erasure, backup handling, audit evidence, or privacy-law portability workflows.

Use when integrating Stripe one-time payments, PaymentIntents, SetupIntents, Checkout, SCA, multi-currency, idempotency, or webhooks.

Use when designing or reviewing recurring subscription lifecycle on Stripe Billing — plans/Prices, trials, proration, upgrades/downgrades, cancel/pause, Smart Retries dunning, metered usage, automatic tax, multi-currency, and the strategy choice between subscription vs perpetual and monthly vs annual.

Use when designing or reviewing test strategy for production systems, APIs, mobile apps, SaaS platforms, ERP workflows, and AI-enabled systems. Covers unit, integration, contract, end-to-end, regression, release-gate, and risk-based testing decisions.

Use when coordinating AI-assisted planning, implementation, review, modernisation, documentation, human approval, CI evidence, or bounded multi-agent software work.

Use when auditing or scoring an artefact for AI slop after a major iteration or before release. Produces evidence-backed findings, severity, fixes, genericness score, and an A/B/C/F verdict.

Use when producing any human-facing artefact. Applies real-time anti-slop controls for specificity, verification, authored intent, hard cases, language, code, UI, and release quality.

Use when generating or repairing layered AGENTS.md project guidance from verified repository structure, technology, data, and planning conventions.