wingman — Claude Code plugin for project memory and maps
Wingman keeps project knowledge in the repository, checks data contracts, and helps agents find existing features. Use it before changing code or wiring real data into a project.
MIT ★ 1,596 updated 2026-10-29
/plugin marketplace add hashgraph-online/awesome-codex-plugins
/plugin install wingman@awesome-codex-pluginsWhat wingman does
Wingman provides skills for repository memory, data contracts, and project maps. An agent can load saved context before substantial work, then record useful project knowledge afterward in .wingman/. Memory setup and cleanup run only when directly requested.
data-contracts helps match real inputs, such as API data or database rows, to the code that receives them. Before building a feature, project-map-find searches for existing flows, components, and patterns; project-map-catalog records a durable capability in .wingman/project-map/ so future agents can find it. User and project instructions take precedence, so Wingman’s guidance does not override local rules.
What it helps with
- load repository context before fixing a bug
- match an API response to the code that consumes it
- find an existing component before adding another
- record a reusable project capability for future agents
- compact or correct saved memory on request
Example prompts for the agent
- Load Wingman memory for this repository before fixing the bug with
/wingman:memory-load. - Compare the API response with the receiving code using
/wingman:data-contracts. - Search for an existing upload progress component before creating one with
/wingman:project-map-find.
How to install wingman
Plugin marketplace
/plugin marketplace add hashgraph-online/awesome-codex-plugins/plugin install wingman@awesome-codex-pluginsStep by step, with commands for each platform: Claude Code plugins: marketplaces, installing, and building your own
Questions about wingman
How do I install wingman in Claude Code?
Run these commands in order: /plugin marketplace add hashgraph-online/awesome-codex-plugins, then /plugin install wingman@awesome-codex-plugins.
What does the wingman plugin do?
It adds skills for repository memory, data-contract checks, and project-map discovery. Memory files live in .wingman/ inside the current repository.
Where does Wingman store project-map files?
They live in .wingman/project-map/ in the current repository. Use project-map-find to search the map and project-map-catalog to add a capability.
Source text
wingman.ai · MIT
# Wingman [English](README.md) | [中文](README.zh-CN.md) Wingman is a coding-agent plugin with project memory, contract checks, project-map discovery, and focused workflow guidance. ## Install For Codex: ```bash codex plugin marketplace add lsshym/wingman.ai codex plugin add wingman@wingman-marketplace ``` Start a new Codex thread after installation. For Cursor or Claude Code, use the plugin metadata in this repository. Skill names may appear with a platform namespace, such as `/wingman:memory-setup`. ## Memory Skills Use these as a simple memory workflow for each repository. ### `memory-setup` Use once when you want Wingman memory in a repository. ```text /memory-setup ``` ### `memory-load` Use before meaningful work, especially bug fixes, refactors, business logic, API work, or existing feature changes. ```text Use `memory-load` before this bug fix. ``` ```text Load Wingman memory before changing the upload flow. ``` ### `memory-sync` Use after meaningful work when the agent should record useful project knowledge. ```text Use `memory-sync` to record the API contract decision from this change. ``` ```text Sync memory for this bug fix, but do not write unrelated history events. ``` ### `memory-clean` Use only when you explicitly want memory compacted, pruned, deduplicated, or corrected. ```text Use `memory-clean` to compact the current memory context. ``` ## Independent Skills These skills are separate from the memory workflow. Use them when they fit the task. ### `data-contracts` Use when connecting real source data to receiving code across APIs, database rows, webhooks, SDK/vendor payloads, config/env/CLI input, generated clients, forms, UI props, or AI structured output. ```text Use `data-contracts` to replace this mock payload with the real source contract without inventing fields. ``` ### `project-map-find` Use before building something new, or when you need to find whether an existing feature, flow, page, component, module, contract, pattern, or business concept already exists. ```text Use `project-map-find` before creating a new upload progress component. ``` ### `project-map-catalog` Use after creating or finding one durable project capability that future agents should be able to locate, understand, or reuse as a precedent. ```text Use `project-map-catalog` for src/components/UploadProgress.tsx. ``` ### `using-wingman` This is Wingman's entry skill for platforms that load plugin-level instructions. You usually do not need to call it directly. ```text Use `using-wingman` to load the Wingman skill guide. ``` ## Slash Aliases ```text /memory-setup /project-map-find /project-map-catalog ``` ## Notes - User instructions and project-local instructions still come first. - Wingman memory files live inside the current repository under `.wingman/`. - Wingman project-map files live inside the current repository under `.wingman/project-map/`. - `memory-setup` and `memory-clean` run only when you directly ask for them. ## License MIT
© keni · MIT · hashgraph-online/awesome-codex-plugins