frontend-development

341

du2333

Frontend development patterns for the Flare Stack Blog. Use when implementing data fetching with TanStack Query, creating route loaders, building infinite scroll, adding skeleton/pending states, or organizing UI components.

Loading State Tester

71

PramodDutta

Verify loading indicators, skeleton screens, and progress bars appear correctly during async operations and disappear on completion or error.

kubit-expanding-skeleton

32

aniftyco

Use when adding new files, patterns, or examples to skeleton/. Use when creating new controller, model, job, mailable, migration, view, or component in the skeleton app.

kubit-validating-design

32

aniftyco

Use after any change to skeleton/, packages/core/, or docs/. Use to verify types compile and documentation is synchronized.

user-story-mapping

31

melodic-software

Jeff Patton's User Story Mapping technique for Agile discovery. Visualizes user journey as a map, identifies backbone activities, walking skeleton, and release slices. Use when organizing requirements into deliverable increments or defining MVP scope.

rigging-animation

29

omer-metin

World-class character rigging and animation systems expertise — skeleton hierarchies, deformation, FK/IK, facial rigs, weight painting, and game engine integration from someone who has shipped AAA characters. Use when "rig a character, character rigging, skeleton hierarchy, weight painting, skin weights, joint orientation, fk ik, inverse kinematics, forward kinematics, facial rig, blend shapes, morph targets, twist bones, deformation, animation retargeting, root motion, bone limits, control rig, humanoid avatar, generic rig, candy wrapper effect, volume preservation, rigging, animation, character, skeleton, deformation, maya, blender, unity, unreal, fbx, skinning, weight-painting, ik, fk, facial, mocap" mentioned.

Skeleton UI Standards

25

Aarshps Varisankya Android Skeleton Loading Standards

Guidelines for styling and transitioning from shimmer-ready skeleton placeholders

find-CGameSceneNode_GetSkeletonInstance

22

hzqst

Find and identify the CGameSceneNode_GetSkeletonInstance virtual function in CS2 binary using IDA Pro MCP. Use this skill when reverse engineering CS2 server.dll or libserver.so to locate the GetSkeletonInstance function in CGameSceneNode vtable. Trigger: CGameSceneNode_GetSkeletonInstance, GetSkeletonInstance, skeleton instance

command-creator

18

malhashemi

Authoritative templates and scaffolding for creating slash commands. This skill should be used when creating new commands, reviewing existing commands for template compliance, or understanding command structure. Contains YAML templates with section instructions and scaffolding scripts for generating command skeleton files.

agent-creator

18

malhashemi

Authoritative templates and scaffolding for creating agent system prompts (primary agents and subagents). This skill should be used when creating new agents, reviewing existing agent prompts for template compliance, verifying agent structure, or extracting knowledge into agent prompts. Contains YAML templates with section-by-section instructions and scaffolding scripts for generating skeleton files.

loading-states

16

sanky369

Design effective loading states, skeleton screens, and empty states that maintain user confidence. Use when content takes time to load, when showing progress, or handling empty data scenarios. Triggers on "loading state", "skeleton screen", "empty state", "spinner", "progress bar", "loading animation", "zero state".

python-project-skel

14

zircote

Generate production-ready Python project skeletons with the Astral UV package manager, Hatchling build backend with dynamic versioning, and modern tooling (ruff, mypy, pytest, bandit). Use when creating new Python projects, initializing Python packages, setting up src-layout projects, scaffolding Python libraries, or starting a new Python application. Supports Python 3.14+ by default with configurable version. Output to current directory, specified path, or tarball.

state-ux-flow-builder

12

patricio0312rev

Standardizes UX states for data fetching flows (loading, error, empty, success) and complex multi-view UI patterns. Provides state machine approach recommendations, loading skeletons, error boundaries, and empty state components. Use when implementing "loading states", "error handling", "empty states", or "state machines".

loading-states

12

dylantarre

Use when indicating progress or waiting - spinners, progress bars, skeleton screens, shimmer effects, or any animation showing the system is working.

component-scaffold-generator

12

patricio0312rev

Generates clean React/Vue component skeletons with TypeScript types, prop variants, styling hooks, test files, Storybook stories, and usage documentation. Use when users request "create a component", "scaffold component", "new React component", or "generate component boilerplate".

loaders-spinners

12

dylantarre

