Project Context Setup logo

Project Context Setup

Community
Mathews-Tom
project-context-setup

Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage labels", "domain glossary for agents". Use when a repo needs durable context files before planning, triage, debugging, TDD, architecture review, or multi-agent implementation.

Overview

PublisherMathews-Tom
Repositoryarmory
Skill nameproject-context-setup
Stars
318
Forks
47
Bundled files
4
LicenseMIT
Links
  • Markdown instructions

    A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.

  • Works with any LLM

    AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.

  • 4 bundled files

    Scripts, templates, and references the model can read while it works. Files are read-only and never executed.

  • Open source

    Published by Mathews-Tom on GitHub. Read the source before you install it.

Installation

Install the Project Context Setup AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills
git clone --depth 1 https://github.com/Mathews-Tom/armory.git /tmp/armory
mkdir -p .claude/skills
cp -r /tmp/armory/skills/project-context-setup .claude/skills/project-context-setup
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Project Context Setup in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Project Context Setup on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Project Context Setup is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

  • Loaded only when it is needed

    The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.

  • Switch models mid-chat

    Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

Project Context Setup

Scaffold the repo-local context files that make agent workflows consistent across sessions: issue tracker rules, triage labels, domain glossary layout, ADR layout, agent brief format, and out-of-scope memory.

When To Use

Use this skillUse another package
A repo lacks docs/agents/ context filesadr-writer for one architecture decision
Agents need consistent domain vocabularytask-decomposer for an already-scoped feature
Triage or issue publishing needs label conventionsgithub for direct GitHub CLI operations
Multi-agent work needs durable issue briefshandoff for session-local continuation notes

Reference Files

FileContentsLoad When
references/context-format.mdCONTEXT.md and CONTEXT-MAP.md glossary formatCreating or editing domain docs
references/agent-brief.mdDurable ready-for-agent issue brief contractPreparing issue handoff
references/out-of-scope.mdPersistent memory for rejected enhancementsTriage includes wontfix decisions

Core Workflow

1. Explore

Inspect the actual repo state before writing:

  • git remote -v and .git/config for issue tracker hints
  • root AGENTS.md and CLAUDE.md
  • root CONTEXT.md and CONTEXT-MAP.md
  • docs/adr/ and context-scoped ADR directories
  • existing docs/agents/
  • existing .out-of-scope/

Report what exists and what is missing. Do not overwrite existing files blindly.

2. Choose Setup Values

Resolve these values with the user or from clear repo evidence:

DecisionDefaultOutput
Issue trackerGitHub if a GitHub remote exists, otherwise local markdowndocs/agents/issue-tracker.md
Triage labelsCanonical labels equal role namesdocs/agents/triage-labels.md
Domain docsSingle root contextdocs/agents/domain.md
Agent instructions fileExisting AGENTS.md, else existing CLAUDE.mdUpdated ## Agent context block

If both AGENTS.md and CLAUDE.md exist, update AGENTS.md for cross-agent portability. If neither exists, ask before creating one.

3. Write Context Files

Create or update these files:

text
docs/agents/
├── issue-tracker.md
├── triage-labels.md
└── domain.md

Use these conventions:

  • Keep issue tracker instructions operational: exact CLI, label mutation policy, and whether agents may comment or close issues.
  • Map canonical triage roles to real labels. Do not create duplicate labels when the repo already has equivalents.
  • Document whether the repo uses a single root CONTEXT.md or CONTEXT-MAP.md with per-context glossaries.
  • Record ADR lookup rules. Use docs/adr/ for global decisions and context-local docs/adr/ directories where present.

4. Add Agent Context Block

Add or update this block in the chosen instructions file:

markdown
## Agent context

### Issue tracker

See `docs/agents/issue-tracker.md` for where issues live and which operations agents may perform.

### Triage labels

See `docs/agents/triage-labels.md` for canonical triage roles and their concrete label strings.

### Domain docs

See `docs/agents/domain.md` for `CONTEXT.md`, `CONTEXT-MAP.md`, and ADR lookup rules.

Update the existing block in place if it already exists. Do not append duplicates.

5. Optional Domain Glossary

Create CONTEXT.md only when the user has resolved at least one domain term. Use references/context-format.md. Do not fill it with generic programming concepts.

Create CONTEXT-MAP.md only for multi-context repos where separate glossaries are needed.

Verification

  • docs/agents/issue-tracker.md exists and states the tracker, allowed operations, and required tools.
  • docs/agents/triage-labels.md maps needs-triage, needs-info, ready-for-agent, ready-for-human, and wontfix.
  • docs/agents/domain.md states single-context or multi-context layout and ADR lookup rules.
  • The chosen instructions file contains exactly one ## Agent context block.
  • Existing user-authored content outside that block is preserved.

Bundled files

The model reads these on demand while the skill is loaded. They are exposed as readable files and are never executed.

Frequently asked questions

What does the Project Context Setup AI skill do?

Scaffolds per-repository agent context so coding agents share the same issue tracker rules, triage label vocabulary, domain glossary, ADR layout, and handoff conventions. Triggers on: "set up project context", "configure agent docs", "create CONTEXT.md", "setup agent workflow", "agent issue tracker setup", "triage labels", "domain glossary for agents". Use when a repo needs durable context files before planning, triage, debugging, TDD, architecture review, or multi-agent implementation.

Why use Project Context Setup on TypingMind?

Because you install it once and use it with any model. Project Context Setup is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Project Context Setup in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/Mathews-Tom/armory/tree/main/skills/project-context-setup. TypingMind reads its SKILL.md and bundles its files and installs it as a skill you can enable per chat.

Which AI models can use Project Context Setup?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Project Context Setup?

As many as you like. As long as a model supports skills, you can use Project Context Setup with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Project Context Setup AI skill free?

Yes. It is published on GitHub by Mathews-Tom under the MIT license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