Default Context Generator

Open source (MIT). The extension is published so anyone can install it from the marketplace; the repository is public for contributions and transparency. (No promotion — just available for those who find it.)

Internationalization: primary language English, secondary Portuguese. Extension UI and manifest follow the editor language; see .cursor/rules/i18n.mdc and CONTRIBUTING.md.
Português

Automation that runs inside Cursor (the agent runs the flow) to generate context, rules, best practices, and skills in Git repositories:

• Set up new projects — get the repo ready with rules and context documentation.
• Get into existing projects — extract and document the system by area, based on the code and technologies used.

The core is skills and rules: Cursor analyzes the repo and writes the files in .cursor/ and docs/. No CLI is required: the extension opens the chat and pastes the prompt for you; you send and the agent generates the context.

Extension: "Generate context" (status bar or command palette) — opens the chat with the prompt already pasted; you send and the agent creates docs/context/, .cursor/rules/, and .cursor/skills/ in the conversation. All generated outputs must stay inside the currently opened repository (workspace root), using relative paths only.

Build order

1. Skills — the generator's own skills (analyze repo, write rules, context documentation).
2. Get context — flow/instructions for Cursor to analyze the repo and generate documentation by area.
3. Automation — orchestration via rules + skills (and then, optionally, extension command).

Skills

• Orchestration: default-context-generator — full flow (interpret existing doc → analyze → context → rules → skills).
• Domain: software-architecture, system-design, backend, frontend, ux-ui, devops, security, marketing, testing, data-database, technical-docs, accessibility, performance.

All in .cursor/skills/<name>/SKILL.md.

Structure

defaultcontextgenerator/
├── README.md
├── package.json, src/, out/   # Cursor/VS Code extension
├── .cursor/
│   ├── rules/         # gerar-contexto, projeto-contexto, extension-typescript, i18n, context-docs
│   └── skills/        # default-context-generator + 13 domain skills
└── docs/
    └── context/       # This repo's context (README + extension, skills-e-rules, technical-docs)

Usage

• Via chat: open a repo in Cursor and ask "generate this project's context" (with this repo's skills or the prompt below).
• Via extension: "Generate context" in the status bar (bottom right) or Ctrl+Shift+P → "Default Context Generator: Generate project context". The extension opens the chat and pastes the prompt; you send and the agent generates docs/context/, .cursor/rules/, and .cursor/skills/ in the conversation. No CLI required.
  • Boundary: generation is limited to the current repository; do not create files in absolute external paths.

Install and use in Cursor

Cursor does not list the VS Code Marketplace in its extension search (it uses Open VSX). So the easiest way is to install via .vsix:

Option A — Install via .vsix (recommended for Cursor)

1. Download the extension: VS Code Marketplace → on the right, under Resources, click Download Extension (saves a .vsix file).
   Or get a build from a GitHub release if available.
2. In Cursor: Extensions (Ctrl+Shift+X) → "..." (top of the panel) → Install from VSIX... → choose the downloaded .vsix.
3. Restart Cursor if prompted. The "Generate context" status bar button (bottom right) and the command Default Context Generator: Generate project context will be available.

Option B — VS Code

In VS Code you can search for Default Context Generator in Extensions (Ctrl+Shift+X) and install from the marketplace.

Option C — Development (F5)

• F5 (Run > Start Debugging) opens a development window with the extension loaded, to test without installing.

Publishing (for maintainers): see PUBLISHING.md. To have the extension appear in Cursor’s built-in search, it must be published on Open VSX (Eclipse Foundation account required).

After installing: open a repository, use "Generate context" in the status bar or Ctrl+Shift+P → "Default Context Generator: Generate project context". The chat opens with the prompt pasted; send the message and the agent will generate docs/context/, .cursor/rules/, and .cursor/skills/ in the conversation.

For the agent to follow the full workflow (domain skills and interpretation of existing doc), copy the .cursor/skills/ folder (and optionally .cursor/rules/gerar-contexto.mdc) to the repository where you want to generate context, or open this repo in a multi-root workspace.