agentleFS
dfinsondfinson/promptlings/skills/design-analysis/SKILL.md

design-analysis

Skill1 starsChanged 11 days agoApache-2.0View on GitHub

Examine technical designs and plans against requirements, constraints, alternatives, and integration consequences. Use when exploring an architecture or deciding between materially different approaches.

2 other projects use a version of this.

Adopted by

Most recently taken up by

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    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:

    Stop when the decision can be made on the available evidence or its material dependency is explicit.

    line 34

≈ “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

Design Analysis

Goal

Make the decision and its consequences understandable, then recommend a direction when the evidence and the caller's priorities support it.

Method

  1. Establish the intended behavior, constraints, confirmed decisions, and criteria that distinguish success from failure. Inspect existing solutions and contracts before proposing new abstractions or dependencies.
  2. Identify credible alternatives when they differ materially. Trace their implications for producers and consumers, data validity, state transitions, error recovery, concurrency, operations, and migration as relevant.
  3. Separate internal contradictions and demonstrated failures from tradeoffs. A documented, deliberate tradeoff is not automatically a defect. A missing requirement is an evidence gap until its applicability is established.
  4. Examine costly-to-reverse decisions, hidden assumptions, and the evidence that would change the recommendation. Seek a counterexample to the favored approach.
  5. Recommend a direction with its consequences when supported. When the choice depends on missing user priorities, identify the concrete decision and what would settle it.

Select the smallest coherent mechanism that addresses the observed problem, reusing existing capabilities before adding abstractions or infrastructure. Distinguish a complete opportunity catalogue from the selected implementation, an experiment needed to choose, and a policy decision requiring human judgment. Completeness of discovery does not make every possibility a delivery obligation. Compare implementation and ongoing ownership cost with the supported benefit. More services, coordination, persistent state or PRs for a modest objective should trigger simplification, not automatic decomposition. Preserve essential correctness and explicit constraints without inventing universal size limits.

Return and stop

Return the decision under discussion, material alternatives and consequences, supported recommendation or unresolved choice, and required evidence. Scale detail to the decision rather than imposing a template or fixed number of alternatives.

Stop when the decision can be made on the available evidence or its material dependency is explicit. Do not create a plan, change source, or treat a recommendation as approval to implement unless requested.

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.