PROJECT SETUP FOR CODING AGENTS

Your agents.
Properly
equipped.

A private library for your Skills, MCP, Plugins and working principles. A focused kit for every project you build.

Local application · Open source / MIT · Your choice of AI

R / 001 PROJECT EQUIPMENT
  • Skills
  • MCP
  • Rules
  • Harness

Assembled for Fieldnotes

Illustrative rig. No tools are installed. Choose a project or explore the layers.

ONE LIBRARY. DIFFERENT PROJECTS. SCROLL TO UNPACK

Already part of
your workflow.

Claude CodeCodexKiroOpenCodeAntigravityGrok CLI

01 CHOOSE YOUR CONTEXT

LIBRARY ≠ ACTIVATION

Keep the whole shelf.
Bring the right pieces.

A new project doesn’t need every tool you’ve ever saved. It needs the ones that belong here.

YOUR PRIVATE LIBRARY 12 EXAMPLE CAPABILITIES
S
Native UI Skill
S
React composition Skill
S
API design Skill
S
SwiftUI patterns Skill
S
React Native practices Skill
S
Web accessibility Skill
S
Auth patterns Skill
S
Apple accessibility Skill
M
Project docs MCP
R
Your conventions Directive
P
Design Plugin Native reference
S
Deployment guide Skill
THIS PROJECT
PROJECT / 01

Fieldnotes

Expo / React Native

  1. SNative UI
  2. SReact Native practices
  3. MProject docs
  4. RMobile conventions
04 / 12 selected Review before Apply

Saved is not loaded. Project choices stay focused. Native Plugin references stay native.

Understand your library

02 SPEAK THE NATIVE FORMAT

ONE INTENT. SIX HARNESSES.

Same kit.
Different dialects.

Change the Harness. Rigshelf knows where the project files belong.

Your model is a separate choice. Native discovery and approval still apply.

RIGSHELF Reviewed project kit
S
SKILLS + RESOURCES .claude/skills/
M
MCP CONFIGURATION .mcp.json
R
YOUR GUIDANCE CLAUDE.md
CLAUDE CODE / PROJECT SCOPE

Skills keep their supporting files. Guidance uses the native project format. MCP uses native configuration or a local bridge for documented compatibility gaps.

Read the exact contracts

Claude Code selected. Example paths only; nothing is installed.

03 KEEP YOUR WAY OF BUILDING

Tools come and go.
Your principles stay.

Keep shared rules, stack conventions and project guidance at their own scopes. Reuse a Preset. Ask your AI to turn a rough note into a draft. Review what changes.

Your AI can help with the setup
01 / GLOBAL PRINCIPLES

Be explicit about failure.

Reusable across your projects
02 / MOBILE CONVENTIONS

Start with native interaction.

Only where the platform applies
03 / THIS PROJECT

Preserve the team’s guidance.

Reviewed, scoped and deliberate

04 THE MOMENT BEFORE APPLY

Make the change
with your eyes open.

The important part is knowing what will happen.

01 / INSPECT

Start with what’s there.

Read-only discovery finds existing AI files, including known gitignored locations.

02 / REVIEW

See the actual changes.

Inspect exact file diffs, content findings and compatibility gaps before Apply.

03 / CONTINUE

Keep a way back.

Plans retain receipts and recovery actions. Later edits are protected by preconditions.

Walk through a real setup

05 YOUR WORK, YOUR MACHINES

Local at the core.
Connected by choice.

Bring your own AI.

Use your installed Claude Code/Codex CLI, local Ollama, a local/HTTPS API connection or a connected Agent session. Generation is explicit. Proposals stay reviewable.

Connect a Provider

Back up one deliberate batch.

Compare the changes, then Sync to an existing private destination. GitHub gets one batch commit and PR. S3-compatible storage gets an immutable archive and conditional pointer.

Review the backup flow

BEFORE YOUR NEXT PROJECT

A few things,
made clear.

Does Rigshelf load my entire library into every Agent?

No. Library is storage. Only a reviewed project kit is written to that project, and the Harness controls when it discovers the files.

Does it replace native Plugin installation?

No. Rigshelf tracks native references, versions and evidence. Installation, Hooks and approval semantics stay with the native Harness.

Can it change existing project files?

Discovery is read-only. Apply requires a reviewed plan, preserves unrelated configuration and authored guidance, and rejects stale changes. Recovery does not silently overwrite later edits.

What is available today?

The workbench, CLI and MCP server, installed with Homebrew, run with bunx, or downloaded as an executable for macOS, Linux and Windows. English and Turkish are available.

Install Rigshelf
RIGSHELF / PROJECT SETUP YOUR NEXT ONE STARTS HERE ↙

Less setting up.
More building.

Build your first kit Or get your bearings in the field guide

Search documentation

Start with a guide, or search a topic.

Rigshelf field guide ↑ ↓ navigate esc close