docmancer
Docmancer compresses documentation context so coding agents spend tokens on code, not on rereading raw docs. It ingests local files, fetches public docs, indexes everything locally with SQLite FTS5
MANAGEMENT_REFERENCE ` before running `azd up`; Bicep passes it to the Microsoft Graph extension.
## Documentation Rules
- **Reference `*.csproj` or `package.json` for versions** — keep docs version-free
- **State current behavior
cookstyle -a` to automatically fix issues if needed.
5. Also always update all documentation found in README.md and any files under documentation/*
6. **Always update CHANGELOG.md** (required by Dangerfile) - Make
cookstyle -a` to automatically fix issues if needed.
5. Also always update all documentation found in README.md and any files under documentation/*
6. **Always update CHANGELOG.md** (required by Dangerfile) - Make
general project context for GitHub Copilot. For review-specific guidance, see:
- **Code Review**: `.github/agents/code-review.agent.md`
- **Documentation Review**: `.github/skills/documentation-review/SKILL.md`
## Project Overview
Workshop is a tool for defining and handling ephemeral development environments
GitHub Copilot Instructions
This document provides context-aware guidance for GitHub Copilot when working in this codebase.
## Project Overview
This is a Python project using **Microsoft Agent Framework** to build
DreamGraph Development Rules
## Documentation Maintenance Rule
**Rule:** All auto-generated documentation in `docs/` and the project root `README.md` MUST be kept in sync with the codebase during every development phase
Contributing.md`,
`Workflow.md`, and `code-of-conduct.md`.
## How to treat the repository
- Treat every change as a documentation edit. There is no build, test, or runtime
behaviour to reason about beyond Markdown rendering
configuration
- `Makefile` - TypeScript build and test commands
- `tests/` - TypeScript test files
- `llmsdk_docs/` - **Reference documentation for AI model SDKs**
- See this directory for detailed development guidelines and code conventions
## Coding
Linux, and Windows, using Flutter for the frontend and Moqui for the backend. Comprehensive documentation and support are available at [https://www.growerp.com](https://www.growerp.com).
**Frontend Architecture** (Layered Building Blocks
Licensed under the MIT License.
using System;
using System.Collections.Generic;
using Microsoft.Extensions.Logging;
namespace MyNamespace
{
///
/// Class documentation
///
public class MyClass
{
// Rest of the code...
}
}
```
**Python (`.py`):**
```python
# Copyright (c) Microsoft Corporation.
# Licensed
chain via **pipelines** — each declares `input_contract` /
`output_contract` with artifact types (e.g., `requirements-document` →
`design-document`). The `document-lifecycle` pipeline chains
requirements → design, plus validation consuming requirements and
optionally
permissions required. Use XLIFF for all user-facing strings.
- **Output language: English** — All persisted documents generated by the pipeline (`architecture.md`, `spec.md`, `plan.md`, `phase-N-complete.md`, `plan-complete.md`, `test-plan.md`, code reviews, deliveries) MUST
Snippets and blocks (when blocks are statically rendered) must include the LiquidDoc header that documents the purpose of the file and required parameters. Example:
```liquid
{% doc %}
Renders a responsive image