skills.rest
gesslar
gesslarCOMMUNITY
Explore all skills by this author →
WebsiteGitHub

command-creation

Create and standardize Oxidus LPC commands with naming, inheritance, and entry points.

8|3|Updated Sep 29, 2021
Search Tags:#design#documentation#inheritance#command#lpc#oxidus
One-click install
npx skills add https://github.com/gesslar/oxidus-mudlib --skill command-creation-gesslar
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: command-creation
Source: https://github.com/gesslar/oxidus-mudlib/tree/main/.claude/skills/command-creation
Command: npx skills add https://github.com/gesslar/oxidus-mudlib --skill command-creation-gesslar

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

This skill helps developers create and modify Oxidus commands with consistent naming, inheritance hierarchy, entry points, and documentation, reducing setup friction.

Core Features & Use Cases

  • Standardized command naming and location conventions for Oxidus LPC commands.
  • Clear inheritance guidance (STD_CMD, STD_ACT, STD_ABILITY, STD_SPELL) and a mapped directory structure.
  • Guidance on entry points, return value handling, and help text to ensure uniform UX and maintainability.
  • Use Case: When adding a new verb, generate a solid command skeleton that follows the project conventions.

Quick Start

Create a new standard command named eat that inherits STD_ACT and includes a minimal main() implementation.

Frequently Asked Questions about command-creation

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

FAQPage Schema
How do I create a new Oxidus LPC command with the correct inheritance?▼

Oxidus command inheritance defines a hierarchy using STD_CMD, STD_ACT, STD_ABILITY, and STD_SPELL to standardize behavior and structure. This mapped hierarchy ensures commands follow consistent directory conventions and return semantics across different command categories.

How do I standardize entry points and return values for Oxidus commands?▼

Yes, you can generate a command skeleton for a new verb like eat that inherits STD_ACT. The workflow provides a minimal main() implementation and automatically applies the project's naming and location conventions to reduce setup friction.

What documentation structure is required for an Oxidus command SKILL.md?▼

Use this command creation workflow for both new development and maintenance scenarios where consistent command structure is required. It standardizes naming, inheritance, entry points, and documentation to reduce setup friction across the entire project.

Why does my Oxidus command structure lack consistent return semantics?▼

Use this command creation workflow for both new development and maintenance scenarios where consistent command structure is required. It standardizes naming, inheritance, entry points, and documentation to reduce setup friction across the entire project.

Related Skills

Explore More Software Engineering Skills→
gesslargesslar
8

http-client

Create LPC HTTP client daemons for Oxidus issuing outbound requests and managing responses.

Community
Advanced
gesslargesslar
8

lpc-coding-style

Enforces LPC coding conventions for oxidus-mudlib repository modules.

Community
Intermediate
gesslargesslar
8

wiki-writing

Standardize Oxidus wiki page creation with frontmatter, layout, and component rules.

Community
Intermediate
docs-plusdocs-plus
88

scaffold-exercises

Generate standardized exercise directory structures with required subfolders and stub files.

Official
Intermediate