instruction-factory

Generate path-specific coding rules as *.instructions.md files for source directories.

Updated May 18, 2026
One-click install
npx skills add https://github.com/fzturk/clearlegaltips-workspace --skill instruction-factory
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: instruction-factory
Source: https://github.com/fzturk/clearlegaltips-workspace/tree/main/.claude/skills/instruction-factory
Command: npx skills add https://github.com/fzturk/clearlegaltips-workspace --skill instruction-factory

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill automates the creation of *.instructions.md files for a system, establishing path-specific coding rules for each major source directory, thus streamlining the implementation patterns and enforcing forbidden practices.

Core Features & Use Cases

  • Automated Rule Generation: Generates always-on instruction files for specific directories.
  • Domain-Specific Instructions: Defines implementation patterns, forbidden practices, and references for each domain.
  • Use Case: After completing the SYSTEM_MANIFEST.md and agents, use this Skill to automatically generate coding rules for your source directories.

Quick Start

Use the instruction-factory skill to generate coding rules for your source directories after completing the SYSTEM_MANIFEST.md and agents.

Frequently Asked Questions about instruction-factory

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

FAQPage Schema
How do I generate path-specific coding rules for source directories?

Generating domain-specific coding rules produces *.instructions.md files that define implementation patterns, forbidden practices, and references for each major source directory, streamlining code standards across your system.

What are domain-specific coding rules and how do they enforce code standards?

Domain-specific coding rules are path-specific instructions defined in *.instructions.md files that establish implementation patterns and forbidden practices for each major source directory to enforce strict code standards.

How do I create instruction files that define forbidden practices for specific directories?

You can create instruction files defining forbidden practices by running scripts that generate *.instructions.md files, which configure domain-specific rules and implementation patterns for each major source directory.

What do I need before generating coding rules for my source directories?

Before generating coding rules for source directories, you need to complete the SYSTEM_MANIFEST.md and agents setup, as the instruction generation process depends on these foundational system configurations.

Are there limitations to automating coding rule generation for domain-specific configurations?

Automating coding rule generation requires executing scripts and handling domain-specific configurations manually, meaning you must properly define the major source directories and their specific implementation patterns beforehand.