ensemblr AGENTS.md

Agent Instructions

These instructions apply to this repository.

Project Naming

• This project was previously called piductor, then Ensemble. If agents find references to piductor or Ensemble in code, documentation, branches, commits, issues, or planning notes, interpret them as references to Ensemblr unless the local context clearly says otherwise. The current product name is Ensemblr (domain ensemblr.dev).

App Scaffolding Requires Current Official Docs

When scaffolding an app, project, framework integration, SDK integration, CLI setup, or cloud-service setup, agents must not rely on training data, memory, or recalled commands.

Required workflow:

• Inspect the local repo first so generated files and commands fit the existing project direction.
• Use Context7 MCP before selecting install steps, package names, CLI flags, templates, or generated-file structure.
• Start with resolve-library-id for the relevant library, framework, SDK, CLI, or cloud service unless the exact Context7 library ID is already known.
• Call query-docs with the selected library ID and the full scaffolding question.
• If Context7 is unavailable, incomplete, or lacks the relevant tool, check the current official documentation online.
• Prefer official install directions, official starter templates, and official CLI tools such as documented create, init, or generator commands.
• Do not invent or guess package names, versions, CLI flags, templates, config keys, or setup steps.
• If official docs and local repo conventions conflict, preserve local conventions where possible and call out the tradeoff before making a risky change.
• In the final response, mention the documentation source and the exact official command or CLI path used.

Scaffold provenance guardrail:

• Do not hand-author generated app structure from memory when an official generator exists.
• Run the official generator in .context/ or another disposable directory first, then copy or adapt from that generated output.
• If the generator conflicts with npm, hooks, existing files, or other repo policy, stop and explain the conflict before choosing a workaround.
• Record scaffold provenance in the final response or a tracked audit note: documentation source, exact generator command, generated files used, and every intentional deviation.
• Treat manually added package names, versions, config keys, templates, or generated-file structure as invalid unless they are directly backed by current official docs, generator output, or an explicit user decision.