https://github.com/a-tokyo/aiworkspace
🧑💻 Set up and manage AI agent skills and configs for Cursor, Claude Code, Codex and more across multi-repo workspaces.
https://github.com/a-tokyo/aiworkspace
agentic-engineering agents ai ai-sdlc antigravity claude codex context-ai copilot cursor openclaw plans shared-workspace skills workspace
Last synced: 2 months ago
JSON representation
🧑💻 Set up and manage AI agent skills and configs for Cursor, Claude Code, Codex and more across multi-repo workspaces.
- Host: GitHub
- URL: https://github.com/a-tokyo/aiworkspace
- Owner: a-tokyo
- License: apache-2.0
- Created: 2026-03-30T19:26:29.000Z (3 months ago)
- Default Branch: main
- Last Pushed: 2026-04-02T21:17:18.000Z (2 months ago)
- Last Synced: 2026-04-04T23:18:38.254Z (2 months ago)
- Topics: agentic-engineering, agents, ai, ai-sdlc, antigravity, claude, codex, context-ai, copilot, cursor, openclaw, plans, shared-workspace, skills, workspace
- Language: JavaScript
- Homepage:
- Size: 86.9 KB
- Stars: 11
- Watchers: 0
- Forks: 4
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
- License: LICENSE
- Agents: AGENTS.md
Awesome Lists containing this project
README
# AI Workspace
Manage shared AI agent skills, configs, and automation across multi-repo workspaces. Works with Cursor, Claude Code, Codex, Amp, and 40+ AI coding tools.
**The problem**: AI agents only see the repo they run in. An agent working in a frontend repo has no visibility into the backend, API contracts, or shared conventions -- so it assumes and hallucinates. On top of that, each developer configures AI tools differently, so skills, instructions, and rules drift between projects and team members.
**The solution**: A single `workspace/` repo that acts as the canonical source. Running `npm install` mirrors configs to the parent root, symlinks skills for every AI tool, and installs git hooks to keep everything in sync.
## Quick Start
**Create a new workspace** (one-time, by whoever sets it up):
```bash
mkdir ~/dev/ && cd ~/dev/
npx aiworkspace init
cd workspace
git remote add origin
git push -u origin main
```
**Join an existing workspace** (every other team member):
```bash
cd ~/dev/
git clone workspace
cd workspace && npm install
```
`npm install` restores skills from the lockfile, mirrors configs to the parent root, creates skill symlinks, and installs git hooks. See [setup.md](setup.md) for the full guide.
## How It Works
```
~/dev// <- open this in Cursor / your editor
├── workspace/ <- this repo
│ ├── root-config/ <- canonical source for root-level AI configs
│ │ ├── AGENTS.md <- standing instructions for all AI tools
│ │ ├── .agents/skills/ <- workspace-wide skills
│ │ └── skills-lock.json <- lockfile for workspace-wide skills
│ ├── .agents/skills/ <- workspace project-specific skills
│ ├── scripts/ <- automation (setup, hooks, skill wrappers)
│ └── package.json
├── / <- your app / service / library
├── /
└── ...
```
The setup script walks `root-config/` generically. Add new config types (Cursor rules, Claude settings, Codex config) and they sync automatically with no script changes.
## Knowledge Hierarchy
Everything follows **nearest-wins**: the closer a file is to the code being changed, the higher its priority.
| What | Workspace-wide | Per-project |
|------|---------------|-------------|
| Instructions | `root-config/AGENTS.md` synced to root | `/AGENTS.md` |
| Skills | `root-config/.agents/skills/` symlinked everywhere | `/.agents/skills/` |
| Cursor rules | `root-config/.cursor/rules/` symlinked | `/.cursor/rules/` |
| Docs | `docs/` repo (sibling) | `/docs/` |
## Skills
```bash
npm run skills:add -- [--project ] # add from registry
npm run skills:add -- owner/repo --skill # pick from multi-skill repo
npm run skills:remove -- [] [--project ] # remove
npm run skills:create -- --name my-skill # create manually
npm run skills:list # list installed
npm run skills:find # search skill registry
npm run skills:update # update all
npm run skills:check # check for available updates
npm run skills:setup # re-sync configs and symlinks
```
Without `--project`, skills install to `root-config/.agents/skills/` (workspace-wide). With `--project `, they go to `/.agents/skills/` (project-only).
Skills are tracked in `skills-lock.json` (source + hash). On `npm install`, they are restored from the lockfile automatically.
## Upgrading
```bash
npm run upgrade
```
If `aiworkspace` is in `devDependencies`, this updates that package from npm and copies its `scripts/` into yours (your team's `version` field stays independent). Otherwise the workspace falls back to git: `upstream` remote + `upstream/main` for `scripts/`. `npx aiworkspace init` sets `upstream` automatically. See [setup.md](setup.md) for details.
## Requirements
- Node.js >= 18
- Git
## License
Apache-2.0