making-things
AGENTS.md1 starsChanged 4 months agoMITView on GitHub
This repository packages a tool-agnostic Electron workflow plugin. It is not an Electron application and it contains no project-specific workflow records. - A project using this plugin stores its PRD, contract, plans, research, workstreams, work items, handoffs, and capability evidence only in the sibling Git control repository ../.making/<project-slug>/. - Never create .making/ in a project code repository. local.yaml and *.local.yaml belong only in the control repository and remain ignored. - Do not record secrets, raw user prompts, or absolute machine…
Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.
Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.
In this repository15 other files it gives its agents.
- electron-debugSkill
- electron-implementationSkill
- electron-ipc-securitySkill
- electron-releaseSkill
- electron-reviewSkill
- electron-test-e2eSkill
- github-deliverySkill
- handoffSkill
- handonSkill
- making-thingsSkill
- mts-moreSkill
- mts-oneSkill
- mts-splitSkill
- product-prdSkill
- solution-architectureSkill
The file
We split this AGENTS.md into the rules it gives an agent
6 rules. About 1 is common, 2 are distinctive, and 3 are very specific to this project.
≈1
Common · estimate
Many files like this have a rule of this kind.
≈2
Distinctive · estimate
This author's own choices. Worth a look.
3
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 11
Never create .making/ in a project code repository.
- Common: line 13
Do not record secrets, raw user prompts, or absolute machine paths in the control repository.
- Very specific: line 22
Read the sidecar PROJECT.md, relevant TRACK.md, TASK.md, and the applicable Skill before changing a workstream record.
- Very specific: line 42
Keep renderer code browser-only.
- Distinctive: line 47
Verify privileged IPC senders and inputs at runtime.
- Distinctive: line 51
Use test-first development for behavior changes and preserve unrelated user changes.
≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md 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
Making Things plugin instructions
This repository packages a tool-agnostic Electron workflow plugin. It is not an Electron application and it contains no project-specific workflow records.
Control-repository boundary
- A project using this plugin stores its PRD, contract, plans, research,
workstreams, work items, handoffs, and capability evidence only in the
sibling Git control repository
../.making/<project-slug>/. - Never create
.making/in a project code repository.local.yamland*.local.yamlbelong only in the control repository and remain ignored. - Do not record secrets, raw user prompts, or absolute machine paths in the control repository.
- Packaged Skills, templates, native manifests, adapters, and optional hooks remain source assets in this repository; they are not project records.
Prompt-first workstreams
- A full lifecycle starts only after an explicit user invocation of
making-things. - Read the sidecar
PROJECT.md, relevantTRACK.md,TASK.md, and the applicable Skill before changing a workstream record. Never auto-start a workflow. - There are exactly three workstream classes:
frontend,backend, andintegration. A summary is lowercaseYYYY-MM-DD-english-summary. - A responsible parent Agent manually creates and enters the code branch
{lane}/{date-summary}and.worktrees/{lane}/{date-summary}/. The plugin does not create branches, worktrees, commits, or pushes. - Frontend and backend may proceed in parallel only after an approved contract assigns non-overlapping scopes. Integration begins after its declared inputs are complete. TDD subtasks never receive separate worktrees.
mts-oneis parent-led sequential TDD.mts-moremay use one writing native subagent at a time only when the adapter recordsWRITE_SUBAGENT: VERIFIED; otherwise route tomts-one.handoffandhandonpause and resume a whole workstream, not an individual TDD subtask. Hooks are optional notices only.
Electron safety and evidence
- Keep renderer code browser-only. Expose narrowly scoped preload APIs with
contextBridge; never expose raw privileged Electron or Node APIs. - Preserve
nodeIntegration: false,contextIsolation: true,sandbox: true, andwebSecurity: trueunless a documented, approved exception exists. - Verify privileged IPC senders and inputs at runtime. Do not weaken security or tests to hide a failure.
- Capability claims are only
VERIFIED,DEGRADED, orUNSUPPORTEDand require dated smoke evidence. Do not simulate unsupported host behavior. - Use test-first development for behavior changes and preserve unrelated user changes. Push, publish, sign, or create a release only with explicit user authorization and fresh evidence.
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.