claude

stack

Opinionated development stack: one /work entry point from request to shipped change, tracked in Linear from single issues to multi-session projects, with interview, debug, prototype, research, and code review.

4 on GitHubMITupdated 4 days ago
/

Plugin stack from marketplace firzus-agent-skills in Firzus/agent-skills. Commands read from the repo's manifest — 3 days ago.

What it installs

Skills (46)

  • authoring

    Use when creating, revising, or reviewing a skill's SKILL.md, supporting references, or templates, or when adjusting its invocation conditions and description.

  • gamification

    Gamification design for products, apps, and game meta-layers: design an engagement, habit, or retention system; choose or audit mechanics (points, badges, leaderboards, streaks, progress bars, variable rewards); diagnose mechanics that backfire (novelty decay, demotivated users, streak churn); or ru

  • imagegen

    Generates or edits raster images with AI (photos, illustrations, textures, sprites, mockups, logos, infographics), including transparent-background cutouts. Use when the task needs an AI-created or AI-edited bitmap; not for SVG/vector or code-native visuals.

  • improve-architecture

    Find places where the code is costly to change and propose evidenced refactors that hide complexity behind smaller interfaces. Use when the user asks for an architecture review, refactoring candidates, or where to reduce friction in a codebase.

  • instructions

    Use when creating, revising, or reviewing project AGENTS.md files, scoped rules, or other agent-facing documentation outside skills. Use setup-harness for personal harness instructions and authoring for skill files.

  • monorepo

    Set up, evolve, and troubleshoot multi-project repositories. Use for workspace structure, cross-package dependencies, task graphs, build caching, affected CI, package contracts, releases, or an explicitly requested monorepo migration. Not for ordinary feature work confined to one project.

  • reverse-engineer

    Reverse engineer shipped software quickly with compact, cited evidence. Covers Electron/asar apps, native PE/ELF/Mach-O binaries and Node addons, Go/Rust/.NET binaries, APKs and minified JS bundles. Use to explain how a feature works, trace IPC channels and native calls, extract versions and depende

  • runbook

    Write an interactive bash runbook that guides a person through actions only they can take, such as copying credentials from a third-party dashboard, configuring CI secrets, or approving a migration or cutover. Use when a task is blocked on manual steps in someone's browser or accounts; not for steps

  • security-review

    Perform source-only security audits of codebases, APIs, services, and applications. Use for security questions, focused vulnerability reviews, or explicitly requested full audits.

  • setup-harness

    Set up personal instructions for Codex (app and CLI), Cursor, or Claude Code, with reviewed content, native instruction loading, and no backups or system-prompt replacement.

  • skills

    Install, update, remove and author Agent Skills with the `skills` CLI (skills.sh, vercel-labs/skills). Use when adding a skill from a repo, sharing skills across agents, choosing project vs global scope, publishing a skill repo, or debugging a skill the agent never fires.

  • unslop

    Audit a codebase for dead code and AI slop, clear each suspect against the legitimate reason it exists, and remove only what the evidence carries.

  • video-report

    Record video evidence with FFmpeg after a visual bug fix or when asked for a recorded demo of a web page, native application, or game.

  • youtube-transcript

    Transcribes YouTube videos and produces evidence-backed learning reports. Use when asked to extract YouTube captions, transcribe a video's audio, or explain what a video teaches using speech and on-screen demonstrations.

  • figma-to-unity

    Implements Figma designs (frames, components, HUD elements, menus) as Unity UI Toolkit interfaces — UXML hierarchy, USS styles mapped to design tokens, exported sprite assets, and a minimal C# controller — using the Figma MCP server (get_design_context, get_metadata, get_screenshot, get_variable_def

  • unity-cli

    Use when an agent drives the Unity Editor or a development Player from a terminal: building, running tests, running C# in the live Editor, capturing screenshots, generating scenes or assets headless, exposing project commands, or iterating on a change the user tests in an open Editor. Also when the

  • unity-core

    Use for any Unity task: writing, reviewing, or architecting Unity code, choosing between two Unity tools that do the same job, or when the user mentions Unity, CoreCLR, IL2CPP, Awaitable, Addressables, Content Directories, DOTS, ECS, Jobs, Burst, assembly definitions, Input System, audio, project st

  • unity-editor-tools

    Use when building a custom Unity Editor window, inspector, or authoring tool for project data (ability definitions, dialogue graphs, combo trees), a polymorphic list with [SerializeReference], a node graph, or Editor icons, or when the user mentions custom inspectors, IMGUI, or Odin.

  • unity-multiplayer

    Use when adding or reviewing networking in a Unity game: choosing Netcode for GameObjects or Netcode for Entities, the authority model, sessions, matchmaking, relay, dedicated server builds, or testing several peers with Multiplayer Play Mode.

  • unity-rendering

    Use when choosing or configuring a Unity render pipeline (URP, HDRP, Built-In), writing custom render passes with Render Graph, setting up lighting, light baking, Adaptive Probe Volumes, Surface Cache GI, the GPU Resident Drawer, occlusion culling, or shaders, or investigating GPU rendering performa

  • unity-ui

    Use when building or reviewing Unity runtime UI with UI Toolkit: menus, HUD, world-space or diegetic UI, UXML, USS or translating CSS to USS, design tokens, data binding, MVP, text, localization, or UI performance, or when weighing UGUI against UI Toolkit. For a Figma design use figma-to-unity; for

  • code-review

    Review a change with independent read-only reviewers on requirements, project standards, and correctness. Use for a branch, a pull request, uncommitted work, or the review step of /work.

  • debug

    Find the cause of a bug, failing test, crash, unexpected behavior, or performance regression from reproducible evidence, and fix it when asked. Use when asked to debug or diagnose, or when /work routes a bug here.

  • interview

    Settle open decisions with the user through short rounds of questions until both share the same understanding of what will be built. Use when a request leaves product choices open, when the user asks to be interviewed or challenged on a plan, or when another skill hands over decisions to settle.

  • prototype

    Answer a design or feasibility question with the smallest observable experiment, such as comparing interface variants, exercising domain rules, or measuring a technical limit. Use when a decision needs observed behavior rather than more discussion or source research; not for building the settled fea

  • research

    Investigate a question across many sources with delegated researchers, independent verification of the key claims, and a reusable evidence dossier. Use for explicit deep research, substantial comparisons, or updating an existing dossier; a single factual lookup needs a direct answer instead.

  • work

    Entry point of the stack. Use when the user runs /work with any development request (a feature, a fix, a change, a vague idea, a Linear issue, or a Linear project to start or continue) to take it from intent to a verified result ready to ship.

  • adsense

    AdSense publisher monetization — improve ad revenue on a website without risking the account. Use when the user wants to raise AdSense revenue or RPM, place ad units or choose between Auto ads and manual units, diagnose an earnings, coverage, or ads-not-showing problem, integrate or fix ad code in a

  • astryx

    Astryx (@astryxdesign) — Meta's open-source, agent-ready React + StyleX design system. Covers setup (npm packages, npx astryx init, StyleX compiler), the agent discovery loop (astryx template/component/docs, MCP server, --dense), per-component subpath imports, the xstyle styling order, design tokens

  • cloudflare-cli

    Operate Cloudflare from the shell with `cf`, Cloudflare's agent-oriented CLI (npm package `cf`, open beta) covering the whole Cloudflare API and Workers projects. Use to sign in and select an account or zone, find the command for a Cloudflare task, inspect or change resources such as DNS records, zo

  • dokploy-best-practices

    Dokploy deployment and operations best practices. Use when the user deploys apps, databases, or Docker Compose stacks with Dokploy; configures domains, Traefik, Swarm health checks, CI/CD, backups, or webhooks; or troubleshoots Bad Gateway, 404, volume, database, or hardening issues.

  • extract-theme

    Extracts the visual theme (colors, typography, radius, spacing, shadows) of a public website provided by the user and produces a shadcn/ui + Tailwind CSS v4 compatible token block, ready to paste into the project's `globals.css` (or `app.css`) inside `@theme` and `.dark`. Uses the `agent-browser` CL

  • lettering

    Use when a web wordmark (a name or logo in a hero, header, or loading screen) needs designed hand-drawn lettering instead of a font, delivered as one SVG path that can be animated, or when free fonts look generic and procedural lettering (distance-field fused strokes, SVG goo filters on text) looks

  • nextjs

    Next.js 16+ App Router with React Server Components and TypeScript. Use when working in app/, layouts, pages, route handlers, proxy.ts, Server Actions, "use client"/"use server"/"use cache" boundaries, caching and revalidation, typed routes, view transitions, Cache Components adoption, instant navig

  • payload-cms

    Payload CMS 3.x, the Next.js-native TypeScript headless CMS. Use when working in payload.config.ts, collections, fields, access control, hooks, the Local API, versions and drafts, database or storage adapters, plugin authoring, or the official MCP plugin.

  • shaders

    Guides building GPU-accelerated visual effects in React / Next.js with the `shaders` npm package from shaders.com — declarative `<Shader>` component trees, composition (stacking, nesting, blend modes, masking), reactive props, dynamic prop drivers (`auto-animate`, `mouse-position`, `map`), shape (SD

  • swr

    SWR v2 (stale-while-revalidate) data fetching for React and Next.js. Use when implementing or reviewing code that uses the `swr` package — useSWR hooks, cache keys, revalidation, mutations, pagination, or SWRConfig.

  • tanstack-query

    TanStack Query v5 (React Query) async state management for React. Use when implementing or reviewing code that uses `@tanstack/react-query` — query keys, queryOptions, useQuery/useSuspenseQuery, mutations and invalidation, QueryClient defaults, SSR hydration, or infinite queries.

  • tanstack-router

    TanStack Router v1 for React — file-based routing, type-safe navigation, validated search params, loaders and router context. Use when working in a project that uses `@tanstack/react-router` — routeTree.gen.ts, createFileRoute, Link/useNavigate, validateSearch, loaderDeps, route masking, or code spl

  • tanstack-start

    TanStack Start, the full-stack React framework built on TanStack Router with Vite or Rsbuild. Use when setting up or reviewing a `@tanstack/react-start` project — the build-tool plugin, SSR and selective SSR, server functions (`createServerFn`), server routes, middleware, prerendering, SPA mode, env

  • tanstack-store

    TanStack Store client-state management. Use when implementing or reviewing @tanstack/store or its framework adapters, immutable updates, derived stores, selectors, subscriptions, batching, scoped SSR state, or migrations from legacy Store/Derived/Effect APIs.

  • tauri

    Tauri 2 development and validation. Use for src-tauri, Rust/frontend IPC, capabilities and plugins, windows, mobile entry points, packaging, or inspecting a running Tauri app with tauri-agent-kit.

  • vite-plus

    Vite+ projects using vite-plus and the vp CLI. Use when setting up, migrating to, or updating Vite+, configuring its checks, tests or library builds, debugging built-in versus script execution, or configuring workspace tasks and caching. Applies to Vite+ integrations, not every standalone Vite proje

  • web-assets-optimization

    Audits and optimizes all web-app assets for performance: images (Sharp AVIF/WebP variants, responsive `img`/`picture`/`srcset`/`sizes`), video (ffmpeg H.264/VP9/AV1 encoding, posters, lazy loading), animated GIF replacement with video or animated WebP/AVIF, web fonts (WOFF2 subsetting, font-display,

  • web-extension

    Design, build, port, debug, test, or prepare browser extensions for Chromium, Firefox, and Safari using the WebExtensions model. Use when work involves manifest.json, Manifest V3, extension service workers or background scripts, content scripts, extension messaging, browser permissions, toolbar acti

  • zod

    Zod schema validation. Use when writing or reviewing Zod schemas, parsing untrusted data, handling coercion, refinements, transforms or validation errors, integrating forms or APIs, exporting JSON Schema, or migrating Zod versions.

View source on GitHub skills.sh

More from Firzus/agent-skills

All 4 plugins →

Cross-cutting engineering skills — code health.

46 skills

4

game

claude

Unity development skills — engine defaults, UI, Editor tools, rendering, multiplayer, Editor automation, and Figma UI.

46 skills

4

web

claude

Développement web et applicatif : frameworks, ressources et déploiement.

46 skills

4

Maintain stack?

This page updates itself from your repo. Add the badge to your README, or get it Featured to pin it above the organic results with a followed link to your site.

claude & codex plugins4 plugins