subskill-generation-rule

What This Skill Does

The subskill-generation-rule acts as an architectural blueprint for OpenClaw AI agents, ensuring that projects remain maintainable as they scale. As AI agents generate more code and artifacts, skill roots often become cluttered with one-off scripts and data files. This skill enforces a structured hierarchy by mandating that artifacts go into a data/ directory and feature-specific code is isolated within subskills/<feature>/. By centralizing documentation into a SKILL.md file within each feature folder, it ensures that project knowledge is decentralized and contextually scoped, preventing the main root directory from becoming an unmanageable mess. This is essential for long-term project viability.

Installation

To integrate this architectural standard into your current OpenClaw project, run the following command in your terminal:

clawhub install openclaw/skills/skills/kenera/subskill-generation-rule

Use Cases

This skill is highly recommended for developers who are building modular agents where multiple features or capabilities are added over time. It is particularly useful when:

1. Refactoring legacy projects: Use it to reorganize scattered files into a standard structure.
2. Large-scale automation: When your agent needs to generate dozens of Python scripts or temporary logs, this keeps the workspace clean.
3. Collaborative environments: Standardizing folder layouts ensures that multiple AI agents or human developers know exactly where to find source code, configuration, and documentation.
4. Preventing Technical Debt: By enforcing these rules early, you avoid the 'spaghetti root' problem where root-level scripts become impossible to track.

Example Prompts

1. "Apply the subskill-generation-rule structure to my current project. Move all log files to data/ and group my report generators into subskills/report-generator/."
2. "I need to add a new data extraction feature. Please set up the folder structure according to the subskill-generation-rule and create a SKILL.md file for the documentation."
3. "Refactor my root directory. Move all stray Python scripts into subskills/ and ensure every module has its own SKILL.md for instructions."

Tips & Limitations

To maximize effectiveness, initialize this skill at the very start of your project development. While it is possible to apply it retrospectively, moving existing files might break hardcoded paths in your previous configurations. Always verify that your import statements are updated after moving scripts into the subskills/ subdirectories. Remember that this skill focuses on structure; it does not automatically refactor the logic within your code, only the file placement conventions.