add-language-rules
Workflow command scaffold for add-language-rules in ECC.
11,180 slash commands in 908 plugins.
Workflow command scaffold for add-language-rules in ECC.
Generate a concrete design system (tokens, style, type, UX) before building UI
Implement tasks incrementally โ build, test, verify, commit. Add "auto" to run the whole plan in one approved pass.
Open a first-contribution PR (or bug issue) on nexu-io/open-design โ works for non-coders too.
You are the **Anti-Pattern Czar**, an expert at identifying and fixing error handling anti-patterns.
RTK Codebase Health Audit โ 7 catรฉgories scorรฉes 0-10
Kubernetes-native AI automation platform for intelligent agentic sessions.
Portable, source-controlled configuration for AI coding assistants. my-ai-tools installs one consistent set of agent guidelines, skills, commands, hooks, MCP servers, and tool settings across supported AI coding assistants.
Official Factory plugins marketplace containing curated skills, droids, and tools.
Documentation A ZoneMinder client for web, desktop, iOS, and Android. It shows live camera feeds, a montage of many cameras at once, and events on a timeline, and has an AI chat agent you can ask about your cameras.
Runs eleven specialist agents that review code, analyze issues, and verify waves, plus commit and release-note commands. Fires when you plan an issue, orchestrate a swarm of agents, or cut a release.
Make Your Ideas Real. Build Apps, Websites and AI Agents with Plain English with Astro, React, Shadcn and Cloudflare.
Routes each task to a Codex, Gemini, or Claude model and gates code review. Fires when you ask for a review or a GitHub issue fix.
Searchable, application-level encryption for building privacy-first apps.
Agentic Coding with Claude Code, published by Packt.
Building the social economy for AI agents? Star the repo and help others find the path.
Every developer who has ever returned to a project after weeks away and found only ruins knows the wound CLEO was built to heal. The agents are powerful. But power without memory is chaos. Brilliance without continuity is waste.
Auto-invokedPlugins that fire their skills as you need them. You prompt as usual, and a Flowy hook picks the right skill, so you never have to invoke it by hand.How it works
Gives your coding agent a planning, testing and review routine to follow on every task. It plans before building, checks changes with tests, has a fresh reviewer look for regressions, and saves repeated wins as reusable skills.
Walks a software change from a written spec through design, testing, code review, CI/CD, and release, applying the matching engineering skill at each stage. Useful for developers using Claude Code on full development workflows.
Gives AI coding agents a repeatable engineering loop, from brainstorming and planning through building and review, and saves what each change taught so later work can reuse it. Covers tasks like shepherding a pull request to merge.
Gives you skills for pulling answers and prep from Circleback meeting notes, and for triaging failing GitHub Actions runs and GitHub issues. Use it to find what was decided, build meeting briefs, and sort CI failures and issues without digging through logs by hand.
Turns PDFs, scanned images, spreadsheets and other documents into clean text, tables and metadata, and splits them into chunks for LLM context windows or search. You can also batch-extract whole folders, pull keywords, and run OCR on scans without a text layer.
A research assistant plugin for Claude Code that supports literature review, paper writing, citation verification, Zotero and Obsidian integration, and code review and debugging for academic and software work.
Skills for building open data portals with PortalJS. Scaffold a portal, add datasets, charts and geospatial files, migrate an ArcGIS Hub site, and publish DCAT catalog feeds for national open-data harvesters.
A Claude Code plugin for iterative development with independent AI review. It generates and refines implementation plans, consults Codex and Gemini as second opinions, and runs a review loop where Codex checks each round of work.
A Rust development assistant for Claude Code with skills, agents, commands and hooks for code style, ownership, concurrency, error handling and refactoring, plus research on Rust docs and crates.
Reviews your code for structural decay such as tangled dependencies, duplicated knowledge and weak tests, citing classic engineering books for each finding. Each result comes with a severity label and a concrete fix, and an audit or debt-assessment mode can also map a roadmap for cleanup.
/plugin marketplace add owner/repoRun it once for the repository that lists the plugin. The listing page links that repository.
/plugin install plugin-name@marketplace-nameClaude Code opens the plugin panel on that plugin. Read it before you choose a scope, because a plugin can run hooks and MCP servers.
/plugin-name:fileA command file at commands/file.md in the plugin becomes /plugin-name:file. A subfolder adds another segment to the name.
No plugin needed for one command: save its Markdown file in .claude/commands/ and its file name becomes the command.
These steps are the pattern for a plugin listed in a marketplace. Each Flowy listing shows the install its own repository documents.
A slash command is a prompt you run by typing its name after a slash. Custom slash commands are Markdown files in .claude/commands/ or in a plugin, and Claude Code names a plugin command after the plugin. A command runs when you ask and never before.
Commands are the older format. Skills now do the same job and more, and a skill runs by name the same way.
Install the plugin that ships it and type the command with the plugin name in front. You can also save the Markdown file in .claude/commands/ to use it in one repository.
Yes. Custom commands have been merged into skills. A file in .claude/commands/ and a skill folder both create the same slash command, and a skill adds a folder for supporting files.
Claude Code namespaces plugin commands as /plugin-name:file so two plugins can ship a command with the same file name without colliding.
By the GitHub stars of the plugin that ships the command, one per plugin. A command has no stars of its own, and the card says which plugin the number belongs to.
Yes. A command is a Markdown prompt, and every command page on Flowy shows it as written with a link to its repository. Nothing runs until you type it.
In .claude/commands/ for one repository, in ~/.claude/commands/ for every project, or in the commands folder of a plugin. The Markdown file name becomes the command name.
Write $ARGUMENTS in the Markdown file. Claude Code replaces it with whatever you type after the command name. Positional placeholders pick out single words.
Skills are the current format and do the same job: a skill folder and a command file both create a slash command. Pick a skill when you want supporting files or want Claude to load it on its own. A command file suits a prompt you only run by hand.
Publish it on GitHub and the crawler finds it. Or send the repository yourself.
Submit a plugin