Showing 59221–59250 of 77205 skills
TsukiNi22/ai-utils
TsukiNi22/ai-utils
TsukiNi22/ai-utils
TsukiNi22/ai-utils
TsukiNi22/ai-utils
Clean editorial-style interfaces. Warm monochrome palette, typographic contrast, flat bento grids, muted pastels. No gradients, no heavy shadows.
BumpyClock/agent-templates
Execute approved tsq plans via subagents, aggregation reviews, integration.
BumpyClock/agent-templates
A relentless interview to sharpen a plan or design, which also creates docs (ADR's and glossary) as we go.
carmonalab/ECODA_paper
Create or update a DESIGN.md from an existing product repository or public website. Use when asked to document an interface's design language, reconstruct its visual system, extract design tokens and guidance from current evidence, or give coding agents persistent UI context. Do not modify product source or promote accidental implementation patterns into design decisions.
gagandeepgill/puzzle-game
How this repo builds Wordle-style daily puzzles: UTC date keys, deterministic seeding, rotating rule variants, first-attempt-counts records, streaks that survive being offline, and spoiler-free share payloads. Use when adding or changing a daily mode, a seed, a streak, a share string, or when a puzzle must be identical for every player on a given day.
gagandeepgill/puzzle-game
Use this skill to generate or audit design systems, check visual consistency, and review PRs that touch styling.
gagandeepgill/puzzle-game
Playwright E2E testing patterns, Page Object Model, configuration, CI/CD integration, artifact management, and flaky test strategies.
gagandeepgill/puzzle-game
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
Audit 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
Accessibility 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
Frontend development patterns for React, Next.js, state management, performance optimization, and UI best practices.
gagandeepgill/puzzle-game
Sound 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
Juice 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
Map 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
How 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
React 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
React 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
React 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
TypeScript 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
Run 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
Run 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
Map 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
Turn 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
Capture 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
Write 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