Explore skills
Showing 54421–54450 of 71492 skills
Audit and fix HTML accessibility issues including ARIA labels, keyboard navigation, focus management, color contrast, and form errors. Use when adding interactive controls, forms, dialogs, or reviewing WCAG compliance.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexAudit and fix animation performance issues including layout thrashing, compositor properties, scroll-linked motion, and blur effects. Use when animations stutter, transitions jank, or reviewing CSS/JS animation performance.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexAccessibility patterns for React and Next.js — semantic HTML, ARIA attributes, form labeling, keyboard navigation, focus management, and screen reader support. Use when building any interactive UI component or form.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexSound in the arcade: the synthesised blip vocabulary and what each cue means, why the AudioContext is built lazily, the mute preference, the per-frame cap that stops a cascade becoming noise, and the OfflineAudioContext plan for the native port. Use when adding or changing a sound, when a cue fires at the wrong moment or not at all, or when tuning how a drop sounds.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexJuice craft for this arcade: hit-stop, staged reveals, easing that reads as mechanical, audio pitch as information, and the difference between feedback that is legible and feedback that is merely loud. Use when adding or tuning any animation, sound, screen effect or score presentation, or when a moment that should feel good does not.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexMap of the Payload engine-builder: the marble simulation, how parts, blueprints, jams and difficulties are declared, and the invariants that keep runs deterministic and fair. Use when adding or changing a part, blueprint, jam, difficulty or quota, when a drop scores wrong, or when marbles animate out of sync with what actually fired.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexHow this arcade ships as an installable PWA: the service worker's cache strategy and version bump, the deliberate no-skipWaiting decision and the update prompt that completes it, what is safe to precache and what is not, and the stale-build trap that makes a fix look like it did not work. Use when touching public/sw.js, the manifest, offline behaviour, caching, or when a change you just built is not showing up in the browser.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexReact 18/19 patterns including hooks discipline, server/client component boundaries, Suspense + error boundaries, form actions, data fetching, state management decision trees, and accessibility-first composition. Use when writing or reviewing React components.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexReact and Next.js performance optimization patterns adapted from Vercel Engineering's React Best Practices (https://github.com/vercel-labs/agent-skills). Organizes 70+ rules across 8 priority categories — waterfalls, bundle size, server-side, client fetching, re-render, rendering, JS micro-perf, advanced. Use when writing, reviewing, or refactoring React/Next.js code for performance.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexReact component testing with React Testing Library, Vitest/Jest, MSW for network mocking, accessibility assertions with axe, and the decision boundary between component tests and Playwright/Cypress end-to-end runs. Use when writing or fixing tests for React components, hooks, or pages.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexTypeScript conventions for modelling this game's state: discriminated unions for phases, branded ids, exhaustive part handling, and keeping the pure rules engine free of any renderer. Use when writing or changing types in src/game, adding a part or blueprint, or designing the shared core that both the web and a future native build consume.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexRun and verify this repo's games for real: which of them build and which are single files, how to drive a game in the browser pane, how to bot-play a full run to check balance, and the gates to clear before calling it done. Use when asked to run, start, preview, screenshot, test or verify Payload or Ledger Lane, or to confirm a change actually works rather than only reading right.
gagandeepgill/puzzle-game
Stars: 0Claude CodeCodexRun all the CI code-analysis gates locally against a change, before opening a PR, so failures are caught in seconds instead of after a full pipeline cycle. Use when the user says "run the gates", "check before I push", "will CI pass", "run the CI checks locally", "did I break a gate", or "pre-PR check", or as the verification step at the end of a change. Do NOT use to evaluate a skill's quality (that is governance-validate-skills) or to validate only the artifact graph and docs wiki (that is governance-check-graph); this runs the whole gate set the pipeline runs.
tsunami28/MindNova
Stars: 0Claude CodeCodexMap the customer journey and opportunity landscape for a discovery theme as a diagram, exposing pains and opportunities before any solutioning. Use when the work needs a visual of the experience: phrasings like "map the customer journey", "draw a journey map", "where do users feel pain in this flow", "lay out the opportunity landscape", "visualise the as-is experience", "what are the stages and pain points", or when a Discovery/Spike needs its journey made navigable. Do NOT use to run or synthesise the research itself (that is discovery-synthesize-research), to frame the riskiest assumptions (that is discovery-upsert-hypothesis-canvas), to turn opportunities into stories or create tickets (that is elaboration-upsert-user-story), or to add links to an existing issue (that is governance-enrich-ticket).
tsunami28/MindNova
Stars: 0Claude CodeCodexTurn raw research into a synthesis anchored on a local Discovery/Spike work item under docs/discovery/. Use when research has been gathered and needs to become navigable findings: phrasings like "synthesise this research", "write up the interview findings", "summarise the research study", "what did the user research conclude", "turn this research into something the team can act on", "anchor this study to a Spike", or when discovery work is done and should feed elaboration. This is the entry point to the discovery phase. Do NOT use to run or collect the research itself (that happens upstream), to create an ordinary feature story (that is elaboration-upsert-user-story), to author an ADR (governance-author-adr), or to add links to an already-synthesised item (governance-enrich-ticket).
tsunami28/MindNova
Stars: 0Claude CodeCodexCapture a product hypothesis (lean canvas) for a discovery theme so discovery stays evidence-driven, not opinion-driven. Use when a discovery direction needs framing before work proceeds: phrasings like "what's our hypothesis here", "frame this as a hypothesis", "write a lean canvas", "what are we assuming", "what's the riskiest assumption", "how would we validate this", "is this a fact or a guess", or when research has surfaced a belief that should be stated and tested. Do NOT use to synthesise raw research (that is discovery-synthesize-research), to write a full PRD or map stories (that is elaboration-upsert-prd-document / elaboration-upsert-user-story), or to author an ADR (governance-author-adr).
tsunami28/MindNova
Stars: 0Claude CodeCodexWrite a Product Requirements Document for an initiative or epic - the problem, goals, scope, requirements, and success metrics - as the elaboration-phase anchor that stories derive from. Use when an initiative needs framing before it is sliced into work: phrasings like "write a PRD", "draft the product requirements", "what are the requirements for this epic", "spec out this initiative", "what's in and out of scope", "define success for MN-10", or when a confirmed hypothesis is ready to become a buildable epic. Do NOT use to capture an early hypothesis (that is discovery-upsert-hypothesis-canvas), to slice a PRD into stories (elaboration-upsert-user-story), to design the API contract (elaboration-upsert-api-contract), or to author an ADR (governance-author-adr).
tsunami28/MindNova
Stars: 0Claude CodeCodexCreate or draft new work items (stories, tasks, bugs, epics) as local markdown files under docs/discovery/, following the house story template, point scale, and conventions. Use this whenever the user wants a new work item: phrasings like "create" or "write up a story", "make a ticket", "log a bug" or "ops task", "create an epic", "raise a ticket", or any description of work that should be tracked as a new item, even when they only describe the work rather than naming a ticket. Do NOT use this for reading, searching, commenting on, transitioning, or reviewing existing tickets; for GitHub issues or pull items, GitHub issues or pull requests, Confluence pages, or PRDs; or for a bare "what points would you give" estimate when there is no ticket to create.
tsunami28/MindNova
Stars: 0Claude CodeCodexDerive clear, testable acceptance criteria for a story and define the test-trait mapping that lets the deferred AC-coverage gate attach with no rework. Use when the user says "write the acceptance criteria", "define the ACs for MN-42", "what are the success criteria for this story", "make these criteria testable", "turn this story into checkable conditions", or "set up the AC-to-test mapping" - and when a story is being refined for build but its success criteria are vague or untestable. Do NOT use to CREATE the story (that is elaboration-upsert-user-story), to implement or tag the tests (that is create-code-generation), or to write the work item fields directly (defer that to governance-enrich-ticket).
tsunami28/MindNova
Stars: 0Claude CodeCodexValidate documentation and graph integrity across the repo: the AI-SDLC artifact graph (every artifact declaring a `story:` has a valid work-item key, a known phase, and `relates:` links that resolve) AND the documentation wiki (no orphan pages, no broken relative links, indexes in sync), and documentation house-style (no em-dash characters). Use when the user says "check the artifact graph", "validate the artifact links", "lint the docs", "are the doc links broken", "check the wiki", "check for em-dashes", before opening a PR that touches docs or graph artifacts, or as the governance-check-graph step. It runs the same scripts the CI gates run, so local results match the pipeline. Do NOT use to create or fix artifacts, tickets, links, or docs (that is elaboration-upsert-user-story / governance-enrich-ticket / governance-author-adr / create-upsert-documentation).
tsunami28/MindNova
Stars: 0Claude CodeCodexCreate, amend, or check a project's governing "constitution" - the small set of non-negotiable engineering principles that every agent run (Claude Code and GitHub Copilot) should honour. Use when the user says "create/set up a constitution", "add a rule/principle to the constitution", "amend/update the constitution", "make this a non-negotiable", "what are our project principles", or asks to bootstrap the AGENTS.md contract; and in check mode when the user says "check my changes against the constitution", "does this violate a clause", "constitution check", or "review this for constitution compliance". Do NOT use for authoring a single architectural decision (that is governance-author-adr), for validating doc or graph link integrity (that is governance-check-graph), for ordinary docs, or for editing tracker tickets.
tsunami28/MindNova
Stars: 0Claude CodeCodexValidate the AI-SDLC skills under .claude/skills/ with the layered eval harness before relying on a new or changed one. Use when a skill has just been added or edited and needs checking, or when the user says "eval the skills", "validate this skill", "run the skill harness", "test the skills", "did my skill change break routing", or "check skill discriminability". This is the durable form of the "draft-only eval harness" the roadmap refers to. Do NOT use to validate the artifact graph or docs wiki (that is governance-check-graph), or to author or edit a skill's content.
tsunami28/MindNova
Stars: 0Claude CodeCodexGather post-release signals and record them as concise feedback notes anchored on the originating epic/story. Use after a release ships and you need to learn whether it delivered its intended outcome: phrasings like "did the release land", "collect feedback on what we shipped", "what is the telemetry showing for this feature", "summarise the support tickets since release", "what did stakeholders say", or when a feature is in production and should feed the next loop. This is the entry point to the mature phase. Do NOT use to triage a specific issue the feedback surfaced (that is mature-analyze-ticket), to turn validated needs into new stories (that is elaboration-upsert-user-story), to run fresh research (that is discovery-synthesize-research), or to add links to an already-recorded ticket (governance-enrich-ticket).
tsunami28/MindNova
Stars: 0Claude CodeCodexNavigate the AI-SDLC workflow for a given work item or artifact: report where it is in the lifecycle and what to do next. Use when the user asks "where are we on MN-42", "what is the next step for this story", "run the sdlc on <key or path>", "what is missing before this can ship", "which phase is this in", or hands over an artifact (a work item key, a spec, a doc, an ADR) and asks how to proceed. It is READ-ONLY for navigation: it resolves the anchor, traverses the artifact graph, and reports the current phase plus the next /<phase>-<step> and the persona who owns it. It does NOT create, edit, link, or transition anything, and it never writes directly; on explicit request it can dispatch the next step by handing off to the owning phase-step skill (which writes behind its own confirmation gates), per docs/ai-sdlc/orchestration.md. Do NOT use to author artifacts or to write work items.
tsunami28/MindNova
Stars: 0Claude CodeCodexstribus/pygerengastos
Stars: 1Claude CodeCodexSecurely interact with Bitwarden password manager via the bw CLI. Covers authentication (login/unlock/logout), vault operations (list/get/create/edit/delete items, folders, attachments), password/passphrase generation, organization management, and secure session handling. Use for "bitwarden", "bw", "password safe", "vaultwarden", "vault", "password manager", "generate password", "get password", "unlock vault". Requires bw CLI installed and internet access.
kbarbel640-del/skills
Stars: 1Claude CodeCodexGeneral-purpose Coda document manager via REST API v1. Supports listing/creating/updating/deleting docs, managing tables/rows/pages, triggering automations, and exploring doc structure. Requires CODA_API_TOKEN environment variable. Delete operations require explicit confirmation; publishing and permission changes require explicit user intent.
kbarbel640-del/skills
Stars: 1Claude CodeCodexComplete Kimai time-tracking API integration. Manage timesheets, customers, projects, activities, teams, invoices and exports via REST API. Supports time tracking workflows, reporting, and administrative operations. Keywords - kimai, zeiterfassung, timesheet, tracking, project, customer, activity, invoice, export, timer, stunden
kbarbel640-del/skills
Stars: 1Claude CodeCodexTrack live NFL, NBA, NHL, or MLB games and automatically change Hue light colors based on which team is leading. Use when user wants to sync smart lights with live sports scores for visual game tracking. Supports NFL, NBA, NHL, and MLB games with customizable team colors.
kbarbel640-del/skills
Stars: 1Claude CodeCodex