Sponsored by

Find leads on Reddit on auto pilot

Agent skills
ai-agents

Topic: ai-agents

18,135 skills in this topic.

orchestrate This skill should be used when the user asks to 'orchestrate a task', 'break down work into parallel agents', 'coordinate subtasks', 'run agents in parallel', or mentions 'multi-agent'. Decomposes complex tasks into tracked subtasks, dispatches parallel subagents, and coordinates until completion.
varun29ankuS/shodh-memory 191
shodh-memory Persistent memory system for AI agents. Use this skill to remember context across conversations, recall relevant information, and build long-term knowledge. Activate when you need to store decisions, learnings, errors, or context that should persist beyond the current session.
varun29ankuS/shodh-memory 191
autogrind Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.
ttttonyhe/autogrind 6
autogrind Engage in 24x7 auto-work mode. Continuously grind through improvements, fixes, tests, and polish without stopping until you say so. For long-running sessions across code, ML/data, research, design, or writing. Not for single bounded tasks. Trigger phrases: /autogrind, /自己动, 'autogrind this', 'grind on this', 'keep working don't stop', 'work until I say stop', 'keep improving', 'keep going'.
ttttonyhe/autogrind 6
frontend-design Create distinctive, production-grade frontend interfaces with high design quality. Use this skill when the user asks to build web components, pages, artifacts, posters, or applications (examples include websites, landing pages, dashboards, React components, HTML/CSS layouts, or when styling/beautifying any web UI). Generates creative, polished code and UI design that avoids generic AI aesthetics.
onecli/onecli 1,737
vercel-react-best-practices React and Next.js performance optimization guidelines from Vercel Engineering. This skill should be used when writing, reviewing, or refactoring React/Next.js code to ensure optimal performance patterns. Triggers on tasks involving React components, Next.js pages, data fetching, bundle optimization, or performance improvements.
onecli/onecli 1,737
web-design-guidelines Review UI code for Web Interface Guidelines compliance. Use when asked to "review my UI", "check accessibility", "audit design", "review UX", or "check my site against best practices".
onecli/onecli 1,737
find-skills Helps users discover and install agent skills when they ask questions like "how do I do X", "find a skill for X", "is there a skill that can...", or express interest in extending capabilities. This skill should be used when the user is looking for functionality that might exist as an installable skill.
onecli/onecli 1,737
brainstorm Guided game concept ideation — from zero idea to a structured game concept document. Uses professional studio ideation techniques, player psychology frameworks, and structured creative exploration.
Donchitos/Claude-Code-Game-Studios 8,725
art-bible Guided, section-by-section Art Bible authoring. Creates the visual identity specification that gates all asset production. Run after /brainstorm is approved and before /map-systems or any GDD authoring begins.
Donchitos/Claude-Code-Game-Studios 8,725
asset-spec Generate per-asset visual specifications and AI generation prompts from GDDs, level docs, or character profiles. Produces structured spec files and updates the master asset manifest. Run after art bible and GDD/level design are approved, before production begins.
Donchitos/Claude-Code-Game-Studios 8,725
consistency-check Scan all GDDs against the entity registry to detect cross-document inconsistencies: same entity with different stats, same item with different values, same formula with different variables. Grep-first approach — reads registry then targets only conflicting GDD sections rather than full document reads.
Donchitos/Claude-Code-Game-Studios 8,725
bug-report Creates a structured bug report from a description, or analyzes code to identify potential bugs. Ensures every bug report has full reproduction steps, severity assessment, and context.
Donchitos/Claude-Code-Game-Studios 8,725
changelog Auto-generates a changelog from git commits, sprint data, and design documents. Produces both internal and player-facing versions.
Donchitos/Claude-Code-Game-Studios 8,725
architecture-review Validates completeness and consistency of the project architecture against all GDDs. Builds a traceability matrix mapping every GDD technical requirement to ADRs, identifies coverage gaps, detects cross-ADR conflicts, verifies engine compatibility consistency across all decisions, and produces a PASS/CONCERNS/FAIL verdict. The architecture equivalent of /design-review.
Donchitos/Claude-Code-Game-Studios 8,725
create-architecture Guided, section-by-section authoring of the master architecture document for the game. Reads all GDDs, the systems index, existing ADRs, and the engine reference library to produce a complete architecture blueprint before any code is written. Engine-version-aware: flags knowledge gaps and validates decisions against the pinned engine version.
Donchitos/Claude-Code-Game-Studios 8,725
create-stories Break a single epic into implementable story files. Reads the epic, its GDD, governing ADRs, and control manifest. Each story embeds its GDD requirement TR-ID, ADR guidance, acceptance criteria, story type, and test evidence path. Run after /create-epics for each epic.
Donchitos/Claude-Code-Game-Studios 8,725
balance-check Analyzes game balance data files, formulas, and configuration to identify outliers, broken progressions, degenerate strategies, and economy imbalances. Use after modifying any balance-related data or design. Use when user says 'balance report', 'check game balance', 'run a balance check'.
Donchitos/Claude-Code-Game-Studios 8,725
create-control-manifest After architecture is complete, produces a flat actionable rules sheet for programmers — what you must do, what you must never do, per system and per layer. Extracted from all Accepted ADRs, technical preferences, and engine reference docs. More immediately actionable than ADRs (which explain why).
Donchitos/Claude-Code-Game-Studios 8,725
create-epics Translate approved GDDs + architecture into epics — one epic per architectural module. Defines scope, governing ADRs, engine risk, and untraced requirements. Does NOT break into stories — run /create-stories [epic-slug] after each epic is created.
Donchitos/Claude-Code-Game-Studios 8,725
asset-audit Audits game assets for compliance with naming conventions, file size budgets, format standards, and pipeline requirements. Identifies orphaned assets, missing references, and standard violations.
Donchitos/Claude-Code-Game-Studios 8,725
code-review Performs an architectural and quality code review on a specified file or set of files. Checks for coding standard compliance, architectural pattern adherence, SOLID principles, testability, and performance concerns.
Donchitos/Claude-Code-Game-Studios 8,725
adopt Brownfield onboarding — audits existing project artifacts for template format compliance (not just existence), classifies gaps by impact, and produces a numbered migration plan. Run this when joining an in-progress project or upgrading from an older template version. Distinct from /project-stage-detect (which checks what exists) — this checks whether what exists will actually work with the template's skills.
Donchitos/Claude-Code-Game-Studios 8,725
bug-triage Read all open bugs in production/qa/bugs/, re-evaluate priority vs. severity, assign to sprints, surface systemic trends, and produce a triage report. Run at sprint start or when the bug count grows enough to need re-prioritization.
Donchitos/Claude-Code-Game-Studios 8,725