All authors
Claude Skills by shennawardana23
github.com/shennawardana23150 skills1 installs86 views
- Apply CommentsApply pending @slide-comment markers written by the open-slide inspector tool. Use when the user asks to "apply comments", "process slide comments", "apply the inspector comments", or references markers left inside `slides/<id>/index.tsx`.Votes: 0GitHub stars: 2
- Create SlideUse this skill when the user wants to create, draft, author, or generate new slides / a presentation in this open-slide repo. Triggers on phrases like "make slides about X", "make a deck about X", "create a presentation", "draft slides for", "new slide", or when the user asks to add content under `slides/`. Do NOT use for editing the framework itself — only for authoring content inside `slides/<id>/`.Votes: 0GitHub stars: 2
- Create ThemeUse this skill when the user wants to create, draft, author, or extract a slide theme in this open-slide repo. Triggers on phrases like "create a theme", "make a theme called X", "extract a theme from <slide>", "build a theme from these images". Produces two paired files under `themes/` — `<id>.md` (palette, typography, layout, fixed Title/Footer components, motion) and `<id>.demo.tsx` (a runnable demo slide that the dev-UI Themes panel previews). Do NOT use for editing real slides — only for...Votes: 0GitHub stars: 2
- Current SlideResolve which slide, page, and (optionally) selected element the user is currently viewing in the open-slide dev server. Consult this whenever the user references "this page", "this slide", "this element", "the slide I'm on", "the current page", or any deictic reference to slide content without naming it. Re-read `node_modules/.open-slide/current.json` at the start of every such turn — the user navigates between turns, so a value you read earlier in the conversation is almost certainly stale.Votes: 0GitHub stars: 2
- Slide AuthoringTechnical reference for writing or editing open-slide pages — file contract, 1920×1080 canvas, type scale, layout, palette/visual direction, assets, stepped reveals, page transitions, and morph transitions. Consult this whenever you are about to write or modify any file under `slides/<id>/`, including from inside the `create-slide` or `apply-comments` workflows, or for any ad-hoc slide edit. Triggers on phrases like "edit slide", "tweak this page", "fix the layout", "change the palette", "rev...Votes: 0GitHub stars: 2
- CommandsValidate and run a skill's eval suite with smeval, then summarize the resultVotes: 0GitHub stars: 2
- CommandsScaffold a new skill directory following this repo's specVotes: 0GitHub stars: 2
- AccessibilityAudit and improve web accessibility following WCAG 2.2 guidelines. Use when asked to "improve accessibility", "a11y audit", "WCAG compliance", "screen reader support", "keyboard navigation", or "make accessible".Votes: 0GitHub stars: 2
- Adk Go Agent BuilderThis skill should be used when the user asks to "build an agent with ADK Go", "create an ADK agent in Go", "add a tool to my Go agent", "use google.golang.org/adk", "compose sub-agents in ADK Go", or writes Go code against Google's Agent Development Kit for Go (google.golang.org/adk/v2). Provides verified API patterns for agents, models, function tools, and multi-agent composition.Votes: 0GitHub stars: 2
- Agent Drift And Re AnchoringUse when a long-running agent session has drifted from its original goal, when reviewing why an agent kept working on something it wasn't asked to do, when designing checkpoint or re-anchoring behavior for an autonomous/long-horizon agent loop, or when asked about "agent focus", "agent losing the plot", or preventing an agent from going down a tangent.Votes: 0GitHub stars: 2
- Agent Harness ConstructionUse when designing or reviewing the tool/function interface an LLM agent calls through — naming and scoping tools, shaping observation payloads, writing error-recovery contracts, or deciding between ReAct-style and structured function-calling loops. Trigger phrases include "design a tool for the agent", "the agent keeps calling the wrong tool", "what should this tool return on error", "too many tools", or "the agent doesn't recover from failures".Votes: 0GitHub stars: 2
- Agentic EngineeringUse when planning how to hand an implementation task to an AI coding agent — deciding how to decompose the work, which model tier to route it to, when to define eval/regression criteria before starting, and where to focus human review of the agent's output. Trigger phrases include "break this down for the agent", "which model should handle this", "define done for this task", or "review this AI-generated change".Votes: 0GitHub stars: 2
- Ai Design Slop AuditThis skill should be used when the user wants an evidence-backed review of an existing UI for generic "AI-generated" design defaults — asking to "audit this design", "why does this look AI-generated", "review this for design slop", or wants a removal-first cleanup plan without a speculative redesign. Point-in-time audit of a screenshot, rendered page, or design code producing a prioritized, cite-the-evidence findings table. Does not edit anything and is not a build-time guide — see frontend-u...Votes: 0GitHub stars: 2
- Ai First EngineeringUse when designing team-level process, architecture standards, review policy, or hiring/evaluation criteria for an engineering org where AI agents generate a large share of the implementation. Trigger phrases include "how should our review process change for AI-generated code", "what architecture makes this codebase agent-friendly", "what should we test for in AI-first hiring", or "set testing standards for agent-written code". Not for single-task workflow — see agentic-engineering for that.Votes: 0GitHub stars: 2
- Ai Regression TestingUse when an AI coding agent has fixed a bug or modified API/backend logic and you need to prevent the same class of bug from recurring — especially in codebases with two parallel code paths (sandbox/mock mode vs production, or feature-flagged variants). Trigger phrases include "the agent keeps missing the same bug", "write a regression test for this fix", "check sandbox and production return the same fields", or "set up a bug-check workflow". Covers Go with the standard testing package and ta...Votes: 0GitHub stars: 2
- Animation Improvement PlanningThis skill should be used when the user asks to "improve the animations", "audit the motion across the app", "make this feel better" without a specific diff to review, or wants a prioritized roadmap of animation fixes rather than a single verdict. Surveys a codebase's motion, produces a severity-ranked findings table, then writes self-contained implementation plans an executor with zero context can follow. Read-only on source code — it never edits application code itself. Use animation-review...Votes: 0GitHub stars: 2
- Animation Opportunity ScanThis skill should be used when the user asks "what could be animated here?", "where should we add motion?", or wants the interface to "feel more alive" without saying what to change. Read-only sweep of a codebase or UI for moments that would genuinely benefit from motion, gated by frequency/purpose/duration/function so it proposes a short, high-conviction list instead of a wishlist. Does not implement anything and does not review existing animation — see animation-improvement-planning to turn...Votes: 0GitHub stars: 2
- Animation ReviewThis skill should be used when the user asks to "review this animation", "check this transition/motion code", "grade this animation diff", or wants a craft-bar pass over CSS/JS motion (transitions, keyframes, Framer Motion, GSAP, WAAPI). Reviews a diff or snippet against a fixed motion-craft bar and returns a findings table plus a block/approve verdict. Does not review non-motion code — see code-reviewer for that — and does not search for missing animation or plan a repo-wide motion audit — s...Votes: 0GitHub stars: 2
- Api And Interface DesignGuides internal interface and module-boundary design — Go interfaces, package APIs, and cross-team contracts inside a codebase, as distinct from the wire-level REST/RPC contract shape covered by the api-design skill. Use when defining an interface between packages, deciding where an interface should live, choosing between accepting an interface or a concrete type, evolving a public function signature without breaking callers, or reviewing a Go package's exported API for coupling and future fl...Votes: 0GitHub stars: 2
- Api DesignGuides REST and RPC API design across Go, TypeScript, and PHP backends. Use when designing new endpoints, defining request/response contracts, planning breaking or additive schema changes, or reviewing an existing API for consistency in error handling, pagination, or naming.Votes: 0GitHub stars: 2
- Autonomous LoopsUse when choosing or designing an architecture for running a coding agent repeatedly with little or no human intervention — a scripted sequence of non-interactive agent invocations, a parallel-generation loop, an iterative PR-and-merge loop, or a spec-driven multi-agent pipeline. Trigger phrases include "set up an autonomous loop", "run the agent in a pipeline", "which loop pattern should I use", "generate N variations in parallel", or "orchestrate multiple agents against an RFC". For operati...Votes: 0GitHub stars: 2
- Backend PatternsGuides backend service architecture — layering, N+1 query prevention, caching, retries, rate limiting, and background job processing, in Go primarily and TypeScript/PHP where the pattern is language-agnostic. Use when structuring handler/service/repository layers, reviewing a service for N+1 queries, adding a cache in front of a slow read, implementing retry logic, or setting up a background job queue.Votes: 0GitHub stars: 2
- Backward Compatibility And Deprecation PolicyUse when the user asks to "deprecate this endpoint/field", "set a sunset date", "plan a breaking change rollout", "write a deprecation notice", "how long should we support the old version", or is retiring an API version, a config format, a CLI flag, or an internal library's old interface. Guides the organizational process and timeline for deprecating something already shipped — not the contract-design question itself (see the api-design skill for that).Votes: 0GitHub stars: 2
- Best PracticesApply modern web development best practices for security, compatibility, and code quality. Use when asked to "apply best practices", "security audit", "modernize code", "code quality review", or "check for vulnerabilities".Votes: 0GitHub stars: 2
- Browser Testing With DevtoolsUse Chrome DevTools MCP to inspect, debug, and verify anything that runs in a browser — DOM structure, console errors, network requests, performance traces, and accessibility. Use when building or fixing browser UI, diagnosing a runtime bug that isn't visible from source code alone, or verifying a fix actually works instead of assuming it does. Requires the chrome-devtools MCP server.Votes: 0GitHub stars: 2
- Bug Triage And Severity ClassificationThis skill should be used when the user asks to "triage this bug", "what severity is this", "classify this incident/bug", "is this a Sev1 or Sev2", "what priority should this ticket be", or is deciding SLA/response urgency for a reported defect. Use for assigning severity and priority to bugs and incidents, distinguishing the two, and running a triage process — not for the technical debugging itself.Votes: 0GitHub stars: 2
- Channel Manager Ota IntegrationGuides integrating a hotel PMS with online travel agencies (OTAs) via a channel manager. Use when implementing rate/availability push, reservation pull, reconciling a channel-manager sync failure, or reviewing code that treats an OTA's view of availability as always in sync with the PMS.Votes: 0GitHub stars: 2
- Ci Cd And AutomationGuides CI/CD pipeline design — quality gates, GitHub Actions for Go/TypeScript/PHP, feature-flag-decoupled deploys, secrets scoping, and pipeline optimization. Use when setting up or modifying a build/test/deploy pipeline, adding an automated quality gate, configuring CI secrets, or diagnosing a slow or flaky pipeline. For the rollout strategy the pipeline triggers, see deployment-patterns; for the image it builds, see docker-patterns.Votes: 0GitHub stars: 2
- Code Ownership And BoundariesUse when the user asks to "set up CODEOWNERS", "who should review this", "define module boundaries", "this service keeps needing changes across three teams", "reorganize our repo structure", or is designing team/service boundaries, module ownership, or review-routing rules. Guides applying CODEOWNERS-based review routing and Conway's Law (system architecture mirrors org communication structure) to keep ownership boundaries matched to team structure.Votes: 0GitHub stars: 2
- Code Review And QualityRuns code review as a change-management process — right-sizing the diff, labeling findings by required-vs-optional severity, applying structural remedies for complexity, and resolving reviewer/author disagreements. Use when a change needs splitting before review, when review comments need severity labels, when a "should I approve this" call is being made, or when setting up a team's review process rather than auditing a single file.Votes: 0GitHub stars: 2
- Code ReviewReviews code changes for security, correctness, performance, and maintainability, in Go, TypeScript, PHP, Vue, or any language. Use when given a PR URL, a diff, or a file path; before merging a change; or when asked to check for injection risks, missing edge cases, missing authorization checks, or error-handling gaps.Votes: 0GitHub stars: 2
- Code ReviewerRuns a fixed-category severity scan over a diff, file, or snippet — correctness, security, error handling, concurrency, performance, readability, tests — and emits a CRITICAL/HIGH/MEDIUM/LOW/INFO-graded report. Use when asked to "scan this code", grade a change by severity, or review Go code for concurrency bugs (data races, goroutine leaks, deadlocks) alongside the usual review axes.Votes: 0GitHub stars: 2
- Code SimplificationSimplifies working code for clarity without changing behavior — reduces nesting, renames vague identifiers, removes dead code and unnecessary abstraction. Use when code works but is harder to read, maintain, or extend than it should be, or when a review flagged accumulated complexity. Not for adding features or fixing bugs — pair with test-generation or debug for those.Votes: 0GitHub stars: 2
- Coding StandardsCross-language code-quality heuristics -- function size, nesting depth, magic numbers, comment intent, naming -- for reviewing or writing code in any language. Use when reviewing code for maintainability, setting up lint rules, or onboarding conventions. For Go-specific idioms use go-service-idioms, for API contracts use api-design, for Laravel use laravel-patterns, for Vue/Nuxt use vue-nuxt-frontend-patterns -- this skill is the language-agnostic layer underneath those.Votes: 0GitHub stars: 2
- Compose Multiplatform PatternsPatterns for building shared UI across Android, iOS, Desktop, and Web with Compose Multiplatform and Jetpack Compose — state hoisting with ViewModel/StateFlow, type-safe navigation, slot-based composables, recomposition performance, and expect/actual platform code. Use when writing or reviewing Compose UI, wiring a ViewModel to a screen, debugging unnecessary recomposition, or adding platform-specific behavior in a KMP project.Votes: 0GitHub stars: 2
- Content EngineTurn one source asset (article, demo, launch memo, podcast) into strong, platform-native content for X, LinkedIn, TikTok/short-video, YouTube, or a newsletter instead of cross-posting the same copy everywhere. Use when the user wants social posts, threads, video scripts, a content calendar, or a launch repurposed across multiple platforms.Votes: 0GitHub stars: 2
- Content Hash Cache PatternCache expensive file-processing results (PDF parsing, OCR, text extraction, image analysis) keyed by a SHA-256 hash of file content rather than file path, so renamed files still hit the cache and changed content auto-invalidates it. Use when building a file-processing pipeline that reprocesses the same files across runs, or when adding a --cache/--no-cache option without touching the existing pure processing function.Votes: 0GitHub stars: 2
- Context EngineeringDeliberately curate what an agent sees, when, and how it's structured, to keep output quality high across a session. Use when starting a new coding session, when agent output quality is degrading (hallucinated APIs, ignored conventions), when switching between unrelated parts of a codebase, or when setting up a new project's rules files.Votes: 0GitHub stars: 2
- Continuous Agent LoopUse when a coding-agent loop is already running unattended and you need to define its quality gates, detect that it's stuck (churning without progress, retrying the same failure, cost drifting up), and recover it safely. Trigger phrases include "the loop has run 20 times with no progress", "the agent keeps failing the same way", "our autonomous run is costing more than expected", or "how do I add a quality gate to this loop". For choosing which loop architecture to build in the first place, s...Votes: 0GitHub stars: 2
- Continuous Learning V2Use when designing a fine-grained, hook-driven learning system that observes every tool call (not just session end), stores atomic "instincts" with confidence scores, and evolves clusters of related instincts into skills, commands, or agents — with project-scoped vs. global separation so React conventions don't leak into a Python repo. Trigger phrases include "observe every tool call for patterns", "score confidence on a learned behavior", "keep this pattern scoped to this project", or "clust...Votes: 0GitHub stars: 2
- Continuous LearningUse when setting up end-of-session extraction of reusable patterns (error resolutions, user corrections, workarounds, project conventions) from a Claude Code session into a saved skill file, via a Stop hook. Trigger phrases include "save what we learned this session", "extract a skill from this conversation", "set up a Stop hook for pattern extraction", or "turn this fix into a reusable skill". For a finer-grained, hook-driven approach with confidence scoring, see continuous-learning-v2.Votes: 0GitHub stars: 2
- Core Web VitalsOptimize Core Web Vitals (LCP, INP, CLS) for better page experience and search ranking. Use when asked to "improve Core Web Vitals", "fix LCP", "reduce CLS", "optimize INP", "page experience optimization", or "fix layout shifts".Votes: 0GitHub stars: 2
- Customs Trade ComplianceCodified expertise for customs documentation, tariff classification, duty optimization, restricted-party screening, and regulatory compliance across US/EU/UK/APAC jurisdictions, including HS classification logic, Incoterms application, FTA utilization, and penalty mitigation. Use when classifying goods, preparing customs documentation, screening trade parties, evaluating FTA/duty-savings opportunities, or responding to a customs audit or penalty notice.Votes: 0GitHub stars: 2
- Data Retention And Privacy By DesignUse when the user asks to "design a new data model that stores personal data", "add a retention policy", "figure out how long to keep guest data", "handle a data deletion request", "design for GDPR compliance", or is adding any field/table that captures a name, email, phone, ID document, or payment detail. Guides applying GDPR's data minimization principle and Ann Cavoukian's Privacy by Design framework at design time, not as a bolt-on compliance pass after launch.Votes: 0GitHub stars: 2
- Data Scraper AgentBuild an automated data-collection agent that scrapes a public source on a schedule, enriches results with a cheap/free LLM, stores them in a database, and improves scoring from user feedback over time — runnable entirely on free-tier infrastructure. Use when the user wants to monitor, collect, or track any public data automatically (job boards, prices, news, GitHub repos, sports scores, listings).Votes: 0GitHub stars: 2
- Database MigrationsGuides safe, reversible PostgreSQL schema and data migrations using golang-migrate, Prisma, Drizzle, or Django migrations. Use when creating or altering tables, adding or removing columns or indexes, planning a zero-downtime schema change, or reviewing a migration before it runs against production. For tables partitioned by hotel_id, use the postgres-hotel-partitioning skill alongside this one.Votes: 0GitHub stars: 2
- DebugRuns a tight four-phase loop — reproduce, isolate, diagnose, fix — to root-cause a single bug with evidence, not guesses. Use when given a specific error message, stack trace, or unexpected behavior for one bug and need a fast, mechanical session (reproduce → isolate → diagnose → fix → prevention). For broader failure-class triage across tests/builds/incidents, or a stop-the-line policy, use debugging-and-error-recovery instead.Votes: 0GitHub stars: 2
- Debugging And Error RecoveryEnforces a stop-the-line triage protocol across failure classes — test failures, build breaks, runtime errors, and production incidents — using bisection, safe-fallback design, and instrumentation lifecycle management. Use when any unexpected failure appears and the question is "what class of failure is this and what's the triage tree", not root-causing one already-identified bug (use debug for that tight four-phase loop instead).Votes: 0GitHub stars: 2
- Deep ResearchProduce a thorough, multi-source, cited research report on an open-ended topic using web search and page-fetch tools, optionally fanning out across parallel sub-agents for broad subjects. Use when the user wants a deep dive, investigation, or "what's the current state of X" report on any topic, not a narrow technical question or a business decision memo.Votes: 0GitHub stars: 2
- Defining Done And Acceptance CriteriaThis skill should be used when the user asks to write acceptance criteria for a user story, define or review a team's Definition of Done, evaluate whether a story is "ready" or "done", or asks things like "write Given/When/Then criteria for this story", "is this Definition of Done good enough", "why do we keep disagreeing about whether this is done", or "review this ticket before we start it". Distinguishes the team-wide Definition of Done from per-story acceptance criteria and applies INVEST...Votes: 0GitHub stars: 2