All authors
Claude Skills by shennawardana23
github.com/shennawardana23150 skills1 installs86 views
- Dependency And License PolicyUse when the user asks to "add a dependency", "vet a license", "check if this package is safe to use", "can we use this library", "add this to go.mod/package.json", or is preparing a proprietary/closed-source product that bundles open-source code. Guides license-compatibility review before a dependency is pulled in, distinguishing copyleft obligations (GPL/AGPL/LGPL) from permissive ones (MIT/Apache-2.0/BSD) and flagging when legal review is required.Votes: 0GitHub stars: 2
- Deployment PatternsGuides production rollout strategy — rolling/blue-green/canary deployments, liveness/readiness/startup probes, startup config validation, and rollback planning. Use when choosing a deployment strategy, implementing health check endpoints or Kubernetes probes, planning a rollback path before a release, or reviewing a production-readiness checklist before a launch. For building the container image itself, see docker-patterns; for the pipeline that runs the deploy, see ci-cd-and-automation.Votes: 0GitHub stars: 2
- Deprecation And MigrationGuides deprecating and removing old systems, APIs, or code, and migrating consumers to a replacement. Use when replacing a library, API, or internal system with a new one, sunsetting a feature, deciding whether to maintain or remove legacy code, or planning how a new system will eventually be retired.Votes: 0GitHub stars: 2
- Diff AnalysisAnalyzes a git diff or PR across three tracks — complexity, style/convention, and security impact — run together, then synthesized into a single risk-graded report with required actions cited to file:line. Use when given a raw diff, PR number, or branch to triage before merge, especially when the ask is "how risky is this change" rather than a full line-by-line review.Votes: 0GitHub stars: 2
- Docker PatternsGuides Dockerfile and Docker Compose design for local development and image builds — multi-stage builds, networking, volumes, and container security — primarily for Go services with TypeScript/PHP notes. Use when writing or reviewing a Dockerfile, setting up Docker Compose for local development, troubleshooting container networking or volume issues, or hardening a container image. For rollout strategy and health-probe design once an image is built, see deployment-patterns; for the pipeline th...Votes: 0GitHub stars: 2
- Documentation And AdrsRecord architecture decisions and documentation that capture why, not just what — use when making a significant architectural decision, choosing between competing approaches, changing a public API, shipping user-facing behavior, or documenting context a future engineer or agent will need.Votes: 0GitHub stars: 2
- Documentation LookupFetch current library and framework documentation via the Context7 MCP server instead of relying on training data. Use for setup or configuration questions, API references, code examples that depend on a library's behavior, or whenever the user names a specific framework or library (React, Next.js, Prisma, Supabase, etc.).Votes: 0GitHub stars: 2
- Doubt Driven DevelopmentSubjects a non-trivial decision to a fresh-context adversarial review before it stands, in-flight rather than as a post-hoc PR verdict. Use before an architectural decision under uncertainty, before committing non-trivial code, before asserting a non-obvious fact ("this is safe", "this scales", "this matches the spec"), or when working in code you don't fully understand.Votes: 0GitHub stars: 2
- E2e TestingGuides Playwright end-to-end test design — Page Object Model, CI configuration, and flaky test diagnosis. Use when writing browser-based end-to-end tests, debugging a test that fails intermittently, setting up Playwright CI configuration, or reviewing E2E test code for race conditions and arbitrary waits.Votes: 0GitHub stars: 2
- Engineering Onboarding DesignThis skill should be used when the user asks to "design an onboarding plan", "write a 30/60/90 day plan for a new engineer", "set up onboarding for a new hire", "what should a new engineer do in their first week", or is structuring how a new engineer ramps up on a team/codebase. Use for the structure and cadence of onboarding a new engineer — not for the content of technical documentation itself.Votes: 0GitHub stars: 2
- Engineering Values And Tradeoff PrinciplesUse when the user asks to "should we prioritize shipping fast or reliability here", "define an error budget", "how much risk can we take on this release", "we keep debating speed vs quality", "write down our engineering principles", or is deciding how to balance reliability/velocity/quality tradeoffs at a policy level rather than for one specific decision. Guides turning a philosophical tradeoff into an operational, measurable policy, grounded in Google SRE's error budget concept.Votes: 0GitHub stars: 2
- Erd ExpertDesigns entity-relationship schemas for the hotel domain (reservations, guests, rooms, rate plans, folios) on PostgreSQL, following Archipelago International's Sentec platform conventions — hotel_id LIST partitioning, naming, and required audit columns. Use when designing a new table or ERD for Sentec PMS, Sentec Booking Engine, or Sentec EMS, when reviewing a proposed schema against org conventions, or when modeling the reservation lifecycle or room-availability queries.Votes: 0GitHub stars: 2
- Error Handling PhilosophyUse when the user asks to "review error handling in this code", "should this panic or return an error", "design an error type", "how should this function report failure", or is writing Go code with error returns, panics, or wrapping. Guides applying Go's "errors are values" philosophy (Rob Pike) — explicit error returns over exceptions, wrapping with %w for context, and reserving panic for truly unrecoverable programmer errors.Votes: 0GitHub stars: 2
- Eval HarnessSets up eval-driven development (EDD) for an agent-assisted feature — define capability and regression evals before coding, grade them with code/model/human graders, and track reliability with pass@k and pass^k metrics. Use when defining pass/fail criteria for an AI coding task before implementation starts, measuring agent reliability across repeated attempts, or building a regression suite that guards prompt or agent changes.Votes: 0GitHub stars: 2
- Experiment Design And Ab TestingGuides the product-experimentation layer of A/B testing — writing a falsifiable hypothesis, sizing a test with minimum detectable effect (MDE), reading statistical significance without falling into the peeking problem, accounting for the novelty effect, and choosing guardrail metrics. Use when the user asks to "design an A/B test", "how big a sample do I need", "can we stop this test early, it hit p<0.05", "is this result significant", "what guardrail metrics should we track", or wants to rev...Votes: 0GitHub stars: 2
- Exploratory Testing TechniquesThis skill should be used when the user asks to "do some exploratory testing", "write a test charter", "explore this feature for bugs", "run a testing session", or needs an unscripted, human-judgment-driven approach to finding bugs in an ambiguous or newly-built feature that isn't well-specified enough for scripted automation yet. Use for structured, charter-driven manual investigation — not for writing automated Playwright/unit tests (see e2e-testing, test-driven-development).Votes: 0GitHub stars: 2
- Feature Prioritization FrameworksGuides prioritizing a backlog of features or requests using RICE scoring (Reach x Impact x Confidence / Effort) as the primary quantitative method, with MoSCoW (Must/Should/Could/Won't) for stakeholder negotiation and the Kano model for classifying features by satisfaction-curve shape. Use when the user asks to "prioritize these features", "rank this backlog", "score with RICE", "do a MoSCoW", "apply Kano", or gives a list of feature requests and asks which to build first.Votes: 0GitHub stars: 2
- Frontend PatternsFramework-agnostic client-side performance architecture — route/component code splitting, list virtualization mechanics, hydration cost, and asset loading strategy. Use when a page feels slow to load or interact with, when deciding whether/how to split a bundle or lazy-load a component, when a long list janks while scrolling, or when triaging SSR hydration cost. Complements vue-nuxt-frontend-patterns (reactivity/SSR fetching) and frontend-ui-engineering (component/accessibility patterns) rath...Votes: 0GitHub stars: 2
- Frontend SlidesCreate zero-dependency, animation-rich HTML presentations that run entirely in a browser, from a topic/draft or by converting a PowerPoint file. Use when the user wants a talk deck, pitch deck, workshop deck, or wants a .ppt/.pptx converted to a web presentation. Helps users without a clear aesthetic preference discover one through visual previews rather than an abstract questionnaire.Votes: 0GitHub stars: 2
- Frontend Ui EngineeringBuild production-quality, accessible, non-generic-looking UI components and pages — component composition, the state-management ladder (local to global), avoiding the recognizable "AI aesthetic," WCAG 2.1 AA accessibility, and responsive/loading/empty states. Use when building or modifying user-facing interfaces, or when output needs to look like it was built by a design-aware engineer rather than generated by a model.Votes: 0GitHub stars: 2
- Genkit Go FlowsGuides building AI features with Genkit for Go - flows, prompts, structured generation, tool calling, and middleware. Use when defining a Genkit flow, writing a prompt, calling genkit.Generate/GenerateData, defining a tool, debugging Genkit output with traces, or asked how Genkit differs from Google's Agent Development Kit (ADK).Votes: 0GitHub stars: 2
- Gin Lambda Api Service PatternsGuides Go API services built with Gin and deployed as a serverless function (AWS Lambda via an API-Gateway adapter) alongside a local HTTP-server dev mode. Use when touching a service's entrypoint, its dual local/serverless run paths, its build-and-deploy pipeline, or reviewing why a change that works locally behaves differently once deployed.Votes: 0GitHub stars: 2
- Git Workflow And VersioningGuides git commit discipline, trunk-based branching, and semantic versioning/changelogs for released code, including Go modules' major-version import path rule. Use when committing, branching, resolving conflicts, cutting a release, choosing a semantic version bump, tagging a release, or writing a changelog entry.Votes: 0GitHub stars: 2
- Go ExpertUse when writing or reviewing Go code that starts goroutines, holds a sync.Mutex/RWMutex, or closes channels - to enforce goroutine lifecycle ownership, lock-hygiene, and channel-close-side rules, and to wire up the detection tooling (go test -race, go vet, go.uber.org/goleak) that catches violations tests alone won't. Use when the user asks "review this Go concurrency code," "why is this goroutine leaking," or "is this Go code race-safe."Votes: 0GitHub stars: 2
- Go Service IdiomsThis skill should be used when the user asks to "write a Go function", "implement this in Go", "structure this Go service", "add error handling in Go", "handle context cancellation in Go", "write a Go worker pool", "add a table-driven test", "review this Go code for idioms", or otherwise writes or reviews Go backend/service code. Provides idiomatic Go patterns for error handling, context propagation, concurrency, package layout, and testing.Votes: 0GitHub stars: 2
- Golang ConcurrencyThis skill should be used when the user asks to "review this Go code for goroutine leaks", "should I use a channel or a mutex", "use sync.WaitGroup vs errgroup", "audit this Go code for race conditions", "write a Go pipeline with fan-out/fan-in", "add a bounded worker pool in Go", or is choosing between sync primitives, debugging a goroutine leak, or designing a concurrent pipeline. For the one-paragraph "use errgroup for fanning out work" default in ordinary service code, use go-service-idio...Votes: 0GitHub stars: 2
- Golang ContextThis skill should be used when the user asks to "add a timeout to this Go call", "why isn't context cancellation propagating", "should I store context in a struct", "use context.WithValue", "compose context timeouts", "detach a context from its parent's cancellation", or is designing how context.Context deadlines, cancellation, and values flow through a Go call chain. go-service-idioms already covers "thread ctx as the first parameter" as a basic default; this skill is for the deeper composit...Votes: 0GitHub stars: 2
- Golang DatabaseThis skill should be used when the user asks to "configure a Go database connection pool", "use database/sql in Go", "set up pgxpool", "why is my Go app running out of connections", "scan rows into a Go struct", "handle sql.ErrNoRows", or writes Go code that opens, pools, queries, or scans a PostgreSQL/MySQL connection via database/sql or pgx. postgres-patterns and mysql-patterns cover the SQL/schema layer (indexes, data types, query shape); database-migrations covers schema evolution; this s...Votes: 0GitHub stars: 2
- Golang Dependency InjectionThis skill should be used when the user asks to "wire up dependencies in Go without a framework", "should I use wire, dig, fx, or samber/do", "generate a Go dependency injection container", "add a lifecycle hook to an fx app", "why does my dig container fail to invoke", or is choosing between or implementing google/wire, uber-go/dig, uber-go/fx, or samber/do for constructing a Go application's dependency graph. go-service-idioms's default is manual constructor functions wired by hand in main(...Votes: 0GitHub stars: 2
- Golang GrpcThis skill should be used when the user asks to "write a gRPC service in Go", "add a gRPC interceptor", "return a gRPC status error", "stream data over gRPC in Go", "chain gRPC unary interceptors", or writes or reviews Go code using google.golang.org/grpc — server/client setup, interceptors, streaming, deadlines, or status codes. Distinct from golang-context (general context composition) and jwt-tenant-scoped-authorization (HTTP-oriented tenant auth) — this skill is specifically about gRPC's ...Votes: 0GitHub stars: 2
- Golang PatternsUse when designing Go struct/interface APIs or optimizing allocation-heavy hot paths - functional options for constructors, defining narrow consumer-side interfaces, making zero values useful, and reducing allocations with preallocated slices, strings.Builder, and sync.Pool. For error handling, context propagation, or basic package layout use go-service-idioms instead; this skill is about API shape and allocation efficiency, not service plumbing.Votes: 0GitHub stars: 2
- Golang TestingUse when asked to benchmark Go code, compare Go implementations for performance, add a fuzz test, or investigate allocations on a hot path - covers go test -bench/-benchmem, sub-benchmarks, benchstat for noise-resistant comparison, and native fuzzing (testing.F). For basic table-driven unit tests use go-service-idioms or test-driven-development instead; this skill is specifically about benchmark-driven optimization and property-style fuzz testing.Votes: 0GitHub stars: 2
- Hotel Rate And Inventory ModelingGuides modeling hotel rate plans, room inventory, and availability/allotment for a multi-brand, multi-property hotel management company. Use when designing a rate plan or room-type schema, implementing availability or overbooking logic, modeling allotment across a channel manager, or reviewing a design that conflates rate and inventory concerns.Votes: 0GitHub stars: 2
- Idea RefineRefine a vague or raw idea into a sharp, actionable concept through structured divergent-then-convergent ideation — expand into variations, stress-test the strongest directions, then ship a one-page brief. Use when an idea is still fuzzy, when the user wants options before committing to one direction, or when they say "ideate on this" or "stress-test my plan".Votes: 0GitHub stars: 2
- Idempotency And Retry SafetyUse when the user asks to "make this endpoint safe to retry", "add an idempotency key", "handle duplicate webhook delivery", "design a payment/booking API", "what happens if this request is sent twice", or is building any endpoint or message consumer that a client, queue, or upstream system might call more than once for the same logical operation. Guides designing idempotency keys and safe retry semantics under at-least-once delivery.Votes: 0GitHub stars: 2
- Incident Response And PostmortemsThis skill should be used when the user asks to "write a postmortem", "run an incident retro", "do a blameless postmortem", "document this outage", or is drafting an incident timeline, root cause analysis, or action items after a production incident. Use for the incident-response process and the after-the-fact postmortem document — not for the live technical debugging itself (see the diagnose/debugging skills for that).Votes: 0GitHub stars: 2
- Incremental ImplementationBuilds in thin vertical slices -- implement one piece, test it, verify it, commit, then expand -- instead of writing a whole feature in one pass. Use when implementing any change touching more than one file, when a task feels too large to start, or before writing more than roughly 100 lines without running anything.Votes: 0GitHub stars: 2
- Interview MeExtract what a user actually wants, rather than what convention makes them ask for, via a one-question-at-a-time interview with a stated confidence level until reaching roughly 95% confidence in the underlying intent. Use when a request is underspecified (missing who/why/success/constraint), when the user says "interview me" or "are we sure?", or before any plan/spec/code exists for a non-trivial ask.Votes: 0GitHub stars: 2
- Jwt Tenant Scoped AuthorizationGuides multi-tenant authorization where a JWT claim carries a tenant/organization identifier that every endpoint must check against the resource being accessed. Use when adding a new endpoint to a multi-tenant API, reviewing JWT-based auth code, deciding what a JWT claim should carry, or investigating a cross-tenant data access report.Votes: 0GitHub stars: 2
- Laravel PatternsGuides Laravel application architecture — controllers, Eloquent, service/action layers, queues, and API resources. Use when building Laravel controllers or routes, working with Eloquent models and relationships, designing API resources, or adding queued jobs, events, or caching to a Laravel app.Votes: 0GitHub stars: 2
- Laravel SecurityUse when configuring Laravel-specific auth/session/CSRF/authorization plumbing - Sanctum SPA authentication, session cookie hardening, policy/gate wiring, mass-assignment guards, signed URLs, or encrypted casts. For generic web-security review (injection, secrets, auth-vs-authz on any stack) use security-review instead; this skill is for getting Laravel's own framework mechanisms configured correctly.Votes: 0GitHub stars: 2
- Laravel TddDrives Laravel feature development with Pest or PHPUnit — factories, RefreshDatabase, fakes for queues/mail/notifications, Sanctum auth, and Inertia assertions. Use when writing or fixing a Laravel controller, Eloquent model, policy, job, or notification, when the project uses Pest/PHPUnit, or when asked to test an Inertia page's props.Votes: 0GitHub stars: 2
- Laravel VerificationUse when asked to verify a Laravel project before a PR, after a major refactor or dependency upgrade, or before deploying to staging/production. Runs a phased env-check -> lint -> test -> security -> migration -> deploy-readiness -> queue pipeline, stopping at the first failing gate rather than reporting every phase's output at once.Votes: 0GitHub stars: 2
- Layered Logging And Alerting PatternsGuides services where a single logging call fans out to multiple side effects - error tracking (e.g. Sentry), a centralized log-shipping endpoint, and chat/webhook alerting - rather than just writing a log line. Use when adding a log statement to a service with this shape, reviewing why removing a "log statement" broke alerting, or designing observability for a service with more than one logging sink.Votes: 0GitHub stars: 2
- Lifecycle PlannerExecute a full development lifecycle for a feature or bug fix in one pass — requirements, technical design, implementation, self-review, and a gated approval — rather than jumping straight to code. Use for feature requests, bug fixes, or technical changes that need multiple coordinated steps, especially in Go services.Votes: 0GitHub stars: 2
- Market ResearchConduct business market research, competitive analysis, investor due diligence, and market-sizing that supports a business decision rather than producing research theater. Use when sizing a market (TAM/SAM/SOM), comparing competitors, vetting an investor or fund before outreach, or evaluating a vendor/technology adoption decision.Votes: 0GitHub stars: 2
- Mcp Server PatternsGuides building Model Context Protocol (MCP) servers — tools, resources, prompts, transport choice, and schema validation — biased toward the official Go SDK with TypeScript SDK notes where it differs. Use when implementing a new MCP server, adding a tool or resource to an existing one, choosing between stdio and HTTP transport, or debugging MCP registration and transport issues.Votes: 0GitHub stars: 2
- Me On ReviewThis skill should be used when the user asks to "review this PR/repo as me", "compile a review of these changes", "give me a human-readable summary of this code review", or wants a whole pull request, branch, or repository's changes turned into one narrative report in their own voice rather than a per-file finding list. Aggregates and compiles findings across multiple files/commits into a single readable report with a merge/no-merge call, applying Archipelago/Sentec-specific lenses (PostgreSQ...Votes: 0GitHub stars: 2
- Metrics And North Star FrameworksThis skill should be used when the user asks to define a North Star Metric, choose input/driver metrics for a product, diagnose a funnel using AARRR or "Pirate Metrics" (Acquisition, Activation, Retention, Referral, Revenue), or asks things like "what metric should we rally the team around", "where in the funnel are we losing users", "signups are up but usage isn't, what does that mean", or "help me build a metrics tree for this product". Combines the North Star Metric framework with AARRR to...Votes: 0GitHub stars: 2
- Multi Agent OrchestrationUse when designing a system where one agent delegates to multiple subagents/workers, deciding whether a task should fan out to multiple agents at all, decomposing a task without creating a "telephone game" handoff chain, or reviewing why an orchestrator's subagents are duplicating work, leaving gaps, or declaring success too early. Distinct from the orchestrator skill (single-session skill routing) - this skill covers dispatching work to separate agent instances.Votes: 0GitHub stars: 2