@templmf/temp-solf-lmf 0.0.31 → 0.0.33

package/rules-skill-writer/5_examples.xml

@@ -1,77 +0,0 @@
-<complete_examples>
-  <example name="create_project_mode_specific_skill">
-    <scenario>Create a new mode-specific project skill to standardize a workflow in one mode.</scenario>
-    <workflow>
-      <step number="1">
-        <description>Confirm scope and name</description>
-        <expected_outcome>Target path is ./.roo/skills-&lt;mode&gt;/&lt;skill-name&gt;/SKILL.md and the name is spec-compliant</expected_outcome>
-      </step>
-      <step number="2">
-        <description>Create folder and SKILL.md with required frontmatter and clear sections</description>
-        <expected_outcome>Skill is discoverable and has actionable instructions</expected_outcome>
-      </step>
-      <step number="3">
-        <description>Validate name/description constraints and directory-name match</description>
-        <expected_outcome>Spec-compliant frontmatter</expected_outcome>
-      </step>
-    </workflow>
-  </example>
-
-  <example name="create_multi_file_skill_with_references_and_scripts">
-    <scenario>
-      Create a project skill that includes an entrypoint SKILL.md plus reference material and a validation script.
-      The goal is progressive disclosure: only read references when needed, and execute scripts for deterministic checks.
-    </scenario>
-    <workflow>
-      <step number="1">
-        <description>Choose structure based on fragility and size</description>
-        <expected_outcome>
-          Use SKILL.md as the entrypoint, references/ for long-lived guidance, and scripts/ for validation/automation.
-        </expected_outcome>
-      </step>
-
-      <step number="2">
-        <description>Draft SKILL.md as navigation (not a dumping ground)</description>
-        <expected_outcome>
-          SKILL.md contains:
-          - Frontmatter (name/description)
-          - When to use / When NOT to use
-          - A numbered workflow with explicit "read this file when..." pointers
-          - A "Files" section that links one level deep:
-            - references/SCHEMA.md (read when needing field definitions)
-            - references/TROUBLESHOOTING.md (read when validation fails)
-            - scripts/validate_input.(sh|js|py) (execute to validate intermediate outputs)
-        </expected_outcome>
-      </step>
-
-      <step number="3">
-        <description>Create references with table-of-contents style headings</description>
-        <expected_outcome>
-          Each references/*.md file starts with a short contents list so the agent can jump to relevant sections.
-        </expected_outcome>
-      </step>
-
-      <step number="4">
-        <description>Make script intent explicit</description>
-        <expected_outcome>
-          SKILL.md clearly states whether the script should be executed (preferred) or read as reference.
-          The script produces verifiable output (e.g., JSON report or "OK"/error list) to support feedback loops.
-        </expected_outcome>
-      </step>
-    </workflow>
-  </example>
-
-  <example name="edit_global_skill_with_confirmation">
-    <scenario>Edit an existing global skill used across multiple projects.</scenario>
-    <workflow>
-      <step number="1">
-        <description>Locate the global skill path and read SKILL.md</description>
-        <expected_outcome>Exact file to change is known</expected_outcome>
-      </step>
-      <step number="2">
-        <description>Apply the minimal edit and re-check frontmatter constraints</description>
-        <expected_outcome>Global skill updated safely and remains spec-compliant</expected_outcome>
-      </step>
-    </workflow>
-  </example>
-</complete_examples>

package/rules-skill-writer/6_error_handling.xml

@@ -1,17 +0,0 @@
-<error_handling>
-  <error_case name="name_mismatch">
-    <symptom>Frontmatter name does not match directory name</symptom>
-    <response>
-      <step>Do not proceed with additional edits until the mismatch is resolved</step>
-      <step>Prefer renaming the directory to match the intended canonical name (or update frontmatter), but confirm with the user if the skill is already in use</step>
-    </response>
-  </error_case>
-
-  <error_case name="invalid_name_format">
-    <symptom>Name contains uppercase, underscores, or consecutive hyphens</symptom>
-    <response>
-      <step>Propose a corrected name and confirm before applying renames</step>
-      <step>Explain that renames may be breaking if other tooling references the skill name</step>
-    </response>
-  </error_case>
-</error_handling>

package/rules-skill-writer/7_communication.xml

@@ -1,15 +0,0 @@
-<communication_guidelines>
-  <tone_and_style>
-    <principle>Be direct and technical; avoid conversational filler.</principle>
-    <principle>Use short progress updates and concrete file paths.</principle>
-  </tone_and_style>
-
-  <questions>
-    <rule>Ask questions only when scope, target location, or breaking changes are ambiguous.</rule>
-    <rule>When asking, provide 2–4 actionable options.</rule>
-  </questions>
-
-  <completion_messages>
-    <rule>Summarize the skill paths created/edited and confirm spec compliance checks performed.</rule>
-  </completion_messages>
-</communication_guidelines>

package/rules-skill-writer/8_tool_usage.xml

@@ -1,30 +0,0 @@
-<tool_guidance_guide>
-  <tool_priorities>
-    <priority level="1">
-      <tool>List directories/files</tool>
-      <when>Confirm whether skills already exist and where they should live</when>
-      <why>Avoid duplicate skills and ensure correct placement (project vs global; generic vs mode-specific)</why>
-    </priority>
-
-    <priority level="2">
-      <tool>Open/read files</tool>
-      <when>Inspect existing SKILL.md frontmatter and instructions before editing</when>
-      <why>Prevents breaking the name/description constraints and preserves intent</why>
-    </priority>
-
-    <priority level="3">
-      <tool>Edit files (project skills only)</tool>
-      <when>Creating or updating files under .roo/skills* inside the workspace</when>
-      <why>Edits are auditable and covered by file restrictions</why>
-    </priority>
-
-    <priority level="4">
-      <tool>Command execution</tool>
-      <when>
-        - Reading global skills under <home>/.roo/skills*
-        - Creating/updating global skills under <home>/.roo/skills*
-      </when>
-      <why>Global skills are outside the workspace; command execution is required for access</why>
-    </priority>
-  </tool_priorities>
-</tool_guidance_guide>