Skip to content

Recently active skills

Trending is calculated from star growth this site has recorded itself. No history is estimated or back-filled.

Not enough history yet: 3 of 7 days recorded. Until then this list is ordered by the most recent content change.

77104 skills

design-systemgagandeepgill/puzzle-gameUse this skill to generate or audit design systems, check visual consistency, and review PRs that touch styling.Stars: 0Updated Claude CodeCodexVerifiedInstall
e2e-testinggagandeepgill/puzzle-gamePlaywright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.Stars: 0Updated Claude CodeCodexVerifiedInstall
fixing-accessibilitygagandeepgill/puzzle-gameAudit 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
fixing-metadatagagandeepgill/puzzle-gameAudit and fix HTML metadata including page titles, meta descriptions, canonical URLs, Open Graph tags, Twitter cards, favicons, JSON-LD structured data, and robots directives. Use when adding SEO metadata, fixing social share previews, reviewing Open Graph tags, setting up canonical URLs, or shipping new pages that need correct meta tags.Stars: 0Updated Claude CodeCodexVerifiedInstall
fixing-motion-performancegagandeepgill/puzzle-gameAudit 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
frontend-a11ygagandeepgill/puzzle-gameAccessibility 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
frontend-patternsgagandeepgill/puzzle-gameFrontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.Stars: 0Updated Claude CodeCodexVerifiedInstall
game-audiogagandeepgill/puzzle-gameSound 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
game-feelgagandeepgill/puzzle-gameJuice 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
game-typographygagandeepgill/puzzle-gameThe arcade's type system: the Fraunces and Outfit pairing, the roles each face plays, the numeric styling that game UI lives on, and the sizing floor set by measured contrast headroom. Use when adding or restyling any text, number, label or button in Payload, Ledger Lane or the hub, when choosing a size or weight, or when text feels cramped, illegible or off-brand.Stars: 0Updated Claude CodeCodexVerifiedInstall
improve-uigagandeepgill/puzzle-gameAudit an existing product surface against its own design evidence, identify verified UI problems, and write self-contained implementation plans for another agent. Strictly read-only on product source. Use when asked to review, refine, improve, or clean up an interface without replacing its identity; investigate design-system drift; or prepare a design handoff.Stars: 0Updated Claude CodeCodexVerifiedInstall
payload-enginegagandeepgill/puzzle-gameMap 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
puzzle-designgagandeepgill/puzzle-gameDesign principles for this repo's genre: daily puzzles, engine-builder runs, and the rules that make compounding scores feel earned rather than arbitrary. Use when adding a part, tuning a quota curve, designing a boss twist, changing what a draft offers, or judging whether a proposed mechanic is fun.Stars: 0Updated Claude CodeCodexVerifiedInstall
pwa-shellgagandeepgill/puzzle-gameHow 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
react-patternsgagandeepgill/puzzle-gameReact 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
react-performancegagandeepgill/puzzle-gameReact 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
react-testinggagandeepgill/puzzle-gameReact 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
tdd-workflowgagandeepgill/puzzle-gameUse this skill when writing new features, fixing bugs, or refactoring code. Enforces test-driven development with 80%+ coverage including unit, integration, and E2E tests.Stars: 0Updated Claude CodeCodexFlaggedInstall
typescript-game-stategagandeepgill/puzzle-gameTypeScript 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
verify-puzzle-gamegagandeepgill/puzzle-gameRun 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
create-code-generationtsunami28/MindNovaOrchestrate a feature or fix from story to PR through the team's AI-SDLC workflow, with human checkpoints: story -> plan -> branch -> TDD (>=80% coverage, story-tagged tests) -> update both doc layers -> record decisions as ADRs -> enrich the work item -> review -> PR. Use when the user says "take this story through the process", "run the dev cycle", "do the full workflow on MN-42", or "build this end to end properly". It delegates to focused skills rather than doing each step itself. Do NOT use for a quick one-off edit, a question, or a standalone git or branch request (creating or naming a branch on its own) - use the individual skills directly for those.Stars: 0Updated Claude CodeCodexVerifiedInstall
create-refactoringtsunami28/MindNovaImprove the internal structure of existing code without changing its observable behaviour. Use when the user says "refactor this", "clean this up", "simplify this", "extract a method/class", "rename for clarity", "reduce this duplication", or "tidy this without changing behaviour". The defining constraint is behaviour preservation: the tests pass before and after, and the public contract is unchanged. Do NOT use to add or change behaviour, fix a bug, or build a feature (that is create-code-generation), and do NOT use to delete dead code as the primary goal.Stars: 0Updated Claude CodeCodexVerifiedInstall
create-run-gatestsunami28/MindNovaRun 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.Stars: 0Updated Claude CodeCodexVerifiedInstall
create-sprint-planningtsunami28/MindNovaAssemble refined, sized stories into an iteration and order them by dependency and value so the build phase starts with a clear, unblocked queue. Use when the user says "plan the sprint", "what should we pick up next", "fill the iteration", "sequence these stories", "order the backlog for the next sprint", or "assign these to the sprint". This is a light coordination step, not a document-producing one. Do NOT use to create or refine a story (that is elaboration-upsert-user-story), to write acceptance criteria (that is elaboration-upsert-user-story-acceptance-criteria), to take a single story through build (that is create-code-generation), or to report the next step on a single work item (that is run-sdlc).Stars: 0Updated Claude CodeCodexVerifiedInstall
create-upsert-documentationtsunami28/MindNovaMaintain BOTH documentation layers as one linked wiki after a change: technical docs in docs/ and functional docs in docs-functional/. Use after implementing or changing a feature, when the user says "update the docs", "sync the documentation", "the docs are out of date", "document how this works", or as the documentation step of a development cycle. Also use when a good answer to a real question deserves to become a page. Reads the layer index first, routes each change to the right layer, cross-links related pages, and flags stale sections. Do NOT use for ADRs (governance-author-adr), the constitution (governance-constitution), or API spec / OpenAPI generation.Stars: 0Updated Claude CodeCodexVerifiedInstall
create-verify-test-coveragetsunami28/MindNovaVerify a change is adequately tested before it ships: run the tests, measure line coverage on the changed projects, and confirm every acceptance criterion has a covering test. Use when the user says "is this tested enough", "check the coverage for MN-42", "are all the ACs covered", "verify the tests before the PR", "run the QE checks", or "is this story gate-ready". Do NOT use to WRITE the implementation or the tests (that is create-code-generation), to derive or number the criteria (that is elaboration-upsert-user-story-acceptance-criteria), or to review code style (that is the review step).Stars: 0Updated Claude CodeCodexVerifiedInstall
discovery-map-journeytsunami28/MindNovaMap 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).Stars: 0Updated Claude CodeCodexVerifiedInstall
discovery-synthesize-researchtsunami28/MindNovaTurn 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).Stars: 0Updated Claude CodeCodexVerifiedInstall
discovery-upsert-hypothesis-canvastsunami28/MindNovaCapture 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).Stars: 0Updated Claude CodeCodexVerifiedInstall
elaboration-upsert-api-contracttsunami28/MindNovaProduce a machine-readable API specification (OpenAPI 3.x in YAML) for the slice being built, so the build and tests consume a contract instead of prose. Use when designing or changing a REST endpoint, when the user says "design the API for this", "write the OpenAPI spec", "define the contract for MN-42", "what should the request/response shape be", or before code generation begins on a slice that exposes or changes an HTTP surface. This is the L3 keystone: the contract lives in the repo. Do NOT use to author an ADR (that is governance-author-adr), to write feature docs, to generate the implementation (that is create-code-generation), or for non-HTTP work.Stars: 0Updated Claude CodeCodexVerifiedInstall