Tandem
Copilot instructions8 starsChanged 14 days agoMITView on GitHub
- Treat package.json as the single source of truth for the Tandem release version. - Before publishing or deploying a release, bump the package version with npm version patch --no-git-tag-version or the intended minor/major increment. - Run npm run pack after the bump so the displayed version, generated extension, and ZIP artifact all identify the same release. - Deploy both .github/extensions/tandem/extension.mjs and skills/tandem/SKILL.md to the matching user-scoped installation. The user-scoped provider owns processing when both scopes are loaded. - Edit…
Where files are headingNew Copilot instructions files have more rules about branches and pull requests, and fewer about code style.
Of the Copilot instructions files we read, the 2,349 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 repository22 other files it gives its agents.
- development/AGENTS.mdAGENTS.md
- backbone-designerSkill
- contract-designerSkill
- control-flow-designerSkill
- deployment-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 copilot-instructions.md into the rules it gives an agent
5 rules. About 0 are common, 0 are distinctive, and 5 are very specific to this project.
≈0
Common · estimate
Many files like this have a rule of this kind.
≈0
Distinctive · estimate
This author's own choices. Worth a look.
5
Very specific
Tied to their project's names, files or tools. Probably skip.
- Common
- Distinctive
- Very specific
- Very specific: line 3
Treat package.json as the single source of truth for the Tandem release version.
- Very specific: line 4
Before publishing or deploying a release, bump the package version with npm version patch --no-git-tag-version or the intended minor/major …
- Very specific: line 6
Run npm run pack after the bump so the displayed version, generated extension, and ZIP artifact all identify the same release.
- Very specific: line 16
Keep process-block integrations behind ProcessAdapterRegistry.
- Very specific: line 23
Use src/planning-prompts.ts for production and behavioral evaluations rather than maintaining separate prompt copies.
≈ “Common” is an estimate: at least 1 in 5 of the 3,779 Copilot instructions 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
Project memory
- Treat
package.jsonas the single source of truth for the Tandem release version. - Before publishing or deploying a release, bump the package version with
npm version patch --no-git-tag-versionor the intended minor/major increment. - Run
npm run packafter the bump so the displayed version, generated extension, and ZIP artifact all identify the same release. - Deploy both
.github/extensions/tandem/extension.mjsandskills/tandem/SKILL.mdto the matching user-scoped installation. The user-scoped provider owns processing when both scopes are loaded.
Implementation boundaries
- Edit maintainable TypeScript and renderer assets under
src/, not the generated extension. Usenpm run check,npm test, andnpm run build. - Keep process-block integrations behind
ProcessAdapterRegistry. Local and GitHub selections must preserve artifact and receipt history; never silently substitute adapters after an error. - Operational state belongs in ignored
.tandem; accepted exports belong intandem-recordsonly after an explicit export. Export is not Git publication. - Worker-reported completion is not tool-backed evidence. Preserve source, request, and specification identities when recording or reusing a pass.
- Use
src/planning-prompts.tsfor production and behavioral evaluations rather than maintaining separate prompt copies. Live evaluations require explicit model and execution limits.
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.