deployment-designer
Skill8 starsChanged 14 days agoMITView on GitHub
Refine runtime technologies in the layered System stack.
In this repository22 other files it gives its agents.
- development/AGENTS.mdAGENTS.md
- .github/copilot-instructions.mdCopilot instructions
- backbone-designerSkill
- contract-designerSkill
- control-flow-designerSkill
- gui-designerSkill
- module-designerSkill
- stack-designerSkill
- storage-contract-designerSkill
- use-case-designerSkill
- tandemSkill
- backbone-designerSkill
- contract-designerSkill
- control-flow-designerSkill
- deployment-designerSkill
- gui-designerSkill
- module-designerSkill
- stack-designerSkill
- storage-contract-designerSkill
- use-case-designerSkill
- brainstorm-whiteboardSkill
- tandemSkill
The file
We split this skill into the rules it gives an agent
3 rules. About 0 are common, 2 are distinctive, and 1 is very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈2
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
- Distinctive: line 9
Use this method when runtime topology, trust boundaries, scaling, availability, rollout, observability, or operational ownership materially …
- Very specific: line 13
Add or refine only the runtime-oriented technologies in existing systemStacks[0].layers.
- Distinctive: line 15
Add a runtime layer only when it materially helps review.
≈ “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.
Files
Deployment Designer
Use this method when runtime topology, trust boundaries, scaling, availability, rollout, observability, or operational ownership materially affects the design. Omit it for local-only work or when deployment has no consequential choices.
Add or refine only the runtime-oriented technologies in existing systemStacks[0].layers. Use
specific choices such as Electron, container, or managed PostgreSQL, with a short role.
Add a runtime layer only when it materially helps review. Do not create a Deployment tab, another
aspect, topology graph, coordinates, or styling.
Explain each runtime choice by its visible operational purpose—where the product runs, who manages it, and what reliability or privacy consequence it has—without assuming infrastructure experience.
Return consequential runtime or deployment Attention to stack-designer, attached to
the affected System layer and tagged blocking or non-blocking.
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
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.