agentleFS
BenknightdarkBenknightdark/neo-skills/skills/neo-csharp-interface-generator/SKILL.md

neo-csharp-interface-generator

Skill7 starsChanged 6 months agoMITView on GitHub

Use this skill when the user asks to generate, update, or place a C# interface from an existing class. Trigger for extracting public members, filtering virtual or non-public members, enforcing getter-only properties, and safely creating, appending, or replacing interface blocks.

The file

We split this skill into the rules it gives an agent

9 rules. About 0 are common, 7 are distinctive, and 2 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈7

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 2

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Environment Awareness: When the user specifies a target file, read the file content to check for the existence of an Interface with the …

    line 21
  2. Very specific:

    Language Constructs Check (C# 15): Verify whether the target type is a C# 15 union or a standard class/record.

    line 22
  3. Very specific:

    Getter Only: All properties in the interface MUST only have a get.

    line 30
  4. Distinctive:

    Formatting: Ensure the generated Interface follows standard C# indentation and brace styles.

    line 32
  5. Distinctive:

    If the target file does not exist: Plan to create a new file with necessary namespaces.

    line 34
  6. Distinctive:

    If the target file exists but has no Interface with the same name: Plan to append the new Interface to the end of the file.

    line 35
  7. Distinctive:

    If the target file exists and already contains an Interface with the same name:

    line 36
  8. Distinctive:

    Use regular expressions or block matching to find the start and end positions of the Interface.

    line 37
  9. Distinctive:

    After generation, pause and ask the user: "In which file should this Interface be stored?

    line 43

≈ “Common” is an estimate: at least 1 in 5 of the 372,429 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
SKILL.md

C# Interface Generator Skill Specification

Perceive

  1. Code Structure Recognition: Parse C# Class content, identify properties, methods, and access modifiers.
  2. Constraint Check:
    • Identify members with the virtual keyword.
    • Identify non-public members.
  3. Environment Awareness: When the user specifies a target file, read the file content to check for the existence of an Interface with the same name.
  4. Language Constructs Check (C# 15): Verify whether the target type is a C# 15 union or a standard class/record. Union types represent closed type choices and usually do not require extracting traditional interfaces.

Reason

  1. Interface Generation Logic:
    • Naming Convention: The Interface name must be the Class name prefixed with I.
    • Property Filtering:
      • Keep only simple properties.
      • Strictly prohibit properties containing the virtual modifier.
      • Getter Only: All properties in the interface MUST only have a get; accessor. No set; or init; is allowed.
      • Include only public members.
    • Formatting: Ensure the generated Interface follows standard C# indentation and brace styles.
  2. Smart Overwrite Strategy:
    • If the target file does not exist: Plan to create a new file with necessary namespaces.
    • If the target file exists but has no Interface with the same name: Plan to append the new Interface to the end of the file.
    • If the target file exists and already contains an Interface with the same name:
      • Use regular expressions or block matching to find the start and end positions of the Interface.
      • Plan to replace only that specific block, preserving other classes, interfaces, or using declarations in the file.

Act

  1. Code Generation: Output a C# Interface that complies with the Reason logic.
  2. User Confirmation:
    • After generation, pause and ask the user: "In which file should this Interface be stored? (Please provide a relative path)".
  3. Execution Write:
    • Based on the user's response, perform read_file (if the file exists) -> logical replacement -> write_file.
    • Inform the user of the result (created, appended, or overwritten).
  4. Output Language: The final output to the user must be in Traditional Chinese (Taiwan).

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.