Use when creating loading indicators, spinners, progress bars, or skeleton screens to communicate system status

Template Method Design Pattern

10

krzysztofsurdy

Define the skeleton of an algorithm in a base class but let subclasses override specific steps without changing the algorithm's structure. A behavioral pattern enabling code reuse and variation in a controlled manner.

skeleton-generate

9

matsuni-kk

Generates the skeleton for a Skills-version agent (CLAUDE.md, .github/skills/, .codex/, etc.) and completes initial configuration. Use this when asked to “generate skeleton”, “create agent”, or “build skeleton”.

tailwind-animate

9

TerminalSkills

Add animations to Tailwind CSS projects. Use when implementing CSS animations with Tailwind, adding entrance effects, building animated components, or creating loading spinners and skeleton screens.

crawl4ai

9

tao3k

Use when crawling web pages, extracting markdown content, or scraping website data with intelligent chunking and skeleton planning. Use when the user provides a URL or link to fetch or crawl.

refactor-structural-duplication

6

JordanGunn

Identify structurally duplicate logic (pipeline-spine duplication) across semantically distinct modules. Use when multiple implementations share the same orchestration skeleton (e.g., bounds→shape→chunking→reduction→wrap), and unification may require subtle abstraction. Produces a duplication map and a safe extraction/refactor plan.

add-loading-indicator

5

marcglasberg

Add loading state tracking to widgets using context.isWaiting() for spinners and skeletons

pko-client-reference

4

Perseus Pko Tools Pko Client Reference

Reference guide for PKO (Pirates King Online) game client source code. Use this skill when you need to understand: (1) Game 3D file format specifications (.lgo, .lmo, .lws, .lac files), (2) How the game engine uses character, mesh, animation, or map data, (3) Verify if current import/export code correctly handles game file structures, (4) Understand bone/skeleton hierarchies, texture mapping, or animation systems, (5) Debug or validate any aspect of the file conversion between PKO formats and glTF.

python-project-skel

3

zircote

Generate production-ready Python project skeletons with Astral UV package manager, Hatchling build backend with dynamic versioning, bump-my-version for semantic version management, and modern tooling (ruff, mypy, pytest, bandit). Use when creating new Python projects, initializing Python packages, setting up src-layout projects, scaffolding Python libraries, or starting a new Python application. Supports Python 3.14+ by default with configurable version. Output to current directory, specified path, or tarball.

annotate-source-files

2

pjt222

Add PUT workflow annotations to source files using the correct language-specific comment prefix. Covers annotation syntax, skeleton generation via put_generate(), multiline annotations, .internal variables, and validation. Supports 30+ languages with automatic comment prefix detection. Use after analyzing a codebase and having an annotation plan, when adding workflow documentation to new or existing source files, or when documenting data pipelines, ETL processes, or multi-step computations.

create-r-package

2

pjt222

Scaffold a new R package with complete structure including DESCRIPTION, NAMESPACE, testthat, roxygen2, renv, Git, GitHub Actions CI, and development configuration files (.Rprofile, .Renviron.example, CLAUDE.md). Follows usethis conventions and tidyverse style. Use when starting a new R package from scratch, converting loose R scripts into a structured package, or setting up a package skeleton for collaborative development.

create-r-package

2

pjt222

Scaffold a new R package with complete structure including DESCRIPTION, NAMESPACE, testthat, roxygen2, renv, Git, GitHub Actions CI, and development configuration files (.Rprofile, .Renviron.example, CLAUDE.md). Follows usethis conventions and tidyverse style. Use when starting a new R package from scratch, converting loose R scripts into a structured package, or setting up a package skeleton for collaborative development.

annotate-source-files

2

pjt222

Add PUT workflow annotations to source files using the correct language-specific comment prefix. Covers annotation syntax, skeleton generation via put_generate(), multiline annotations, .internal variables, and validation. Supports 30+ languages with automatic comment prefix detection. Use after analyzing a codebase and having an annotation plan, when adding workflow documentation to new or existing source files, or when documenting data pipelines, ETL processes, or multi-step computations.

ux-vocabulary

1

rawktron

