legacy-command-client-keeper

Maintain the optional prefix-command layer for DiscordCommandClient and Command parsing.

1.1k|250|Updated Aug 12, 2015

Search Tags:#discord #parsing #aliases #maintain #cooldowns #command-client

Ready to run

npx skills add https://github.com/discord-php/DiscordPHP --skill legacy-command-client-keeper

💬 Prompt for ChatGPT / Claude Chat▼

Please help me install this Agent Skill.
Skill: legacy-command-client-keeper
Source: https://github.com/discord-php/DiscordPHP/tree/main/.agents/skills/legacy-command-client-keeper
Command: npx skills add https://github.com/discord-php/DiscordPHP --skill legacy-command-client-keeper

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Maintaining and evolving the optional prefix-command layer (DiscordCommandClient) without impacting core Discord functionality, ensuring safe command parsing and separation from application commands.

Core Features & Use Cases

Keeps the command-client option resolution, lifecycle, and routing isolated from core runtime so changes do not ripple into application commands.
Preserves prefix and mention-prefix expansion, top-level command and alias registries, and default help behavior when working on the command layer.
Use case: editing src/Discord/DiscordCommandClient.php or src/Discord/CommandClient/Command.php to update command-layer behavior without affecting core Discord.

Quick Start

Load this skill when maintaining the message-based command layer to preserve the optional prefix-command behavior.

Frequently Asked Questions about legacy-command-client-keeper

High-intent search queries and answers about installing and using this skill.

FAQPage Schema

How do I maintain prefix-command parsing without affecting the core Discord runtime?▼

You maintain prefix-command parsing by isolating the DiscordCommandClient lifecycle and routing from the core Discord runtime. This separation ensures command parsing, aliasing, cooldowns, and help behavior remain cleanly separated from core application commands.

What is the best way to update command aliases and cooldowns in a Discord command client?▼

The best way to update command aliases and cooldowns is to modify them within the optional prefix-command layer. This preserves the top-level command and alias registries while ensuring changes remain non-intrusive to the core Discord client.

Does editing the DiscordCommandClient impact default help behavior?▼

Editing the DiscordCommandClient does not impact default help behavior if you maintain the recommended command-layer structure. The optional prefix-command layer is designed to preserve help behavior while keeping changes isolated from the core Discord runtime.

Can I modify prefix and mention-prefix expansion without breaking application commands?▼

Yes, you can modify prefix and mention-prefix expansion without breaking application commands. The command-client layer enforces strict boundaries so message-based command flow updates do not ripple into the core Discord client or application commands.

When should I not use the optional prefix-command layer for Discord commands?▼

You should not use the optional prefix-command layer when working on core Discord functionality or application commands. It is specifically designed for maintaining message-based command flow and should remain isolated from the core runtime.