agentleFS
Sign inStart free
MakeItEzzz555MakeItEzzz555/Gridline/skills/materials-specifications/SKILL.md

materials-specifications

Skill39 starsChanged 23 days agoMITView on GitHub

Select, compare and document architectural materials, assemblies, finishes and performance requirements; draft outline and project specifications without inventing proprietary data. Use for material selection, finish schedules, performance specs, three-part specification structure, substitutions and technical product research.

The file

We split this skill into the rules it gives an agent

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

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈3

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 1

    Very specific

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

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Keep verified facts, project assumptions, design options, and unresolved questions visibly separate.

    line 15
  2. Distinctive:

    Do not reproduce copyrighted specification libraries or standards verbatim beyond allowed excerpts.

    line 40
  3. Distinctive:

    Do not invent certifications, test results, warranties, availability or code approvals.

    line 41
  4. Distinctive:

    If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application …

    line 45

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

Materials & Specifications

Connect design intent to measurable performance, installation, coordination and maintenance requirements.

Preflight

  • Project stage, location/exposure, assembly/function, design intent, durability/maintenance goals, fire/acoustic/thermal/moisture requirements, budget and procurement constraints.
  • Office/master specification system and product/manufacturer information when available.

Keep verified facts, project assumptions, design options, and unresolved questions visibly separate. If a required input is absent, record it as UNKNOWN rather than inventing it.

Workflow

  1. Define required performance before naming products; separate basis-of-design, approved equal and performance-only requirements.
  2. Compare materials on technical performance, durability, maintenance, embodied impact, availability, lead time, install interfaces and replacement strategy.
  3. Draft concise specification clauses or schedules with scope, products/performance and execution/quality-control headings.
  4. Coordinate specifications against drawings, schedules and details; track substitutions and deviations explicitly.

Deliverables

  • Material/finish option matrix
  • Outline or three-part specification draft
  • Finish/product schedule
  • Substitution/deviation register

Verification

  • Product values and standards are source-linked and edition-specific.
  • Drawings, schedules and specifications use consistent material/assembly names and performance requirements.

For file/model changes, compare the result against a pre-change baseline and report changed items, skipped items, failures, and checks actually run.

Professional boundaries

  • Do not reproduce copyrighted specification libraries or standards verbatim beyond allowed excerpts.
  • Do not invent certifications, test results, warranties, availability or code approvals.

If a live CAD/BIM/GIS/analysis tool or MCP integration is available, inspect the current document/model and tool version before write operations. Prefer read-only inspection, dry runs, bounded samples, new output paths, and native undo/transaction mechanisms. Never claim a model or drawing was changed unless the tool confirms it.

If the native application is unavailable, produce a reproducible plan, script, structured data, SVG/DXF artifact, or exact in-application procedure instead of pretending to have operated the software.

On-demand evidence and practice references

Load only the relevant reference. These are original review prompts, not binding code or full-book extraction.

  • B03: preliminary structure and MEP
  • B05: materials and construction sequence
  • B08: historical precedent
  • B09: timber interfaces
  • B10: glazed assemblies
  • B11: concrete coordination
  • B13: hospitality coordination
  • B14: material 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.

Check your setup, free