A shared UX vocabulary for precise conversational descriptions of interfaces. Use this skill whenever the user describes a UI, UX flow, interaction, or layout using words from the UX glossary — such as morph, grow, yield, rail, selectable, overlay, skeleton, snappy, mark-and-undo, etc. Also trigger when the user is describing any interface behavior and you need to resolve ambiguity about what they mean. This skill defines ~40 words with exact meanings so the user can describe UX in plain English while remaining precise. When you see these words, do NOT interpret them loosely -- they have specific agreed-upon definitions.

agent-install-templates

1

phazurlabs

Production-ready templates for packaging AI agents as installable software. Use when the user mentions: template, scaffold, boilerplate, starter, skeleton, package.json, pyproject.toml, Dockerfile, docker-compose, MCP server template, Claude Code plugin template, LangGraph deploy, install script, release action, GitHub Actions, agent packaging template, generate template, gen-template, cookiecutter, project structure

sdd-spec-template

1

JiKl-coding

Produce a clear, review-ready SDD specification skeleton in Markdown.

blog-outline

1

megastep

SERP-informed outline generation with H2/H3 heading hierarchy, competitive content gap analysis, section-by-section word count targets, chart and image placement markers, FAQ question planning, and internal linking zones. Lighter than a full content brief — generates article skeleton and structure only, ready for $blog write to consume. Use when user says "outline", "blog outline", "content outline", "structure blog", "plan sections", "article skeleton", "heading structure", "SERP analysis", "competitive outline", "plan article".

kb-plan

1

glenzli

A planning-phase skill for exploring a codebase and generating a knowledge-base construction blueprint (KB_PLAN.md). This skill performs a high-level scan of the repository during planning, distinguishing "high signal-to-noise" business logic from "boilerplate noise" and producing an actionable KB_PLAN.md build blueprint. Features include: reading only README and core configuration files under constraint (e.g., package.json / go.mod / pom.xml / docker-compose.yml), inspecting the project root and main entry skeleton files without delving into implementation details; identifying modules to include (business cores, cross-module contracts, implicit state transitions, stable public APIs) and directories to exclude (tests, node_modules/vendor, scaffold scripts, etc.). It outputs a standards-compliant KB_PLAN.md at the project root or .agent/kb/ containing overall planning, filtering declarations, and a construction task checklist with checkboxes (each item lists the target KB path, involved source code, and core focus points). After generation it stops and prompts for human confirmation to allow subsequent use of kb-build to execute documentation consolidation, improving documentation output efficiency and consistency.

skills-generate-skill-template

RyoMurakami1983

Generate a single-workflow skill skeleton with bilingual support. Use when starting a new skill.

frontend-conventions

henriqueneves87

Enforces robust frontend conventions for React/Next.js - semantic tokens, proper feedback (toast/skeleton/empty), SVG icons, a11y minimum, incremental changes

skeleton-skill

ephemeraldew

This skill helps developers quickly create professional-grade project structures by pulling pre-built templates from a remote repository. Use this skill when users request to create project scaffolding, initialize projects, or generate project skeletons. Instead of generating files token-by-token, it executes a script to fetch complete templates instantly.

Smart Blog Outline

rainday

Generate SERP-driven article outlines. Analyze the structure of the top 5 search results, identify content gaps, and produce a complete skeleton with suggested word counts.

template-method-pattern

rivettidaniel

Defines algorithm skeleton with customizable steps using Template Method Pattern. Use for data importers, exporters, multi-step processors, or any process with fixed flow but variant steps.

feedback-states

Abdullah4AI

Feedback state patterns: loading indicators, error handling UI, success confirmations, disabled states, skeleton views. Use when adding loading spinners, error alerts, success feedback, or managing empty/error/loading view states. Triggers: ProgressView, loading, error, alert, empty state, skeleton, disabled, feedback.

acceptance-test-design

arielperez82

BDD outer-loop methodology for acceptance tests - walking skeleton strategy, driving-port-only testing, business language purity, and design mandates that connect to the TDD inner loop

pr-tldr

inkeep

PR TLDR context brief — serves dual purpose: 1. **Committed state (template):** Contains the document skeleton with {{FILL}} markers. The pr-review orchestrator loads this at startup, fills in the markers during Phase 1.5, and overwrites this file with the filled result. 2. **Runtime state (filled):** After the orchestrator writes, subagent reviewers load this file and get the filled context brief. If you're reading this and see {{FILL}} markers, the template has not been filled in — either the orchestrator hasn't run yet, or you're viewing the committed source.