feat(init): generate AGENTS.md with plugin development conventions

[mackenziemcclaskey]

Summary

• Adds renderAgentsMd() to init-template.ts — produces an AGENTS.md guide for agentic coding assistants (Cursor, Claude Code, etc.) working in a WE plugin project
• Adds writeAgentsMdIfAbsent(pluginDir) to init.ts — writes AGENTS.md during init, skips gracefully if one already exists
• Wires writeAgentsMdIfAbsent into InitCommand.run() after plugin.tsx is written

AGENTS.md covers:

• What the project is and where the entry point lives (plugin.tsx)
• Routes and type-safe navigation (route(), useNavigate(), useParams())
• Data provider context — DataResolver, DataProvider, GraphQLResolver, generated hooks from everywhere bind
• Peer dependency constraints (react, react-dom ≥18 must not be bundled)
• Import conventions (.js extensions required on all local imports)
• CLI reference (everywhere dev, everywhere build, everywhere bind)

Test plan

• just test passes (373 tests, all green)
• just check passes (typecheck + lint + prettier)
• 14 new tests added: 8 for renderAgentsMd() in init-template.test.ts, 5 for writeAgentsMdIfAbsent in init.test.ts
• Manually run we init in a fresh directory and confirm AGENTS.md is generated with correct content
• Re-run we init in a directory that already has AGENTS.md and confirm it is not overwritten

🤖 Generated with Claude Code

[mpfilbin]

I think this looks good as is. I made a couple of suggestions that might be worth considering.

[mpfilbin]

We might consider adding references (URLs) to our example applications to this file so the agent can go an reference implementations to help improve the changes of producing a viable plugin with zero-shot prompting.

[mpfilbin]

We might also consider having this be a standalone .md file in the repository calling it something like agents.template.md. It might be easier to work with it as a markdown document rather than a large string value in a TypeScript file. The init command can just copy the file over to the target location in the file system.

[mpfilbin]

If we opt to extract the markdown content as a standalone file, we could use Node streams to efficiently copy the file contents doing something like:

import { createReadStream, createWriteStream } from 'fs'

const templateFile = createReadStream('agents.template.md');
const agentsFile = createWriteStream('path/to/plugin/Agents.md');

templateFile.pipe(agentsFile);

templateFile.on('error', (err) => {
    this.log(chalk.red(`Unable to copy Agents.md file, ${String(err)}`));
});