agentleFS
mikezangusmikezangus/agent-skills/structural-design/SKILL.md

structural-design

Skill0 starsChanged 29 days agoMITView on GitHub

Choose and review responsibilities, grouping, boundaries, and dependencies. Use when deciding what parts are needed, how they should be grouped, and how they must work together.

The file

We split this skill into the rules it gives an agent

4 rules. About 0 are common, 4 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈4

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Use established dependencies to identify constraints and missing prerequisites within the authorized work.

    line 17
  2. Distinctive:

    When constructing or revising an arrangement, work from required contributions to available ways of supplying them and the conditions under …

    line 63
  3. Distinctive:

    Use the relevant language, tool, or discipline's established meanings for its constructs.

    line 71
  4. Distinctive:

    Use the identified contributions and dependencies to compare grouping, separation, and placement.

    line 96

≈ “Common” is an estimate: at least 1 in 5 of the 350,495 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

Establish the required result

Interpret the request in its available context. Distinguish the result sought, the work authorized, and the choices the request fixes or leaves open. Support each consequential interpretation through the request and applicable rules. Use established dependencies to identify constraints and missing prerequisites within the authorized work. Determine separately what the result must accomplish and how it is to be presented.

For an example or comparison, identify the relationship it illustrates or the claim it challenges and the scope the request assigns to it. Establish which features affect the required result. For a proposed term, method, or arrangement, determine whether the request adopts it, requires its examination, or permits alternatives.

Compare readings that would change the result or authorized work against the available context. Investigate a missing fact; make a delegated choice within its stated constraints; obtain clarification for a remaining difference that changes what is required or permitted. Continue work whose validity is independent of that unresolved difference.

Derive the behavior, information, or understanding the result must supply from the request, supporting facts, and applicable rules. Use that basis to determine which instructions apply.

For each requirement, identify the information needed to assess satisfaction and select a method that can establish the required property. Identify preservation obligations. Use the same requirements to assess an existing arrangement and a replacement.

Identify missing facts that could change a responsibility, grouping, or dependency decision. Obtain those facts through authorized means or identify the decision they prevent. Keep an unresolved assumption distinguishable from a supported basis for selecting an arrangement.

Identify contributions and dependencies

Establish which contributions the arrangement must produce or maintain and which it only consumes from existing or external providers. Justify a new production or maintenance responsibility through the authorized task.

Distinguish work needed to produce or assess the current result from responsibilities that must continue afterward. Justify each continuing responsibility through a later use or preservation obligation within the authorized task.

For each proposed part, identify the behavior it performs, the information it establishes or preserves, or the understanding it enables. Identify what it requires from other parts to supply that result. Derive these contributions from the required result independently of proposed names and locations.

When constructing or revising an arrangement, work from required contributions to available ways of supplying them and the conditions under which those ways work. Establish those relationships to the detail needed to justify the arrangement. Use the conditions to constrain choices that must work together, distinguishing what the arrangement establishes from what it requires of external suppliers. Obtain a missing construction method where it is needed to establish the arrangement, or identify the capability that remains unresolved.

Use the relevant language, tool, or discipline's established meanings for its constructs. State a local meaning where the task requires a different use. Give a proposed name the meaning established by its content or responsibility.

For each dependency, identify the receiving part, supplying part, and required information or behavior. Compare what the receiver requires with what the supplier establishes under the conditions of use. Obtain or establish a missing property needed for that relationship, or keep the dependency unresolved.

Where a required property can cease to hold before or during a dependent use, establish when and for how long it must hold. Identify what preserves that condition or prevents the dependent use when it does not hold.

Identify the parts that make or maintain a choice, the information they need, and what other parts require from the result. Determine which decisions can be made within each part and which require information from elsewhere.

For proposed shared behavior or instructions, identify the required behavior, information, and assumptions that remain the same across their uses. Determine which differences are inputs to the same procedure and which require a different procedure or prerequisites. Establish the applicability of the shared behavior from those facts.

Compare and select an arrangement

Use the identified contributions and dependencies to compare grouping, separation, and placement. For each proposed separation, identify what it changes about access, understanding, execution, maintenance, or other required behavior. Determine what the actual mechanisms control and what depends on stated rules.

Compare the dependencies each alternative adds, removes, or retains. Determine which information its parts must share or keep consistent, which uses remain possible, and which decisions can change independently. Justify placement through those relationships and consequences.

Trace the changes the task or available evidence gives reason to expect. Determine which parts each change would affect and why. Distinguish a change in what is supplied from a change in how it is produced. Use those consequences to assess the dependencies created by each arrangement.

Derive required execution or explanation order from what must be available for an action or understanding to occur. Establish the dependency requiring that order independently of the proposed grouping.

Select among alternatives using the task's priorities and constraints. State a tradeoff through the differing properties and their consequences. Preserve open alternatives where the available basis permits several choices. Investigate further to resolve a specified difference that could change the selection, in proportion to the consequences of a mistaken choice.

Produce the arrangement or assessment requested by the task. Preserve fixed choices and establish the relationships selected through the comparison.

Examine the arrangement

For each applicable requirement, follow the required behavior, information, or understanding through the parts that supply it. Check that information is available where it is used, that suppliers establish what receivers require, and that their combined result satisfies the requirement.

Examine each boundary through the effects used to select it. Trace the effects of relevant changes on what must remain usable or unchanged. Use the actual access and execution mechanisms to establish enforced properties. Distinguish predicted effects from effects observed in use.

Identify the affected part, required property, examination method, supporting evidence, and finding. Establish required execution from observations of the performed actions. Compare the task requirements and applicable procedural actions with the completed examinations. If that comparison establishes an omitted check, unsupported finding, or discrepancy, identify the requirement and information that expose it.

Correct discrepancies and determine completion

For an established discrepancy, locate the responsible assumption, responsibility, grouping, or dependency. Return to that decision and select a correction through its effects on the required result. Compare retaining, replacing, dividing, combining, reordering, or removing material where those choices address the discrepancy.

Apply changes within the task's authority. In an assessment-only task, present the supported correction as a proposal. Re-examine the changed result and the behavior or dependencies affected by the change. A changed requirement or supporting fact also requires reconsidering the decisions and examinations that depend on it. Continue correction where the new examination establishes a remaining discrepancy.

Determine whether each unresolved point is a permitted uncertainty or choice, or leaves required work unfinished. Obtain the information or authorization needed for unfinished work where the task permits. Otherwise identify what remains required and what prevents establishing it.

Deliver the requested result as complete when examination of that result establishes satisfaction of each applicable requirement and required procedural action. Base the completion judgment on those findings and their evidence.

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.