Menu
Navigate your projects. Get context, paths, status. Use when needing project overview or finding specific work.
Install with Codex or Claude Copy this prompt, paste it into Codex, Claude, or another assistant, and let it review the skill page and install it for you.
Based on SOC occupation classification
Read Claude Code documentation to learn about features, capabilities, hooks, skills, MCP, subagents, and how to use Claude Code effectively.
Close a dev-cycle session, capture learnings, and optionally commit. Use when development work is complete and ready to wrap up.
Fully autonomous development mode. Spec in, production-ready software out. Claude makes decisions, uses agents, commits locally. Only stops for hard blockers.
Run QA checks on current work. Tests, linting, type checking, build verification. Use during or after development to catch issues early.
Release candidate preparation. Final checks before merge - QA, security, review, changelog. The last gate before shipping.
Security audit with Sentinel. Checks for vulnerabilities, secrets, dependencies, and security best practices. Use before shipping or when working on auth/crypto/sensitive areas.
| name | my-projects |
| description | Navigate your projects. Get context, paths, status. Use when needing project overview or finding specific work. |
Customize this template with your own projects and paths.
Path: /path/to/project/
Status: [Active/Development/Production]
What: Brief description
Stack: Technologies used
Key files: Important files to know about
| Client | Path | Focus |
|---|---|---|
| Client A | /path/to/client-a/ | Brief focus area |
| Client B | /path/to/client-b/ | Brief focus area |
| Tool | Path | Purpose |
|---|---|---|
| Tool A | /path/to/tool/ | What it does |
To understand any project: read .megg/info.md in its root (if using megg).
Current priorities:
